evujumenuk

If your idea of a federated Twitter is a bunch of mini-Twitters that sometimes exchange indirect replies or something, then the Fediverse fulfills that purpose completely. Mission accomplished, we can all go home now.

If your idea is that the replies to every post look the same to any user, anywhere, at any time, even the thing Mastodon merged half a year ago that supposedly fetches all replies if you remember to navigate to the topmost post, and wait up to 15 minutes for your view of the thread to coalesce, falls short.

And this is why hosting Mastodon is cheap, it fundamentally cannot provide the functionality BlueSky offers. Of course, you might think that such functionality is not desirable anyway, and that’s entirely fair. But if you’re looking for the immediacy that centralized Twitter gave users, I don’t see a way for Fedi to ever provide that, whereas there is a path to BlueSky decentralization. It’s a fact that your UX is diminished if all of your followers and followeds are not on the same instance.

But in the end, I think there is space for both.

It’s been a while since I last touched Rust, but there’s a discussion on whether to commit Cargo lockfiles to version control, and the consensus is basically that you should do it if your crate is primarily a binary, and, conversely, you shouldn’t if it’s primarily a library. It acknowledges that code at the apex of the dependency graph should follow different rules than everything below it, and this kind of reasoning could apply to licenses in similar ways.

That’s the most sensible thing I’ve read all day. I think much of the reasoning for Cargo lockfiles could apply here as well.