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.

* there will maximum privacy. There will be no cookies or per-user tracking.
If you want to preserve password for thread moderation, turn autocomplete on or use an addon doe saving form data.
If you want a custom style/wordfilter personal, write your own userscript.
I cringe when i see a casually designed site with dozens of libs and frameworks and huge CSS includes running on top of slow PHP scripts(granted for simple IO bound tasks there isn't much to do, but C is way faster in general). Processing of all that to display a text-only site is not only an overkill, its a insult to user experience and server quality.

The post visibility(hidden by OP/mod) will be controlled by a permission file named perm.dat file fetched for an entire thread(threadID/perm.dat),
it will be stored separate from thread content, and not included in the threadlist file.
Its a huge bitfield,0/1 for every post. so e.g. 100k posts is 12500 bytes
1.the person has JS disabled -> he sees all the post no need to unhide anything manually
2.the person has JS enabled ->perm.dat is fetched and ONLY posts which are marked visible are unhidden
3.the person has JS enabled and he sets to ignore OP moderation by blocking perm.dat-> all posts are unhidden


orbis terrarum delenda est

*Actually each page of the thread( configured as 100,1000 or 10K posts) will have its own perm.dat for better caching since larger permission file needs to re-downloaded on changes, increasing bandwidth use.



orbis terrarum delenda est

>2011
>flat files
>no web server
>no js
>no css

10/10, will read again

>>84
I imagine the hosting, its a DSL "server" on his room which is shutdown each night.

>>85
It doesn't have to be like that.

Are you still around OP?

>>1
no bbcode
FUCK _O^FF

>>1'
>* Performance/bandwidth oriented
>* Very spartan text-only design, no CSS/JS or any external files
Typical autist. Doesn't realize that a cached CSS file will increase performance and reduce bandwidth consumption by orders of magnitude.

>>88
Fuck off.

>>40
django
get out of /prog/