Not sure it'll get old, but you make a good point about speed. I'll make a note to keep it configurable.>>13052>the UI
I don't think the 2ch/Futallaby style was necessarily a stroke of UX genius, and I think imageboards have been hurt by people not experimenting with the formula more often. The frontend is subject to change and I've been taking suggestions and integrating them, but I intentionally want something a bit out there to separate Maniwani from the current offerings and to see if we can't come up with something better.>features
Couple things come to mind that I don't see in other engines:
1) Super easy deployment thanks to Docker; if you got docker-compose installed, spinning up a fresh instance of Maniwani backed by Postgres/Minio/nginx from scratch is 3 commands. It's a lot easier to try out than other imageboard engines. I've tried to put in a lot of effort to make rollouts easily automated; you can define your boards, board settings, rules, and general configuration with two files and keep them where you like, mount them in Docker, and bam, Maniwani is configured to your liking. I'm able to easily roll out new updates from Github to Futatsu for this reason.
2) Great media support; Maniwani is the first imageboard engine (or if not, definitely one of the first) to support WebP, and one of the few to support uploading text directly as an attachment with the thumbnail generated from the file contents. I also plan to add the ability to render Latex attachments and view attached 3D models in the browser, which will be a really great help to people uploading art and literature. I also have some stuff planned for the translation board that should make it trivial to collaborate on subtitling anime and other video without needing any sort of software installed, with the end result being an SSA file that you can plug into any video player.
The thumbnailer in general accepts arbitrary MIME types (though it can only properly thumbnail text, images, and video for now), and you can configure which MIME types are valid on a per-board basis. If you wanted to allow mp4 uploads, you could do that. I'm fairly certain AV1 will just work too (ffmpeg supports it and I use it for video thumbnailing), but I haven't bothered to try.
3) Media storage is handled with S3 and not via flat files or a document store the way a lot of imageboard engines work. So proper CDN support and whatnot is extremely turn-key, and the application server doesn't have to strain and serve both general requests and media. Maniwani actually does include a flat file storage backend, but I use it for testing only.
4) Markdown support in posts, I think that's pretty neat.
5) A REST API that supports both reading and writing, i.e, you can post and moderate via REST. The goal is to be able to do everything you that you could normally do on the web interface via REST, which seems a reasonably rare feature among imageboards.
6) Fast development pace; everything you see was done in the only past 7-8 months starting from scratch. I also pride myself on taking criticism and suggestions well and being a generally accessible head developer.
There's other stuff related to Futatsu itself (the narrow board topics, elected moderators, some other stuff), but those are the feature points that Maniwani in general can claim to have.