J.TrIDr3ESpPJEs ID: c10550 June 19, 2018, 11:53 a.m. No.1815936   🗄️.is 🔗kun

Double thread post:

https://8ch.net/qresearch/res/1815630.html

https://8ch.net/qresearch/res/1815743.html

 

Another double thread post:

https://8ch.net/qresearch/res/1815156.html

https://8ch.net/qresearch/res/1815095.html

 

Pedophilia association attempt:

https://8ch.net/qresearch/res/1815244.html

 

Whack-a-mole!

J.TrIDr3ESpPJEs ID: c10550 June 19, 2018, 12:11 p.m. No.1816205   🗄️.is 🔗kun

Board posting security proposals for threads (min char length is good):

 

1) At least one link (either 8chan or article). Use a REGEX to detect.

 

2) Cooldown period of 1 hour minimum between posting threads (no high quality thread is going to be quicker than this, and the higher the quality, longer the cooldown).

 

2 can be circumvented by IP rotation - but that will highlight those who 'don't play ball' (they will have burn multiple IPs in order to double post/slide etc which will expose their footprint for you to see).

 

3) No exact duplicate titles, and:

 

4) No exact duplicate thread content from threads found on the current page (index first post in a database with the URL UID as lookup).

 

5) Force one posting to a pre-existing thread (any thread) within a 24 hour period before a given IP can post a thread (this will force IP bunny hoppers through additional complexities, but this requirement won't bother chans who post in other threads normally anyway).

 

6) Require a 30 minute wait period (in a given day) from first connection before thread posting is allowed. So if someone tries to IP hop to circumvent the thread wait out, and they haven't previously connected with that IP on that given day, they'll still have to wait 30 minutes (a chan will, on the other hand, already connected and just not yet posted a thread).

 

The goal is to keep adding security measures that allow constructive behaviours (by keeping scope to constructive behaviours, EG no constructive poster would flood a forum, etc) and curtailing abuse.

 

From an admin standpoint, an additional measure: dislodging threads. Basically, it means the thread disappears from the main page, but remains active so not to trip any automatic detection (so if a bot checks for thread deletion, it doesn't get an error).

 

Hope this helps. Feel free to modify or ignore suggestions.