Heh. Building an scm is a great way to become so busy you don't have time for your actual work. Building a db is another great way.
If I could be so unproductive...
If I could be so unproductive...
It goes much further than that...
When one views a fossil-hosted forum post from the main fossil site or sqlite's site, they are looking at...
- A forum post rendered by software Richard wrote. - Piped out to you via an HTTP server he wrote. - Served from an SCM he wrote. - Stored on a database package he wrote. - All coded in a text editor he wrote.
Complete vertical integration. He's written, or had a majority hand in, every part of the chain except for the browser. We're all awaiting his announcement about his browser project. It's only a matter of time.
It's demonstrably become impossible to manage spam in such an environment without the resources of mega-corps, whereas fossil aims to be a entirely SCM environment in a single binary hosted from modest hardware (e.g. a Raspberry Pi).
The inability to manage spam was the driving factor for the forum. It is somewhat quirky, but it works well and our spam rate has been literally one single spam in nearly three years of operation (and that one was subtle - hiding an ad link inside a markdown hyperlink which enclosed only a single period). Similarly, the sqlite forum (which was migrated only relatively recently) is also spam-free.
If you have found a way to develop a fully spam-proof, mailing-list-based solution then, by all means, show us the code. Until then, the forum has proven to completely solve the problem it set out to: provide a spam-free communication channel for fossil and sqlite.
It's a basic tk-based app, IIRC. i peaked at it once when he posted a link to it, but that was 7+ years ago and i don't recall where it lives. No syntax highlighting, no configurable options (beyond editing the source code), very much built for his personal coding style.
You don't want to leave emacs. Emacs loves you. Trust emacs.