The core consists of 3 SSG programs and 913 LOC (lines of C) in total.
The rest is made up of two execline cgi scripts and a url parsing helper.
Pinned threads are orange, anchored threads a lighter gray and locked threads red.
The tripcode hashing function gets the preceding name passed as well, the leading number signs specify how many rounds of hashing will be applied.

That's all for now.

Why is not written in Forth or Assembler (possibly FASM like AsmBBS)? If you're gonna be a madman, go full madman with no excuses.

>>2
Because i'm a huge djb fangirl and wanted to make qmail: the textboard. Later versions of the software may or may not involve
<fully lockless thread/post creation
<modular post markup
<a special-purpose http server fusing fastcgi with qmail-rspawn
<socket level, zero-copy broadcasting

Hey, come join our forum for NS/Fascists
Use a Vpn or Tor to protect your IP
https://fashfront.org

>>4
>fascism
>clownflare
>pseudonymous forum
>advertizing it on leftypol but dead and without images
*dies of cringe*

>>3

https://skarnet.org/ has some djb-style networking software, including a HTTP/1.1 server with CGI support & zero-copy streaming

>>6
I know. I tried to run this instance over tipidee originally, but didn't get the CGI permissions configured correctly. At the moment i'm too lazy to dive into the code and figure out how it applies its rules, so this instance will continue running over busybox httpd for now.

There is also a reason i'm considering writing a special purpose httpd server for the next version. CGI and NPT require one process per connection, so the next logical step would be servicing clients with only a finite number of processes. Programs would be connected over pipes, where they will send each other short messages in a sort of series of continuation passing RPC calls. I'm still unsure whether to transmit the content in-band, over a single data connection, or in a new fifo for every call though.