>>38
You could probably just grab the file from cpan manually on a shared host - make a folder called Captcha and put the file in there. It doesn't use any C extensions, and it's just one file.
http://search.cpan.org/dist/Captcha-reCAPTCHA/lib/Captcha/reCAPTCHA.pm and click on "source" at the top
>>41
name one browser that actually does that.
you can't, because there aren't any. even the browser known for having completely batshit insane bugs due to being developed by a company of lsd-using hipsters doesn't do that.
... on second thought, I'll leave hotaru alone. Otherwise, I might get called a hipster, and I wouldn't want that.
A dice roller. Type "dice (X)d(Y)[Z]" in the email field and it will prepend a little message to your post.
use List::Utils qw( sum );
#put this after "$comment=format_comment($comment,$markup,$thread);" in kareha.pl
if ($link =~ /dice \s*/( #$1
(\d+) #$2
\s* d \s* #letter d
(\d+) #$3
\s* #space
([+-]\d+)? #$4
)/xi) {
my $derp = ", "; #array element separator
my @results = map { int( rand($3) ) +1} (1 .. $2); #generate dice results
my $sum = sum(@results) + $4; #adds the results together, plus the modifier
my $roll = join($derp, @results); #adds commas to the array elements
my $modifier = ", $4" if defined $4; #http://en.wikipedia.org/wiki/Oxford_comma
my $rolled = "<strong>Rolled: $roll$modifier = $sum</strong>"; #e.g. "Rolled: 2, 3, +1 = 6", in bold
$comment = $rolled . $comment;
}Here's some miscellaneous little stylesheet-related patches that might be worth applying to Wakaba and Kareha.
kareha/border-radius.patch and wakaba/border-radius.patch:
border-radius declarations to stylesheets using -moz-border-radius, since every common web browser (Firefox, Chrome, Safari, Opera, and even MSIE 9) now supports the standard declaration. Separate patches for Wakaba and Kareha included.kareha/javascript.patch and wakaba/javascript.patch:
set_cookie() to be RFC 2109 compliant. It wasn't escaping values before, so strictly-complying cookie implementations will choke on (for example) stylesheets with spaces in the titles.set_stylesheet(), instead of when the window is closed. This gets rid of inconsistencies when working in multiple tags; in particular, changing the style and then opening a new tab should ideally show the new tab with the newly selected style..*? or .+?. Not that I expect anyone to actually use IE5, but I tested the code with it and it didn't work, so there.set_stylesheet().kareha/pseud0ch.patch:
.replytext em selector to add underlining for <em> text, since the font-style: normal rendered it indistinguishable from normal text. (Was that intentional? Why?)I tested these changes in Firefox, Chrome, Opera, and Internet Explorer, and everything appears to work.
I am working on linking multiple boards together through a single .php file roughly like so:
index.php?board=one
get($board)
include($board/wakaba.html)
the issue I'm having is with make_http_forward, it always dumps the user into Boardname/wakaba.html rather than index.php?board=Boardname.
In every case i can find in wakaba.pl, I've changed make_http_forward(HTML_SELF,ALTERNATE_REDIRECT) to make_http_forward("http://website.com/index.php?board=$myboard",ALTERNATE_REDIRECT), and even gone so far as to go into wakabautils and alter the make_http_forward function to
if($alternate_method) { $location=mypage;
What I've found is in every call of "ALTERNATE_REDIRECT", it seems to completely ignore the location I give it. The only way I've found to get this to work is to put a $location=page in the ELSE section, but I can't actually find any calls to make_http_forward that don't use ALTERNATE_REDIRECT so i'm not sure where these calls are coming from, and doing so breaks the admin panel.
It's clear I'm not understanding this function and I've spent about 2 hours on this, so if anyone can help I'd be thrilled.
>>52
Pretty sure I have something similar working at http://www.studiocrabapple.com/index.php?id=board.php
Is this what you're trying to accomplish?
Here's a patch for Wakaba I made to deal with a raid on my board. It adds a "Ban All" link in the admin panel, which bans every poster in a thread, so you don't have to add bans for them manually. Perfect for dealing with CP floods and such. "Mass-banned: " will be prepended to the ban comment, but you can customise that in config.pl.
To apply it, run patch < wakaba_massban.patch on a clean install of Wakaba.
While I'm at it, here's also a patch for Kareha which lets you ban IPs on non-Apache web servers, as requested in http://wakaba.c3.cx/sup/kareha.pl/1316722874/. It simply prevents the user from posting, nothing more, nothing less.
IPs are added in a file called ipbans.txt. I haven't bothered trying to encrypt it or anything, so you might want to configure your webserver to deny access to the file.
Disclaimer: I'm not really familiar with Kareha, so there might be stuff I've left out. I tested it using mode_message, and it worked fine.
Apply it using patch -p1 < kareha_bans.patch.
>>38 The CPAN module for recaptcha is available, but it doesn't verify if it's correct or not. It just goes straight to posting.
>>56
You're probably missing one of its dependencies. The patch is designed to allow posting if the module doesn't work.
Try running perl -e 'use Captcha::reCAPTCHA' on the command line and see if that returns any errors.
>>57 It output's:
Can't locate Captcha/reCAPTCHA.pm in @INC...
Should I reinstall? I've searched Google, no helpful information.
>>58
How did you install it? I use Debian and installing it through the package manager always worked for me. Using CPAN left out a dependency or two.
I decided to reinstall it via the package manager, and I don't receive that error anymore, but now it's saying the verification code is wrong even when it's correct. I've tried it with 10+ different codes.
>>61
I can't help you with that one. Only thing I can think of is the public/private keys being incorrect, or your server being unable to connect to Google's servers.
Adding onto my previous post;
Before:
make_error(S_BADCAPTCHA) unless $result->{is_valid};
I added:
print $result->{is_valid};
and it printed the source code of the page.
I really need help with this. I've tried everything. All the keys are correct, I've even tried it on a clean install.
Anyone at all? I've tried literally hundreds of things.
>>68
Hi,
I've taken the time to trace the problem, and I think I have a fix (but as usual, I'm too lazy to test it until anyone whines about it):
Find:
my $challenge=$query->param("challenge");
my $response=$query->param("response");and replace it with:
my $challenge=$query->param("recaptcha_challenge_field");
my $response=$query->param("recaptcha_response_field");That should hopefully do the trick. Obviously it was a derp on my part, I'll create an updated patch soon to rectify this.
Also, why do you even need reCAPTCHA that desperately? The default CAPTCHA is fine, easy to fill out, hard for bots to break and can easily be tweaked if you need better anti-bot measures.
If you're trying to cope with spam, I think you'll find that many of those so-called bots are actually humans.
>Ok, now I don't get "Error: Wrong verification code entered.", but it doesn't post the message. I've rebuild the caches, but no avail.
That's weird. I just tested the fix myself, and it works perfectly for me. Did you try fixing this on a clean install?
>It's definitely bots. Unless the same human is posting 20+ messages a second.
Uh, okay.
>>53
this is what i'm trying to accomplish. where do you change the redirect call? i've tried changing it in every call to make_http_forward i can find, but it doesn't work for me unless I put it in the actual function...
sub make_http_forward($;$)
{
my ($location,$alternate_method)=@_;$location = "http://website/index.php?board=Main"; // <--- this is awful.
if($alternate_method)
{...
I've always wondered why people thought noko was pointless. If anything it makes navigation easier. Shit, nobody even knows if you use it or not. I already wrote a noko patch for wakaba (a bit different than the one in this thread) and I'm planning on adding noko to Kareha as well. Anyone interested in a patch?
> I've always wondered why people thought noko was pointless.
it's because pretty much all browsers have a back button.
> Shit, nobody even knows if you use it or not.
yes, they do, because you usually can't use noko and sage at the same time.
>>76
Pretty sure nokosage exists, at least in Yotsuba.
When you use the back button usually you don't see the latest posts.
>>82
everyone uses the web this way aside from /b/tards. if you think noko is so useful, just write a tiny bit of javascript to implement it in your browser.
>>84
I already implemented it in Wakaba, and most message boards and forums have the feature built in and enabled by default.
Hey, you made PHPerl, which I never got around to making. GJ.
Anyone running a Wakaba board ought to read this.
There's a serious vulnerability in Wakaba 3.0.8 and below which let's anyone inject whatever HTML they want to in posts. This can be fixed by removing a couple of lines in the get_decoded_hashref() and get_decoded_arrayref() subroutines in wakaba.pl, as shown in the included patch file. There should be no problem in making these changes.
Board moderators with no access to the board files may add /chr\([0-9]/ to spam.txt in order to fix the problem.
Looks like that is there to work around some absurdity in MySQL. I supposed MySQL has since changed and is now doing the wrong thing?
I'll put together a 3.0.9.