Today's song: Thanks for the Memory. #

Bluesky is in a jam because there's only one instance. They have an architecture for more instances, but now that we've gotten a look at what federation is like in practice with Mastodon and ActivityPub, I don't look forward to the same idea around Bluesky. Which is where the bind is, because that means that Bluesky, like Twitter and Facebook, would have to take on moderation and will get a lot of grief if they don't do it to people's liking. I wrote: "I don't think they or anyone else can afford to stand against abuse on the web, it's diseconomic. People don't pay for the service, and there's an infinite supply of abuse. You know how when they add a new lane to a freeway thinking it'll ease traffic but doesn't? imho it's the same kind of thing. I do think there's hope for small social nets with dozens or maybe hundreds of users, and let Facebook have the monster social nets, they more or less have found a way to make moderation pay. I've written about this idea a lot, filed under the phrase fractional horsepower."#

FeedLand tweak, there's a new row in the Feed Info page. Should make the flow of navigation a bit smoother. #

Over the last couple of days I moved this.how to an HTTPS server. It was fairly painless, but it did break some pages. If you have an img element in the HTML or use the image attribute in OPML, and the url of the image is on HTTP, the browser will refuse to load it, and at least on Chrome it'll look like it's still loading for a long time, possibly forever. For most of these, I'll never get around to fixing them, it just is what it is. So HTTPS despite the hype, no matter whether you convert or not, still breaks the web, and Google must know all about this and doesn't care. If a platform vendor really cared about the web as a platform, they'd look at the risk in reading an img over http and say wtf, let it go. They're like the Soup Nazi, they have you by the balls, you know it and they know it. #

This bit of arcania has also crept into my RSS feed. As you may know FeedLand is now on HTTPS, it has to be because it's managing identity for itself, and if a feed item has an image only accessible over HTTP, the browser won't load it. I guess all feed readers have this problem, and I guess images from Scripting News have always been broken? But this isn't how I remember it. Hmmm. Maybe they're doing something special, like accessing the image through a proxy running outside of Chrome's control. Haha if so holy shit. Either it's a security problem or it isn't. I really don't think images need to be protected, but what do I know. In any case, from this point on, my images will be HTTPS too. #