I don’t like the clickbait title at all – Mastodon’s clearly going to survive, at least for the forseeable future, and it wouldn’t surprise me if it outlives Xitter.
Still, Mastodon is struggling; most of the people who checkd it out in the November 2022 surge (or the smaller June 2023 surge) didn’t stick around, and numbers have been steadily declining for the last year. The author makes some good points, and some of the comments are excellent.
@thenexusofprivacy So, I’ve just kinda got a stream of random tidbits here that’ll hopefully sorta surmise my thoughts.
The good:
First off, it’s shrunk but it’s by no means dead. Things grow and shrink and grow again, if it was a straight line with no variation I’d assume it was fake.
Also, Mastodon is not all of activity pub. Threads has brought a lot if people onto the protocol, and while it’s still in development it seems to be intended to work interoperably and the devs said they plan to let people migrate out and take their following/followers with them. I expect this to really supercharge the ecosystem.
The indifferent:
This isn’t 2020 anymore, and there’s more protocols out there. Nostr, in my opinion, is leagues better in the decentralization and user options/customizations department. AT (Bluesky) is leagues better in the end user was of use department. Both of those protocols are also much, much, lighter to host.
Activity pub also has it’s advantages of course. Being the oldest and also being great for communities are two quite big ones.
Some people have chosen to either leave Activity Pub for those protocols, or joined the decentralized ecosystem directly into one of the other two. It’s indifferent, though, because it’s a decentralized ecosystem. All three can chat with each other, so Mastodon & Activity Pub may have shrunk - but the amount of people you can communicate with on them has risen exponentially thanks to bridges.
The ugly:
Federation is a mess. You can have a dozen friends on Activity Pub, a dozen on other protocols connected via bridges or threads and find you can only talk to two or three. That’s a problem; most would give up before understanding why, and many more would likely figure out why and the decide it’s not worth their time working around. After the Bluesky wave I’ve heard Mastodon be called some variation of “bickering fiefs” a couple dozen times.
There’s also some toxicity within the space. Most people I’ve interacted with have been great, but it still rears it’s head now and then. You can get nearly bullied off the platform if you suggest people be nice to Windows users. It was kinda funny to see that blog post shortly after I jokingly said “you guys would probably put a hit out on me if I said I was using Windows” in a similar thread. In a similar vein, while accessibility is great, I’d bet more people have left the protocol after being yelled at for not using alt text then there are users who rely on alt text.
My predictions:
I’d bet that all three protocols grow a lot in the future and that more platforms start integrating one or more of the three big protocols. It’s a cheat code for new platforms to automatically have a bunch of content, and it’s free platform software already built. Federation issues and fediverse specific toxicity issues will potentially be eternal septembered away. Most people won’t care what OS you use and will want to be able to talk to their friends as apposed to having current federation. There might be a small splinter group of the older crowd using opt-in federation, but most of the ecosystem will change if it grows.
I’d also bet the three big protocols will continue to get closer. All three can already communicate, and heck, I, as an incompitant programmer, made a quick script that lets any Nostr client communicate with Mastodon &/or Bluesky. Throw some compitant devs at it and soon enough you probably won’t even be able to tell at first glance what protocol the other person you’re communicating with is on. Bluesky and Nostr in the mix bring Mastodon’s ~800k monthly active users to like ~15 million. A more connected ecosystem make things better for everyone.
Do you mind linking your script?
@dameoutlaw Sure
github.com/0n4t3/nipy-bridge
Readme is overdue to actually be finished, but the script itself is working. Can be run locally on desktop or termux, though some clients on desktop need a custom host added since they don’t like localhost and amethyst only uses it if you don’t add it as a local relay.
Re blue sky, is anyone actually federating with it? I don’t know of any other instances besides the official one.
@ColonelThirtyTwo Sorta/mostly. The protocol has a bit of a different model then Activity Pub, and it’s in development so there are some limitations, but it’s been opened and there’s people hosting their own PDSs now (the part of Bluesky that hosts your account).
To my knowledge there’s only two AT relays (the part that aggregates content from PDSs), Bluesky itself and very recently frontpage (a link aggregator). That makes the network fairly centralized right now, although BlueSky/AT has made a lot of progress in the last 9 months in terms of opening up so I expect it’ll be a lot less centralized this time next year. I’m also betting that somebody will make an AT client that pulls posts directly from PDSs instead of going through a relay at some point.
Yes but no. Due to architectural differences, federation under AuthTransfer protocol is simply different compared to ActivityPub. In its own terms it is federated as individuals’ data is stored in personal data servers (PDSs) connected to a relay, which currently is only the Bluesky relay, that roughly speaking connects them to other personal data servers.
You can technically operate your own personal data server apart from those operated by Bluesky, but I think it’s fair to say the vast majority on there don’t. It’s not clear yet, apart from fully holding your own data, how useful it is to operate your own given you only have one relay to use anyway at the moment.
So even in its own terms Bluesky really isn’t federated in much of a meaningful sense yet. The problems are twofold: a major part of their pitch is making federation Just Work™, keeping the underlying tech out of mind to mitigate confusion, but you can’t have your cake and eat it too here. Eventually, if you’re really committed to meaningful federation, you have to teach people about the value of operating their own personal data servers, at minimum, otherwise what was the point in separating it out in the architecture?
Problem is, that goes against their pitch to their audience and spoils the appeal. It’s telling a good joke only to kill it by explaining to the one person that went, “I don’t get it.”
Secondly, they’ve already upfront said that relays may be cost prohibitive for many people to operate, resulting in only a few ever being spun up. If that remains the case and is true, then even if a few were spun up, that’s not any more federated or distributed than the rather consolidated web we see now. How much of a difference would it make if the social web was running on AuthTransfer and the major relays were owned and run by Meta/Facebook, Twitter/X, and Google?
Congrats you have your own data in a personal data server…But are you really the one running it, or did you just opt into the PDS entryway offered by Facebook/Twitter/Google/etc. because sorry, what’s that about a server?
Yeah, right now the way I think of it is that Bluesky is (conceptualy) a single big instance, connected to the rest of the ActivityPub fediverse via Bridgy Fed (which speaks both AT and ActivityPub). Bluesky’s decentralized in a different way, and the broader ATmosphere (apps that use AT protocol) is growing as well, but it deosn’t really have the same concept of instance.
Good points! Agreed very much about all protocols growing, and that the ActivityPub fediverse is broader than just Mastodon.