gmlgcd version 2.0
... now on sourcehut!
Initial writeup: 2024-10-09
So there we are. More freatures for software that up until now, probably just me is using. Maybe that is going to change though! (maybe?) I figured that the gemlog comment daemon was really written with my usecase in mind, disregarding other needs. So that's why version 2.0 is way more configurable than v1.x!
Moving to another hut
And we're also on sourcehut now:
Since for my hacktoberfest-esque projects, I see no need for them to be on microsofthub. But make no mistake! For less hacky stuff that is supposed to be visible to others, I still see use for GitHub. For example, my plugin for the Android launcher
KvaesitsoPlugin-PublicTransport
will stay on GitHub, since I reckon most people from the "Android customization"-community are still not fond of downloading APKs from source hosting sites. How is this then supposed to work when I also move it to sourcehut? And I actually intend that plugin to be useful to non-technical people. This definetly is not the case for gmlgcd! You have to be at least a _little_ technical. :)
I digress...
Changes
The reason I incremented the major version is mainly because the config format has changed, causing a breaking change. The example configuration file provided in the repo includes everything you need to know. But wait! Did you say manpage? YES YOU DID! There is now a manpage for both gmlgcd(8) and gmlgcd.conf(5). Finally! I really wanted to get into writing manpages, and the transpiler
really makes writing manpages easy. So naturally, this is what I used for both.
Also, to increase gmlgcd configurability, quarantine can be: disabled or configured. Disabling makes sense if you have some other kind of rate-limiting in place. Otherwise, it may not be a good idea.
Next, we have configurable authentication, where you can now tell gmlgcd to allow users with no certificate or, at your option: allow users without username nor certificate. These users will appear as "anon". We're almost 4chan-ning!
Lastly, UX is improved by introducing a help-template, that is read by gmlgcd at startup and filled, when applicable, with useful parameters to be displayed to the users on error. So instead of gemini-protocol codes 5x, users will now see a rendered .gmi file that may help their goal of commenting on your gemlog. In fact, I have changed my settings of gmlgcd as well. Feel free to try them out!
Cheers!
Source