busybee fluffy rambles

About a year ago I set up Cloudflare as a fronting CDN for this site and my music site because it was the most expedient way of dealing with an AI bot onslaught. It helped a bit but the bots very quickly figured out how to get around all that and while Cloudflare gave me some slightly-better management tools for some stuff, I figured out better approaches to the bot mitigation.

Cloudflare was also super aggressive about caching some stuff that I didn’t want to be cached, and of course, there are many, many political and ideological reasons to not want to use Cloudflare. So my plan was always to switch back to not being under Cloudflare, but the longer I waited the harder it seemed like it would be, due to how SSL certificates work. In particular, I use wildcard Let’s Encrypt certificates, which require DNS to be current, and a big thing that Cloudflare does is… take over your DNS.

But tonight I got a hair up my butt and switched back to my own termination, and it wasn’t too hard to do, with just a little bit of DNS and TLS juggling, and I wanted to minimize my website downtime.

Ughhhh, this has been a heck of a week.

As usual I’ve been full of pain. And my brief surge of enthusiasm for working on music got cut kind of short because of it. But I’m hoping that tomorrow feels better and I can go back to the studio.

I’m also not sure where I stand with my fatigue. The last few days I’ve had to run quick errands by car and those felt fine. But I’m not feeling courageous enough to drive further just yet, especially with how any escape from White Center means following curvy roads which are especially triggering to me.

I worry about where things are and how I’ll be affected by it. I feel like the dominoes are starting to fall.

Wellp, today I got yet another denial from social security, which tells me this ain’t gonna change any time soon.

The previous denial came with a whole bunch of transphobia and also a claim that I am able to work, doing jobs which simply aren’t available and not reflective of the reality of my situation.

I haven’t received the formal denial yet, just the notification that my appeal was denied, so I suppose in a couple weeks I’ll be getting another giant packet from SSA to fume over.

Wellp, I didn’t get a whole lot done on the TODO list but at least I Tried™. (I did call about the sleep study but they never returned my call and it slipped my mind to try calling again. Oh well, next week.)

Back in the day, independent social media enthusiasts were building their own social spaces on RSS/Atom and self-hosted publishing. There was a huge ecosystem of feed readers and publishing software, where anyone could use their own choice of tools to interact with the space, and it was super cool.

Then Google got into it and made Google Reader, which was a really good feed reader, but they couldn’t figure out how to make it profitable and wanted to shove everyone over to Google+, so they shut Google Reader down, and then the tech press breathlessly claimed that RSS was now dead as a result, and because RSS was (in their eyes) dead, it became a self-fulfilling prophecy. Nowadays, RSS is seen as an obsolete thing only used by diehards, and corporate social media has become the norm, with a relatively tiny faction of people settling on ActivityPub instead, despite it being a poor match for the kinds of things that people used RSS for.

Here are the things I need to take care of within the next week:

• Schedule a sleep study
• File my quarterly business taxes
• Edit background video for Saturday talk
• Set up projection mapping for Sunday show
• Start working on specification for game dynamic soundtrack engine
• Take care of the major clutter piles in the office
• Empty out the car at the nearest Goodwill
• Take the car to the mechanic for servicing

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.