So, it's finally release time!
http://wakaba.c3.cx/releases/wakaba_3.0.0.zip
http://wakaba.c3.cx/releases/kareha_3.0.0.zip
I decided to bump the version number up to 3.0.0, partly because of a number of new features, and partly because there's been lots of messing around in the guts of the scripts, which means there are probably some new and interesting bugs. I do not recommend installing these scripts on any busy boards without doing some testing first, or waiting for others to test them for you. Conversely, testing is very welcome. Report those bugs!
Specific information will follow in the next posts.
I found a scrap of spare time, and started to work on putting together a Kareha 3.1.0 version with the bug fixes that have been piling up. So far I've done this:
I'm still looking into:
What did I forget? Also, got any brilliant ideas for anti-spam measures? I'm thinking mostly heuristics to run on the post text, but I'll consider other tricks too.
>Also, got any brilliant ideas for anti-spam measures?
I've been considering it. As stated it'd be too ugly, but adding an input field with style="display:none" should do the trick.
Bug: IMAGE_REPLIES_PER_THREAD counts the image in the first post.
Also, could you fix the "omitted posts/images" line in mode_image for when there's only a single post/image omitted?
Will this update include changes to mode_image's template? I have a highly customized version of the file, so a diff between 3.0.9 and 3.1.0 would be much appreciated.
P.S. What's the argument for implementing a ban system when you can configure it through the web server?
> Bug: IMAGE_REPLIES_PER_THREAD counts the image in the first post.
Hmm. I suppose that's a bug of config option naming at the very least. I'll try to get that fixed.
> Also, could you fix the "omitted posts/images" line in mode_image for when there's only a single post/image omitted?
Not easily, if I want to retain support for multiple languages.
> Will this update include changes to mode_image's template?
Probably not. The old version will be kept in the releases/old subdirectory though, so you can run your own diff on it in case I end up making any changes, though.
>Hmm. I suppose that's a bug of config option naming at the very least. I'll try to get that fixed.
It doesn't make sense to omit any content in the first post. Maybe you could distinguish between first-post images and reply images just as you do with text.
>Not easily, if I want to retain support for multiple languages.
If need be, the board owner can modify the string text by hand.
That makes no sense.
All right, I've installed an almost-complete v3.1.0 here and on /soc/, as a test. It has the empty-field spam trap, so I've disabled captchas to see if it helps any.
Post previewing should also work now.
Feel free to do some testing and report problems! You may need to shift-reload the page to get the new CSS and JS files for everything to work right.
This may be asking too much, but I'd like to see mode_message's deletion functionality match mode_image's more closely -- that is, the post/reply boxes include a field for deletion passwords, a checkbox appears to the left of each post header, and there's a confirmation area at the bottom of each page for re-inputting the password -- granted that user deletion is enabled in the first place, of course.
Not going to happen, as it changes the 0ch page layout too much. You can make it for yourself by editing the templates, though (although you might run into trouble with nested forms).
Is there some reason the text "Lorem ipsum dolor" has to be there (I don't have CSS support)? It's kind of annoying. How about a if you need some text there for some reason.
Oh, oops, that's a leftover from development. I'll remove it in the next version.
For some reason it says "Thumbnail displayed, click image for full size." even though it isn't supposed to be thumbnailed. I set max widthxheight to 700x500 and posted a 640x480 picture. kareha thumbnailed it to same size, only difference being the thumbnailed picture got shittier in quality.
So I just turned on stupid thumbnailing for now. Is this a bug?
No, it's just not designed to be used for full-size images. It will always say "Thumbnail displayed", for instance. If you don't want it, you have to edit the template to remove it. If you always want full-size images, turn on STUPID_THUMBNAILING, and set the sizes to huge. If you want to display images, except if they are REALLY big, you can set THUMBNAIL_SMALL to 0 instead, which should make it stop recompressing images that are smaller than the thumbnail size.
I just upgraded my Kareha version, and now I need to delete some spam posts, but when I click on the "del" link beside the posts, it says the Admin password is incorrect. Where am I supposed to enter this password? In the documentation, it says to click on the "manage" link, but I don't see any such link!
Also, is it possible to completely remove a post, instead of having to see the "this post was deleted by a moderator" message? My board has been hit really hard by spam, and now its completely covered in these messages.
The Manage link is for Wakaba only. For Kareha, go to admin.pl in your board directory manually to get to the admin interface. And no, there's no way to completely remove a post as it stands now.
http://wakaba.c3.cx/release/wakaba_3.0.5.zip
I finally got off my ass and fixed some outstanding bugs, and also put in the spam trap code from Kareha. This is a recommended upgrade for anyone who has problems with spam bots!
NOTE: You must rebuild caches after this upgrade, or the spam filter will stop all posting!
Fixes:
oekaki_style.pl (hopefully).Changes to lots of files, wakaba.pl, wakaba.js, wakautils.pl, futaba_style.pl, oekaki_style.pl, strings_*.pl and config_defaults.pl. Note for people with custom templates: You will have to rename the fields name,email,subject and comment to field1,field2,field3 and field4!
>You will have to rename the fields name,email,subject and comment to field1,field2,field3 and field4!
Wait, so you went from descriptive variables that are useful to generic, non-descriptive variables? Why?
Are you trying to make Wakaba unmaintainable or something?
Thank the spam bots. I am trying to confuse them. There are fake hidden fields with descriptive names that will cause the post to be discarded if they are filled in.
I don't know if this could be some unrelated problem of mine (I don't see how, since this is a fresh install using standard stuff), but I'm getting a very weird error with this new version that I'm not seeing on older installs.
Specifically, it's thumb nailing images with the dimensions reversed.
For example, a 1280x853 image (wide) is getting thumbnailed to a 133x200 image (tall). It's not instantly obvious because the img tag has width="200" height="133", so it's "correcting" the mistake. (Using quotes cause it doesn't really correct it, it still looks like shit)
Anyone else seeing this problem with 3.0.5 or do I need to pull apart my perl/imagemagick (Does wakaba even use imagemagick? I can't remember) install and look for brokenness?
Did some more testing, and it's not an imagemagick problem (Or it is, in a roundabout way)
convert wasn't in the path of the webserver, so putting a full path for CONVERT_COMMAND fixed it.
Aha. sips is the problem. According to sips --help:
-z, --resampleHeightWidth pixelsH pixelsW
Height, then width. No, I don't know why either.
But just switching the order makes it work fine:sips -z $height $width -s formatOptions $quality -s format jpeg $filename --out $thumbnail >/dev/null; # quality setting doesn't seem to work
Also, even when it's working it gives this error in the logs:
Warning: File format jpeg does not support option 70
It looks like the way to do quality is either "formatOptions" or "quality", but neither of them supports integer settings, only low/normal/high (ewww)
I found this from doing "sips --helpProperties" (which is bloody hard to find out about)
Man, that's fucked up. Especially since the test board run on sips and I never even noticed. Well, I did notice the problem with the quality, but got so tired of it I never fixed it.
Oh, and also: A general request to board admins:
If you edit your own style based on futaba.css, please give it a new name. "Futaba" actually means something here, and many people also want to keep using that style. Give your style a new name, and keep the old futaba.css in place. There is an option to select the default style for a board, you don't need to rename it to "Futaba" just for that.
Thank you.
where would i find a list of usercodes to modifiy text within their posts?.. like bold, colors, strikeout and so on?.. wakabamarkup only explains so much.
After some testing, it appears there were a few bug left in 3.0.5, so here's a somewhat fixed version:
http://wakaba.c3.cx/releases/wakaba_3.0.6.zip
Bugfixes:
wakaba.js has been renamed to wakaba3.js, because the old version would fill in the name field, which triggered the anti-spam filter, and people's browsers kept the old version in cache. Renaming forces them to reload the new file./\x{202e}/).(There were also some further fixes of the handling of numerical entities and charset internally, which may have broken something else. I hope it didn't, but report any problems. SQL dumps were also tweaked again and should work better now.)
Minor problems with 3.0.6:
Typos in the "YOU FUCK SPAMMER" error:
"[...] you are probably accidentiallytrying to use an URL that is listed in the spam file. Tryediting your post to remove it. [...]"
Also, the example.htaccess file uses "line-end comments", which apache (at least 1.3.x) doesn't support, and it will tell you this during every single access of your imageboard.
Just move the comment on "AddCharset utf-8 html" to the line above it, and it'll stop yelling on every access.
Would there be any way to get an sql dump that is not made for SQLite? I have already setup a wakaba imageboard and have been able to get it to connect and communicate just fine with a PostgreSQL server, and would like to be able to enter the initial data into there.
It might not work on PostgreSQL, even though it will talk to it. The syntax for making an autoincrementing column in the database seems to be different on all databases, and there's no code for doing it on PostegreSQL, so post numbers might not work right.
That said, what is the problem with the current SQL dump and Postegres? It should be simple enough to work with any SQL database, unless there is some lingering bug (there have been a number of them, so use the newest Wakaba to generate it).
>>237
Well I am using the DBI postgres driver so that should handle talking to the server no matter what the call correct? But the problem is importing the dump to the database, I can't seem to get it to work, so if someone had a different type of dump (plain diagram even, for me to input by hand) then I could make my own database for it.
That would be true is SQL was actually a standard that people follow, but it's not. There are subtle differences between pretty much every database out there. Wakaba is not built to support Postgres, and is pretty much guaranteed to not work right.
What version are you creating the dump with, by the way?
>>239
I have not created the dump, I was using the .sql dump provided in the zip of wakaba. It's an SQLite dump and I need either a postgresql dump or a more human readable dump if possible, so that I may input it by hand.
>>240
Look at the init_database, init_admin_database, and init_proxy_database functions in wakaba.pl. They do the database creation, and they're quite well commented.
If that's included, it's by mistake. It's not meant to be used for anything, it's just my test database. Wakaba creates its tables itself. However, even if you try to do it by hand, I doubt it will work with Postgres. Last I looked, the way to make an autoincrementing column in Postgres was completely different from other databases and would not work with the current code.
Hmmm, okay, then how do I get it to use the init_ functions, because at first when I made the db and started the board it said "SQL Connection Error." Then when I made all of the tables it said "SQL Fatal Error." And after reviewing the code they should be the first things executed if database pieces are missing, but they don't seem to be doing so.
Well, if you get an SQL connection error, then you're not even connecting to the database.
The thing is, I got that and then the only thing I changed was adding the "admin", "comments", "proxy", and (can't remember right now but there was another) tables to the database and that changed it from "SQL Connection Error" to "SQL Fatal Error."
I found a pretty annoying bug that I needed to fix, so I finally sat down and fixed a couple of old ones too.
http://wakaba.c3.cx/releases/wakaba_3.0.7.zip
http://wakaba.c3.cx/releases/kareha_3.1.2.zip
Changes only in wakautils.pl, wakaba.pl, kareha.pl, spam.txt and the config_default.pl files (just bumped the version number in those).
Hopefully I didn't fuck up anything too badly packaging this, it's been a while.
:( did you put any comments in the files where you edited them?
>>252
there will be many differences between the two :(
Diff against a plain wakaba 3.0.6, it's in the old/ directory.
also, the more robust entity parser fixes a more serious bug that can let people put in their posts... this is really bad because then people can inject javascript, like the bee flying around this page...
p.s. hey WAHa you need to update this board.
Indeed I do. There, should be fixed now.
Also, that only works in Kareha, so Wakaba boards need not worry. Although it's still a good idea to upgrade to fix the spam filter.
gawd, that bee's annoying. I'm so glad this board's been updated xD
thanks for the update! Bees!
A little something that might be of interest to those running Wakaba boards with the captcha enabled: http://dmpk2k.wakachan.org/captcha.txt
It's a replacement for the stock captcha.pl, and reduces the load per board between 85-95% if you have FastCGI installed. It should work whether you have FastCGI or not, but you won't see the reduced load without FastCGI. Some of the letter strokes have had a little bit of tweaking as well.
It was tested on all the wakachan.org boards for several months, so I'm fairly confident it'll behave.
i have a user that is recieving the spammer msg whenever he tries posting. there is no text in his post and the msg it shows when he attempts posting is as follows:
Anti-spam filters triggered.
If you are not a spammer, you are probably accidentially trying to use an URL that is listed in the spam file. Try editing your post to remove it. Sorry for any inconvenience.
post
Joe#tripcode
0k1je6gP
1162910789576.jpg
anddddddddddd now i can't make any post that has an image attached to it.
.......it decided to work for a few minutes and now it's doing the same thing again.
[Sun Jan 21 21:00:35 2007] [error] [client 68.148.7.216] [Sun Jan 21 21:00:35 2007] wakaba.pl: Malformed UTF-8 character (UTF-16 surrogate 0xdc80) in substitution iterator at wakautils.pl line 391., referer: http://wtfux.org/temp/res/501.html
hmmmm
line 391 of wakautils.pl:
$str=~s{(&#([0-9]*)([;&])|&#([x&])([0-9a-f]*)([;&]))}{no one has any ideas? this is causing a lot of problems :( the only 2 files that i edited are futaba_style.pl and wakaba.pl. i have placed the right changes from 3.0.6 to 3.0.7 into my wakaba.pl. When used on my friends hosting the wakaba.pl works fine. I have seen no changes in the futaba_style.pl on the switch to 3.0.7 so that cannot be the problem. The error i am getting, as seen above, is going on in wakautils.pl. I have no idea what the error means or how to go about debugging it.
What all do I have to upload to upgrade from 3.0.6 to 3.0.7? I'm lazy~
>>269
wakautils.pl, wakaba.pl, spam.txt, and the config_default.pl
Under what exact circumstance does this happen, or not happen?
>>271
replying to a thread with an image. and also sometimes when creating a thread. it does not happen to everyone and the people it happens to are not experiencing it 24/7.
I can't reproduce it. Can you determine if it happens to specific images or not?
>>273
images with less than 8 letters and numbers in it's filename (extension not included) post fine. more than that and i recieve the spam message.
As a side effect of the spam engine, it may be that the filename is checked against the spam filters... Do you have something unusual in spam.txt?
>>275
it is the same copy that you have hosted. i will replace it again to see if that helps.
Well, I can't reproduce it locally. What happens if you edit wakaba.pl and change
spam_engine(
query=>$query,
trap_fields=>SPAM_TRAP?["name","link"]:[],
spam_files=>[SPAM_FILES],
charset=>CHARSET,
) unless $whitelisted;to
spam_engine(
query=>$query,
trap_fields=>SPAM_TRAP?["name","link"]:[],
spam_files=>[SPAM_FILES],
charset=>CHARSET,
excluded_files=>["file"],
) unless $whitelisted;Anti-spam filters triggered.
If you are not a spammer, you are probably accidentially trying to use an URL that is listed in the spam file. Try editing your post to remove it. Sorry for any inconvenience.
post
cho0b
uWZbOD0k
OKAY KIDS DOES THIS WORK?
1142201616186.jpg
sadly that does not work waha. I am going to setup a wakaba board on my server that has none of my edits in it (again) to see if it works.
what does this error mean (in dumb people terms):
wakaba.pl: Malformed UTF-8 character (UTF-16 surrogate 0xdc80) in substitution iterator at wakautils.pl line 391
Maybe somebody tried to post a UTF-16 surrogate character? I don't know, what caused it?
okay, even without my edited version of the files (ie stock wakaba) I am getting the error. something strange is going on.
i am with dreamhost atm..... ahhhh
>>281
that error shows up in my error.log whenever anyone tries to post an image and gets the spam message.
also, another problem I have been having lately (of much smaller importance) why can't I put adbrite ads into my board? if i put the ad code into the post form i get xml not well formed errors :(
...what the hell haha. i replaced spam_engine with this code and at first it didn't fix it... but i removed the spam_engine portion and replaced it AGAIN and now it seems to be working... weiiiird. we shall see if it continues to work. :D
it seems i still can't post to certain threads with an image that has more than seven characters in it's filename (excluding the extension etc etc etc etc) Yes, I did rebuild caches. Also, whWREHSFDHBASFDGS GET THE FUCK OUT OF MY COMPUTER YOU FUCKING BEE AFGWERGAD
This really is weird. And I still can't reproduce it at all.
In the worst case, you can try disabling the spam.txt checker by commenting out the lines starting from:
my $spam_checker=compile_spam_checker(@spam_files);in wakautils.pl until the end of the function.
I'll try to take a wild guess at what might be the problem and try to work around that a bit later, and give you some code to try instead, if you want.
>>287
It seems to be only happening in certain (older) threads, now. And not often at all. Most users are saying that it is working fine now. Although, I don't understand why it would still happen sometimes with older threads.
Do not lose sleep over it, but if you can think of anything to try I would appreciate it very much.
Anti-spam filters triggered.
If you are not a spammer, you are probably accidentially trying to use an URL that is listed in the spam file. Try editing your post to remove it. Sorry for any inconvenience.
post
642
anonymous
lgsexiuS
HELLO BEN HOW ARE YOU
1142072561943.jpg
Delete password. It just dumps all the fields from the form onto that page in order to confuse spam bots into thinking they succeeded in posting.
ah i see i see.
p.s. still getting the error every now and again. :( still hates lengthy filenames for some reason.
http://wakaba.c3.cx/releases/kareha_3.1.3.zip
A bugfix for a very annoying bug that can cause multiplying mojibake in threads. This was a pretty subtle bug related to Perl's unicode handling, but it's hopefully fixed now.
I hope this fixes 4-ch.
Yeah, that was pretty much the point.
why are there a bee on this page
Somebody must've left the window open.
will pay user 10 dollars via paypal to insert 3 google ads on my wakaba form. please leave you email or aim address if you are interested.
will pay user 10 dollars via paypal to insert 3 google ads on my wakaba form. please leave you email or aim address if you are interested.