Autism BBS

Lately the technical imperfections and design of shiichan started to get on my nerves(not including the constant shitposting) so i decided to create my own BBS. The feature set is not finalized yet, and some improvement in design might be possible(comment?).
Here is the first draft of what is coming:
* Open Source, using only free code
* Performance/bandwidth oriented
* Minimal processing, no BBCODE,only filters html tags and autolinks URLs
* C without any OOP or platform dependent code
* Very spartan text-only design, no CSS/JS or any external files
* Threads are stored as files in directory as ThreadName.Page generated as follows: 16 char random string THREADID and each 1000 posts(numbered from 0 to 999,1000-1999,etc) is a new file. e.g. /ls78saflGKsu9238.0  is first(zeroth)page of thread ls78saflGKsu9238
* replies consist of post number+text only, no name,email or timestamp, First line of first post in the thread is the thread title.
* Replying to a thread reloads the same thread page,like noko.
* no sage or bump feature, instead there is such system:
1.each new post in the thread swaps its(thread list) position with thread one cell higher(if at top, no change). If the post contains the same text as any of previous replies or only a quoted part of previous post, it does not change the order.
2.new threads start at the top of thread list.

>>16
telnet interface with readind/posting,like pre-internet BBSes? Its not that hard, and anyone already has a telnet client
>>13
>And probably better than whatever you'll cook together (and even if you do manage to put a lightning fast, standard compliant, scalable and secure web server together, prepare to spend months just on that).
Just a webserver which serves flat-file html pages and handles BBS posts from users. Its not meant to be multipurpose or standards compliant. It could be a bit faster since its a dedicated server, without any code bloat.
>>12
a text filter which will reject posts which uses a NFA regexp http://swtch.com/~rsc/regexp/regexp1.html
>>11
>Make it scale, and .. CACHE EVERYTHING!
It will be multithreaded, and file cache will be handled by OS.
>>10
It prevents necro-bumping, attention whoring/spam(repeated posts of same content), does not perturb the thread list significantly and is rewarding active original content threads with higher places in the list.
>>8-9
Scalable enterprise solutions are neither scalable, stable nor fast.