Not to mention nobody uses Mastodon either. Who should Jack be trying to placate, exactly? The extremely few people who were so fed up with Twitter that they left for Mastodon, are they eager to finally start federating with Twitter?
irc died and discord boomed because there was a user generation change. an explosion of new users eclipsed the few irc old timers.
discord is garbage any way you look at it. dont try to sell it as fixing irc. lol.
I never was on Twitter, but I am a Mastodon and Pixelfed user. I have zero interest in the cesspool that is Twitter joining the Fediverse and if they did I would probably instance block them.
This is about standards and my suspicion, that they want to keep all the control and profits, but now want to call it federated.
> The specification may be terrible
Have you read it ? I haven't, but it is working pretty well for the Fediverse. And once again: Standards aren't static, if you actually have a concrete problem with the standard instead of a gut feeling, that "it just sucks, don't ask about the details", then formulate it and bring it up to the creators of the spec or try to fix it yourself.
> IRC beat the 'the standard is just fine as it is' drum for many years
Well maybe that is the difference between IRC and ActivityPub. Nobody on the ActivityPub side is delusional enough to think the standard is perfect. There can pretty much by definition never be a perfect standard. There will always be use-cases that were not thought of during the creation. The solution is not to create one standard after the next, it is to improve existing ones. 1000 Standards are as useful as no standard.
The fact is that average users don't make any considerations about privacy/freedom/technical merit: they just jump on whatever is used by their own contacts. Nobody is using Mastodon because nobody is using Mastodon. It feels like one solution to that would be marketing. And given who is behind ATProto, they may have a shot at convincing many people to use their new shiny app.
https://blueskyweb.xyz/blog/10-18-2022-the-at-protocol
the appropriate place to develop protocols is within IETF, W3C, or other open groups which I'm absolutely sure Twitter could have played a role within.
Kind of discouraging to see this PBLLC doing things their own way.
The fact they even felt the need to create another protocol instead of using, improving and contributing to ActivityPub makes me think they want to bake a busines modell for themselves into the technology and they can't do that if they don't have full control over the spec.
ActivityPub is organically grown from a community to serve that community. Bluesky is created to combine making the profits of a commercial centralized social network + profiting from the investment from crypto bros.
ActivityPub is not perfect and nobody is pretending like it is (there is a big blog post from the co-author about what retrospectively they should have done differently, sadly I couldn't find the link), but a specification is not static ! If you have a suggestion to improve it you can propose changes and a lot of things are left to the implementation, so you can just do things differently than other ActivityPub application currently do.
In fact there are people building the future of the ActivityPub ecosystem right now: https://spritely.institute/
There is no need to create yet another specification. The only feature this claims to have, that all ActivityPub implementations currently don't have is identity portability and that can actually be implemented without changes to the ActivityPub spec, just no ActivityPub Application has implemented it yet.