Status update, November 2022
That moment when you want to write your status update and realize you forgot to push the one from last month… :)
Unfortunately, that also means I hadn’t written anything for a month, even though that had worked out pretty well for me. I’ll do my best to pick that up again.
The forge
I prefer to write about things when they are done, but I’ll make an exception here. For a while now, I’ve been working on moving all sending of encrypted emails into the meta.sr.ht GrapQL API. This work is now entering the final phase. Some of my patches are still pending review, but once they are all merged the cleanup phase will begin. That will involve completely removing PGPy, which we’ve been looking forward to. I am still glad to see that PGPy did see some activity again just recently, as I feared it was dead. Nevertheless, our plan is to move off of Python completely, so this is a great step in that direction.
Also not yet merged, but very close: the expiration date of PGP keys might show up on the “keys” page soon. This would already be a huge improvement, but if this works as expected we could potentially even send out emails if a key is about to expire. At any rate, we hope this will reduce the amount of forgotten-about PGP keys in our database.
But my favorite forge news is that you can now actually collaborate with people on private wikis! To me, man.sr.ht is somewhat under-appreciated. Granted, it could use some lovin’. But what annoyed me most was that - until now - a private wiki could only be viewed by the owner. That was because the ACLs were actually controlled in the backing git repository, but man.sr.ht had no proper way to check these. Well, no longer, thanks to the GraphQL API. Any user who has read access to the backing repository can now also properly view the wiki. With this out of the way I’ll try to give man.sr.ht some more of the attention that it deserves!
Almost the forge
Still sort of the forge, but not quite: just in time for the ID unification I gave our status page a little update. It is running cState and hadn’t been updated in a while. However, cState add a feature that I find very valuable: upcoming or ongoing issues are show above all the services’ status, so you’ll see them immediately without having to scroll. Here is a screenshot. And yeah, I admit it: I also wanted to sneak in a little fix of mine ;)
Did someone just use the K-word?
It seems most people found out about this in the SourceHut anniversary blog post, but (as always) we’ve not been secretive about it at all: we are experimenting with Kubernetes. The three links provide ample reading material, so I’ll just leave it at that.
In other news
So many more loose ends. But I am confident some of them will have been tied up next month. So I will stick to my habit of saving the write-up for then. The one promise I can make is that I have more initramfs adventures for you very soon.
Until then, you can send your questions and comments to my public-inbox
or ping me on IRC - I am bitfehler on libera.chat.