busybee

So yeah I’m deep in a pain flareup right now. I made sure that all of the critical bugs in bandcrash are, to my knowledge, fixed, but I just am not in a situation where I can really work on stuff right now due to a massive pain flareup.

I was just starting to work on some music for a game jam game and Novembeat but I don’t think that’s really in the cards for me this year.

And of course now that I’m in agony, suddenly a lot of folks want to interview me for engineering roles that I’d normally be very interested in, so, thanks for twisting the knife on that one.

At least choir is going pretty well and gives me stuff to look forward to.

I agree that this is a massive pain point and it’s something I’ve talked about a lot on this blog.

At present, I use a combination of 1 (via isso) and 4 (via webmention.io + webmention.js). The integration on 4 is also helped by using Bridgy and Bridgy Fed to receive webmentions from Mastodon and many of the silos, which strikes an okay balance for me, although it’s far from perfect.

One of the biggest problems with webmention, IMO, is that it doesn’t provide a good story for protected/private responses to protected/private entries. Ticket Auth might eventually provide that, but adoption of that protocol has been slow-going, to say the least, and there’s still open questions about how to actually manage the credentials in an unsupervised flow (especially when using a third-party webmention endpoint). An older WIP called AutoAuth had a much better story for that use case but the protocol was incredibly complicated and implementations never progressed beyond the proof-of-concept stage.

For me, isso as my primary comment system remains the least-bad option of a lot of bad options.

how the fuck was this amazing parody of 2020s tech trends made in 2013