Name: FrozenVoid 2013-09-04 4:52
If you don't want to people to resurrect old threads or prefer the content to be fresh,
Just set the algorithm for bumping such that each new post doesn't move a thread to the top
but bumps thread position one higher.
e.g.
thread #1
thread #2
thread #3 <--new post moves this thread to position of thread #2 which falls to #3
Currently, even captcha doesn't prevent necroposting. It is a flaw of many forums, but most have age limits (e.g. thread older than X days are not bumped).
--------------------
An automated system like >>1 Anti-necro fix will shutdown any such flood attempts for good(except first few pages, and if there was a limit to repeated bumps(repeated bumps by same IP don't change thread position) even there necrospam will be stopped ). Plus there couple of suggestions down the thread in >>1 which limit spam even further(With post rate of 60s/post/IP and postfilters the spam rate will be minimal).
----------------------
>>6
>original or crazy ideas about anything, dump it all.
Small boards should start with these:
1.Increase interval between text board replies to 60 seconds to prevent spam and chatter.
(most forums have this)
2.provide a consistent interface and build customizable client-side javascript which operates on that data(e.g. show relative time, threads you posted in, custom regexp filters for posts,).
(like 4chan inline extension(which has many flaws though:its filters are slow to edit/add/remove(which can be replaced by a single regexp),it doesn't have the option to set filters on specific boards only,etc)).
3. Reject post filter. IF post contains words in reject list, its discarded but user is not banned or made aware of which words it rejects.
4. a different approach would be reducing the postinfo to minimum:removing all fields except
subject(thread-only), postnumber and content. No username/tripcode/email/date.
5. use a DFA regexp http://swtch.com/~rsc/regexp/regexp1.html for filtering posts
6. Don't allow the same post content to be submitted again for a selectable interval(hash posts and if e.g. in 1 hour someone tries to post it, it will be rejected, but after 1 hour it will allow it)
7. minimal post content filter:if reply is less than x characters or less than x words its rejected.
8. capslock filter, filter multiple repeated words(a limit of 3 words repeated in sequence).
9. unicode/high ascii filters(with optional whitelisted ranges), maximum BBCode tags, maximum links.
10. entropy filter: if the entropy is close to 8 bits per byte the post is random garbage if its lower than English/source code its probably ascii/sjis art.
11. Uncommon trigraphs filter: see http://pastebin.com/qzLRui2X
12. Filter words longer than x(e.g. 25) chars, Single spaced letters like a b c e d f.
13. After posting user stays in the thread and not forwarded to front page(like imageboards now(this used to be noko, now a default)).
14. Allow to report individual posts/threads(like on imageboards) and optionally automatic hiding of posts which are reported by more than X ips(with unhide/hide buttons for all users).
Alternatively give the OP of thread ability to hide posts(user can unhide/hide them via button).
15. Allow anonymous polls. e.g. if someone want to request a board/site change they will have to show it has support.
16. Support for most html tags via BBCode(except scripts/frames/video/audio/images). BBcode only allows a subset of html. Disallow nested or repeated spoilers.
17. Statistics for most popular pages by views, unique posters, most posts, daily/weekly/monthly/yearly/all time views/posts/unique posters, all threadlists sorted by bump times,size,age,number of posts.
18. on hover links like >>123 it will show the content of post via javascript(common feature on modern boards).
19. Allow downloading of the entire board as .zip/.7z archive updated every day(it will be better than scraping). This will also create decentralized backups of content by userbase.
20. when posts are deleted from top of thread(especially,in case if my anti-necro fix is not used), thread is moved down to the same position it had before the bump.
21. thread list with 2 views, single page(all threads) and 200 threads per page, with threads split into 100 post-sized subpages.
22. Remove arbitrary X maximum posts per thread limit. As long as thread replied to it should be working.
23. limit the amount of posts user can refer to in >>number,number,number to a sane limit(such "combined" links(such as >>,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,3,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ) can easily crash the server btw if enough people click on them in a large thread).
24. Detect bots by showing (admin-only) the number of posts(with link) by unique IP as a stat list. It will allow to catch floods easily and delete all posts by IP.
25. Force the post container to wrap to screen width. Don't allow RTL LTR unicode overrides to change text beyond the field where its located.
26. sage checkbox instead of using email field hacks. Sage would lower thread position by 1 in thread queue(see >>1 ).
27. Have a separate board for suggestions/bug reports/feedback(4chan didn't have one for quite a time) and don't limit the content there. (A /suggestions/ board is better than solitary polls/threads.)
28. don't hesitate to add boards if there is any demand. (Shiichan is stuck in 2007 with its board list). Textboards are not bandwidth hogs and separating topics helps users to find content they want to read.
Also, i'm working on a shiichan extension(which will be released when its done) that will showcase how much you can do with a client-side script(without parsing JSON or expensive server queries).
Just set the algorithm for bumping such that each new post doesn't move a thread to the top
but bumps thread position one higher.
e.g.
thread #1
thread #2
thread #3 <--new post moves this thread to position of thread #2 which falls to #3
Currently, even captcha doesn't prevent necroposting. It is a flaw of many forums, but most have age limits (e.g. thread older than X days are not bumped).
--------------------
An automated system like >>1 Anti-necro fix will shutdown any such flood attempts for good(except first few pages, and if there was a limit to repeated bumps(repeated bumps by same IP don't change thread position) even there necrospam will be stopped ). Plus there couple of suggestions down the thread in >>1 which limit spam even further(With post rate of 60s/post/IP and postfilters the spam rate will be minimal).
----------------------
>>6
>original or crazy ideas about anything, dump it all.
Small boards should start with these:
1.Increase interval between text board replies to 60 seconds to prevent spam and chatter.
(most forums have this)
2.provide a consistent interface and build customizable client-side javascript which operates on that data(e.g. show relative time, threads you posted in, custom regexp filters for posts,).
(like 4chan inline extension(which has many flaws though:its filters are slow to edit/add/remove(which can be replaced by a single regexp),it doesn't have the option to set filters on specific boards only,etc)).
3. Reject post filter. IF post contains words in reject list, its discarded but user is not banned or made aware of which words it rejects.
4. a different approach would be reducing the postinfo to minimum:removing all fields except
subject(thread-only), postnumber and content. No username/tripcode/email/date.
5. use a DFA regexp http://swtch.com/~rsc/regexp/regexp1.html for filtering posts
6. Don't allow the same post content to be submitted again for a selectable interval(hash posts and if e.g. in 1 hour someone tries to post it, it will be rejected, but after 1 hour it will allow it)
7. minimal post content filter:if reply is less than x characters or less than x words its rejected.
8. capslock filter, filter multiple repeated words(a limit of 3 words repeated in sequence).
9. unicode/high ascii filters(with optional whitelisted ranges), maximum BBCode tags, maximum links.
10. entropy filter: if the entropy is close to 8 bits per byte the post is random garbage if its lower than English/source code its probably ascii/sjis art.
11. Uncommon trigraphs filter: see http://pastebin.com/qzLRui2X
12. Filter words longer than x(e.g. 25) chars, Single spaced letters like a b c e d f.
13. After posting user stays in the thread and not forwarded to front page(like imageboards now(this used to be noko, now a default)).
14. Allow to report individual posts/threads(like on imageboards) and optionally automatic hiding of posts which are reported by more than X ips(with unhide/hide buttons for all users).
Alternatively give the OP of thread ability to hide posts(user can unhide/hide them via button).
15. Allow anonymous polls. e.g. if someone want to request a board/site change they will have to show it has support.
16. Support for most html tags via BBCode(except scripts/frames/video/audio/images). BBcode only allows a subset of html. Disallow nested or repeated spoilers.
17. Statistics for most popular pages by views, unique posters, most posts, daily/weekly/monthly/yearly/all time views/posts/unique posters, all threadlists sorted by bump times,size,age,number of posts.
18. on hover links like >>123 it will show the content of post via javascript(common feature on modern boards).
19. Allow downloading of the entire board as .zip/.7z archive updated every day(it will be better than scraping). This will also create decentralized backups of content by userbase.
20. when posts are deleted from top of thread(especially,in case if my anti-necro fix is not used), thread is moved down to the same position it had before the bump.
21. thread list with 2 views, single page(all threads) and 200 threads per page, with threads split into 100 post-sized subpages.
22. Remove arbitrary X maximum posts per thread limit. As long as thread replied to it should be working.
23. limit the amount of posts user can refer to in >>number,number,number to a sane limit(such "combined" links(such as >>,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,2,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,3,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ) can easily crash the server btw if enough people click on them in a large thread).
24. Detect bots by showing (admin-only) the number of posts(with link) by unique IP as a stat list. It will allow to catch floods easily and delete all posts by IP.
25. Force the post container to wrap to screen width. Don't allow RTL LTR unicode overrides to change text beyond the field where its located.
26. sage checkbox instead of using email field hacks. Sage would lower thread position by 1 in thread queue(see >>1 ).
27. Have a separate board for suggestions/bug reports/feedback(4chan didn't have one for quite a time) and don't limit the content there. (A /suggestions/ board is better than solitary polls/threads.)
28. don't hesitate to add boards if there is any demand. (Shiichan is stuck in 2007 with its board list). Textboards are not bandwidth hogs and separating topics helps users to find content they want to read.
Also, i'm working on a shiichan extension(which will be released when its done) that will showcase how much you can do with a client-side script(without parsing JSON or expensive server queries).