Jared White

lol 😂

but yeah, it IS coming.

The slow drip of fediverse features has been frustrating, but it feels like there’s finally light at the end of the tunnel. It’s been absolutely amazing even having the level of interop we have between Mastodon <-> Threads, and it’s about to get so much better. I feel like a whole lot of people out there who think they’re getting what they need out of Bluesky (news, memes, friends, whatever) would get much the same experience if they were just using the fediverse as ActivityPub intended (aka sign up for a variety of services and wire 'em up!).

I can tell you right now nobody’s on Bluesky because it’s “decentralized” because the evidence is clear, it’s not in practice decentralized lol.

This is all a bloody waste of time. I really wish I could just fast-forward two years into the enshittification when everyone realizes they got duped by Big VC. Again.

Thank you! The level of entitlement with some people is simply ridiculous. And I’m weary of claims that pointing out real technical/cultural problems with competing networks is “shaming users”. 🙄

I’m not sure what it is you’re comparing. Instances don’t “sync” with each other. It’s all based on the follow graph of the individual users of each instance. So yes, sometimes a post from one instance won’t show up until days later on another because it just so happens that post may have been interacted with by some other user and only now it shows up on the instance.

FWIW, I operate multiple Mastodon accounts across multiple instances, and I’ve had no problem with seeing posts show up right away across instances.

You seem to be incorrectly stating what is on Wikipedia, which leads:

The fediverse (commonly shortened to fedi)[1][2][3] is a collection of social networking services that can communicate with each other (formally known as federation) using a common protocol.

That last bit is absolutely key: a collection of services using a common protocol. Imagine if two different email servers didn’t both speak SMTP. Imagine if two different web services didn’t both speak HTTP. The Internet as a singular entity is only made possible because of protocol interop between all of its constituent parts.

To say “the fediverse” is comprised of multiple incompatible protocols goes against that grain, and to go back to pre-ActivityPub-as-W3C-specification days as an argument that it’s fine to label multiple incompatible protocols as all being components of “the fediverse” is a stretch.

To me, this isn’t a let’s-agree-to-disagree-issue, honestly. While the term “fediverse” is arguably colloquial and doesn’t necessarily imply any specific technical attributes, it ceases to be useful as a term if Fediverse Platform A cannot in any way communicate with Fediverse Platform B because the two platforms happen to be using 100% incompatible protocols. Aside from a third-party bridge, the AT protocol used by Bluesky is 100% incompatible with ActivityPub used by Mastodon, Threads, and others. Therefore, they cannot both be simultaneously services in the fediverse.

I’m squarely in the AT protocol is not the Fediverse camp. Fine if people want to enjoy Bluesky, but the Fediverse is built on top of the W3C protocol ActivityPub. AT is incompatible. Cool that there’s a bridge, but a bridge between incompatible protocols will always be a bit of a hack in my book.

I’m totally fine with the SWF engaging with Meta just like they would any other entity building software using ActivityPub.

Funding on the other hand is a different story. It sounds like Meta contributed to an overall fund in order to launch the SWF. OK, I suppose — but if there’s specific funding down the road for some specific project or funding in some way which appears to influence decision-making on which projects to work on or how to approach them, that’s when I have a huge problem with it.