i got some problem with people posting threads with unicode 202E that reverses the text direction which causes the site to look VERY odd. Is there any quick fix to just remove this letter from posts/namefields?
(And please waha don't come with your "YOU SHOULD BAN ALL THOSE POSTS!!!!" some moderators might not be active and it is very disturbing.)
If you're running Wakaba 3.0.5, I think it might help if you add this to spam.txt (or make a second spam file for this stuff):
/\x{202e}/Or you could add a word ban on ߩ
Do NOT try to add ߩ to spam.txt, it will not work.
Gah, HTTP and entities. That should read, without extra spaces,
"Or you could add a word ban on & #x202E;
Do NOT try to add & #x202E; to spam.txt, it will not work."
Thank you. <3
You should add this as a default feature in your future releases though. :)
Oh and btw just a quick question, is it possible to add <a href=" into the spam.txt and the software checks for <a href" with wildcards or do i have to add those crazy /\{bla}/?
Since almost every spambot tries to use <a href" or [a href" tags.
On second check, adding /\x{202e}/ to the spam.txt or any own thing didn't quite work. (checked it again, it doesn't seem to want to see any diffrence between upper case and lowercase) i tried with all diffrence combinations of X and E in lower/upper case but didn't do any diffrence.
what
ÃÂâÃÂÃÂÃÂîlol wut?
hmmm
lol â®backwards
it still works because wakaba and kareha don't decode the post as utf-8 before running the regex to strip out bad characters.
you just have to put the actual character in your post instead of typing the html entity.
oh, i guess it doesn't work in the post, but it still works in the name...
does not work in wakaba
so how do i kill this exactly in kareha?
>>17
http://hotaru.thinkindifferent.net/kareha.diff
there may be issues if you're not using utf-8 as the encoding for your board, but there's not really any reason not to use utf-8.
if it's the default then it should be utf-8