Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

using

Name: Anonymous 2013-07-28 20:59

chicken with awful. I'll probably just use sqlite for the data storage for now. Where should we host the revision control?

Name: Anonymous 2013-07-31 7:52

>>48

These are the basic requirements I'm going with right now.

server listens for http on 80 and https on 443 (or whatever the https port is if I have that wrong).

request api will match shiichan so that our spam scripts will still work.

domain-name/board-name/ will display a list of the top X threads and their titles. Later the main page like here will be implemented.

domain-name/read/board-name/thread-number will display the entire thread. Post number ranges will be implemented later. thread numbers will be unix timestamps to match the convention here.

Posting format will match the interface here. The IGNORE THIS OK tag will still be there, but wont do anything for now.

All submitted text must be html tag escaped. I think we learned from 190chan this is needed from the beginning.

I want to work off of the principle of no ips being banned. If something fails the IGNORE THIS trap, the post may be blocked. But long term I would like the site to be able to block a real spammer and allow an actual poster that are both posting from the same proxy. This will take more time of course.

While we are at it, we can add a ssh and telnet interface for the funsies.

later:
hyperlinks, post numbers, bbcode.

later later:
bbcode extensions. turing complete bbcode.

later later later:
optional thread updates with ajax

later later later later:
rewrite the entire server in C and store all data and cached pages in RAM. Run another thread that writes new posts to the persistent database.

later later later later later:
rewrite the entire server in x86 assembly.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List