/siberia/ - Off-topic

I posted

I added a tripcode scheme based on blake2b.

Cool. I have posted there.

This version is pretty much complete and i will make a release soon. I already plan on refactoring some code, but don't plan to add any new features for this version.

What features do you consider essential for a textboard? I've already ruled out formatting beyond quoting and links, since nobody uses those. I also wouldn't add flags without designing a general post form extension mechanism first, so those are on hold for now.

For those who can't view the TOR instance: quoting, links, secure tripcodes, sticky threads, threadlock, boardlock, bumplock and a capcode are all implemented.

>>680343
>This version is pretty much complete and i will make a release soon.
Looks nice!

>What features do you consider essential for a textboard?
* Option to make the post use Shift_JIS art font.
* I would appreciate it if there would be option for the admin to enable public mod logs that would log that post No. 123 got deleted on 2025-06-20 12:00 UTC by mod1 for reason "foobar". I think it would help detect hijacked mod accounts.
* I would appreciate if the post timestamp could be set by admin to be always relative time (like "3 hours ago"), so screenshots would reveal less information to feds.

>>680477
Thank you for the feedback!
>Option to make the post use Shift_JIS art font.
I'm reluctant about adding something like a code tag, but i might add an option to choose between variable and fixed space styles in the form. If shift-jis is compatible with ascii and isn't messed up by the html quoting, it should just be passed through as data.
>mod logs
The current scheme makes removing individual posts impractical and most actions are meant to be done by modifying the filesystem directly. I could look into making a log, where mods and jannies would have to add deletion messages, though (the post counter would make unexplained actions pretty transparent).
>relative time
Unless there's a html feature to specify this, not going to happen in this version.

bumping to remind me to join your text board

>>680477
>>680573
>>Shift_JIS
I have decided against supporting ascii or shift-jis art in version 0, because the formatting would need to be passed as an extra option to my post/thread creation programs, which violates the live free and die spirit of this conceptually pure textboard. Version 1 will decouple formatting from site generation.
>>mod logs
At the moment i'm adding the ability to add comments to threads and a deleted state for spam, in which a thread will immediately slide to the bottom and not link to its page. This should allow for a great deal of transparency

Threads may now be unlisted with the zap action. Moderators can also add comments, which will be displayed beside any thread.

Over the next days i will finish up the documentation and do other boring quality-of-life stuff for operators. I'm already thinking about how to structure the next version though:

Currently boards are generated on each bump and threads only once, with posts being appended to the threads html file at a fixed offset from EOF. This is possible because the size of the footer is always known (given the correct version string). As opposed to a full templating system, my code writes out blocks of html and inserts arguments in between, so if the format of the variable length arguments is know, you can walk through the site html without any costly parsing.

I imagine any sufficiently sophisticated templating system compiles its macro language to a "block-based" format, yet with block ranges and arguments as explicit data types, you can do in-place modifications with only so much as a gap buffer. The motivation for this is not so much performance (i haven't measured anything), as obsoleting the need for a database beyond the filesystem itself. Accessing the counter and writing posts needs to be sequential anyways, so why not dispense with enterprise-grade databases for ad-hoc but well-defined records?