busybee fluffy rambles

Login on this site has been a bit flaky for a while since in my never-ending fight against AI bots I had switched to a multiprocess configuration to give the site a bit more robustness, but which had the side effect of most logins only having a 50% chance of working due to fiddly details inside Publ (or, more precisely, Authl, which defaults to only being safe for single-process configurations).

So, Publ finally implements multiprocess-safe token storage, which is something I’d been meaning to add since approximately forever ago (although it seems I never opened an actual issue to track it, oops), and this should make user login reliable again.

Thanks to Spud who finally lit a fire under my butt to fix this annoying issue.

Time for another proverbial cheese sandwich post¹. Thinking about the end of the year and what’s coming up for me.

This isn’t my annual aspiration wrap-up post; that’ll come later.

I was just going through some old files while preparing some hardware migration stuff (ugh) and I came across a file entitled distributed social network.md, dated December 13, 2014. This was the start of my ideas about what would eventually result in Publ.

Obviously things drifted a lot between 2014 and 2017 when I finally started implementing Publ, and a lot has changed with my goals since then as well.

Don’t use this as a roadmap, is what I’m saying.

Back when Publ was brand-new I was using a fairly common ORM for managing my database. It was okay but I had some issues with how the project was being run, particularly in how the core maintainer treated bug reporters who were reporting things that he didn’t personally agree with.

So I switched to Pony ORM, which has a much nicer, more-Pythonic API, and whose maintainers are friendly and helpful. It’s missing a few important functions such as migrations but for Publ it doesn’t matter so much and they were always claiming that migrations were coming “real soon now” for a while.

Unfortunately, some changes in Python 3.11 broke Pony completely, and progress on getting it working again has been, well, slow.

Back when I switched to Pony I mused about just dropping SQL entirely and moving to a more primitive indexed data store, such as lmdb. But I really do not have it in me to completely redo all that stuff in Publ again, especially with all of the weird regressions that always occur due to subtle differences in locking behavior and so on.

Sometimes I think how now that I actually know how Publ should work I should rewrite it with better testability and a more actively-developed Markdown processor (because misaka has also been abandoned and is in permafreeze status), and if I’m going to do that, maybe I should use it as an excuse to finally learn Rust because honestly the Python ecosystem is kind of a mess right now.

I’ve put so much work into Publ but keeping the project going just feels so… difficult.

Or I mean I could switch to any number of existing site generators out there but then I’d be giving up all of the things that makes Publ unique (friends-only/access-controlled entries, variadic templates, top-notch template-driven image renditions, etc.).

This is one of those things where the decision would be a lot easier to make if people were actually helping to fund Publ development or if it had any actual, y'know, users.

I haven’t felt like blogging lately, but here’s some updates.

Still on disability leave, and still in considerable pain. I’m trying not to work too hard on things, but it’s hard not to do things.

For example, I worked on a song with my friends Ken and Huan-Hua for this week’s Song Fight!; we entered the “We Did Everything We Could” fight under the band name Richard Donner Party. It was a fun song to make. Fortunately I didn’t have to even so much as look at a guitar. Most of my work was vocals, light keyboard work, and editing.

Yesterday I participated in the IndieWeb sensitive data pop-up, or at least the first half of it (I had to disappear for my refrigerator delivery). It was really great to have some further discussion about what people want out of this stuff and how we’re all going to agree to get it.

Authentication stuff

One of the biggest pain points that keeps on coming up is there being no support for people to be able to get private posts without having to log in or be notified about them in side channels. Lots of people are doing things like making pages with unguessable URLs and then doing side-channel notification, but that’s unwieldy; fewer folks are doing things with actual login mechanisms.