Why #FediPact is important (1/3)

The #fediverse should all agree to never federate with #Facebook

#FediPact is an agreement between all current Mastodon instances to never federate with #Facebook, in response to the #Meta corporation's recent announcement that they will be making Facebook compatible with the #ActivityPub standard, and thus allow Mastodon and other ActivityPub services to federate with Facebook.

Most of the arguments I hear in favor of federating with Facebook come down to trying to expand the reach of the fediverse and Mastodon in particular. If people on Facebook can interact with Mastodon, this can only grow the fediverse and make it more relevant. This is a failure to recognize the real threat of Meta.

This pro-Facebook sentiment is usually accompanied by accusations of #FediPact supporters being irrationally dogmatic, overly paranoid about advertising and other for-profit ventures, overly concerned with privacy, and/or ignorant of how technology works. The attitude here is "Don't be so paranoid, just try it and you will see the benefits." This is a straw-man argument against #FediPact.

(1/3 continued)

#Mastodon #Kbin #Lemmy #Pixelfed #PeerTube #Fediverse #Facebook #Meta #FediPact

⁉️ Qual a treta com o #Facebook?

Bom, como todos sabem, a #Meta está vindo para o #fediverso e vai colocar o pezinho começando pelo #Instagram #Threads, que é similar ao #Twitter.

Como todos devem saber também, muita gente não vê com bons olhos a chegada do titio #Zuck por essas bandas, dado todo o histórico negativo e crises políticas, sociais <https://snowdin.town/objects/5447d3f9-de3b-45b7-a6ef-5001d3f766de> e de privacidade causadas pelo conglomerado norte-americano.

Que muitas #instâncias iam desfederar o Facebook no ato, muitos já sabiam. Tantos outros, porém, preferem pagar pra ver e assistir no que vai dar. Alguns acham isso ingênuo, dado o histórico da Meta, que não está no jogo para conviver pacificamente e sim dominar.

Mas enfim, hoje surgiram rumores de que alguns administradores de instâncias do fediverso foram convidados a conversar com a Meta, mas após assinarem um #NDA (Non-Disclosure Agreement). Ou seja, não poderiam falar sobre isso. Tudo na surdina, a portas fechadas, às escondidas, à boca pequena.

Verdade ou não, isso enfureceu ainda mais os admins do fediverso, pois mostra que coisa boa não vem por aí e confirma o pessimismo de muitos.

Disso surgiu um #pacto <https://vantaa.black/pact> para bloquear as redes da Meta no fediverso assim que ativarem a federação.

Update: @stux disse que de fato algumas instâncias foram contactadas, mas não para tratar de uma compra ou algo assim mas só para avisar que estavam chegando <https://mstdn.social/@stux/110567524159195690>.

Sometimes I wish I could go around, grab every single one of those who have joined since the #TwitterTakeover by the shoulders, shake them and tell them, now listen here, #MastodonIsNotTheFediverse. Tell them there's more to the #Fediverse than #Mastodon until they understand why my "toots" look so weird. Also tell them it isn't worth fighting for Mastodon to include certain features. There are more microblogging services in the Fediverse, and they all have these features already, and they all connect to Mastodon.

So you want quote-tweets? Stop pestering Eugen Rochko for including something in Mastodon which he firmly rejects. Go join e.g. #Akkoma instead, and you've got your quote-tweets. And you can always reconnect with all your Mastodon friends just the same as on Mastodon.

Many are positively surprised when they learn that. They've spent some four months in the Fediverse, thinking Mastodon is all there is to the Fediverse. It feels like a whole new world to be explored.

But I've come to the realisation that millions of Mastodon users don't want any of that. They don't want to know about other projects in the Fediverse. It confuses them. They've spent their entire online lives in monolithic, centralised, corporate data silos like #Facebook, #Instagram and #Twitter. It was hard enough to wrap their minds around Mastodon's decentralised architecture with lots of independent #instances, now called #servers.

All they wanted was a Twitter clone without #ElonMusk, but otherwise identical to Twitter. When someone showed them mastodon.social (which isn't even the official Mastodon website; this is), they expected to find just that. And then they first had to learn what instances are and afterwards choose one because mastodon.social didn't let them in. They're still shell-shocked from that. In fact, many of them still wish there were no instances, and Mastodon was a centralised silo like Twitter, for that'd make things easier.

Worse yet, there isn't that one fully-featured mobile app on Apple App Store and Google Play Store that bears the same name as the whole project. There is one, but it sucks, and everyone urges them to use a third-party app that isn't even named Mastodon. So they have to pick something again, and then they have to remember the name of their Mastodon app because it doesn't have "Mastodon" written under the icon.

And then folks like me come along and tell these people that the Fediverse is #NotOnlyMastodon. That some of the instances out there aren't on Mastodon, but parts of wholly different projects. Now, they've just gotten used to the Fediverse being decentral and made up of lots of independent instances of Mastodon. But then someone overthrows this hard-to-grasp world view once again by mentioning that it is, in fact, not only Mastodon that the Fediverse is made of. Worse yet, that someone starts rattling down name after name of other Fediverse projects.

Nope. Nope, nope, nope, nope, nope. That's too much. Too much information for someone who came to Mastodon expecting an iPhone app for another black-box internet platform.

Mastodon had just started feeling cosy to them. Well, except for too much #Linux and #FLOSS technobabble. And except for still being hard to use with all these instances and a lack-lustre official mobile app. In fact, except for this lack-lustre official mobile app being the only available iPhone app for Mastodon until recently because everyone only made apps for Android for reasons that don't belong here. They feel like they finally know the Fediverse, that they don't have to learn anything about it anymore, and they've come to love what they know.

But all of a sudden, all these other Fediverse projects burst into their lives. All at once. More nerdy tech information is being shoved down their throats. And the Fediverse doesn't feel the same anymore, now that they know that not everything is Mastodon.

Again, yes, some may look at me in curiosity, their chin resting on their palms, and say, "That's intriguing, tell me more!"

But many others reject this entirely. They cover their ears and go, "La la la la la, I don't want to hear it!" They're those people who speak of the Fediverse as if it's only Mastodon, whom you tell that the Fediverse is more than Mastodon, and who then continue speaking of the Fediverse as if it's only Mastodon. They want it to only be Mastodon because that's easier to understand, and they ignore everyone and everything that says otherwise.

Truth be told, they may have an additional justification. And that's the kind of people who are in the Fediverse, but not on Mastodon, and whose posts come "flooding" into Mastodon. Weeaboos, furries and other weirdos on #Pleroma. Worse tech geeks on #Akkoma and #CalcKey than even those on Mastodon. On top of that, even worse tech geeks in the shape of the "supremacist" old guard from #Friendica, #Hubzilla and #Streams who play key roles in all rallys against centralised services that'd make Mastodon easier to use for former Twitter users.

A closer look may reveal that all their projects are "unusable" for someone who is used to Mastodon, even more so for someone who freshly comes over from Twitter or Facebook. And yet, all of them even claim that what they use is better than Mastodon. Another reason to not like a not-only-Mastodon Fediverse.

Another reason, in fact, to want the Mastodon-only Fediverse "back" that never even existed in the first place.

However, you can't really protect these people from the parts of the Fediverse beyond Mastodon, even if you want to. For a user of something that isn't Mastodon, this is even more difficult. In particular, you can't pretend to them that you're on Mastodon when what comes out of your instance clearly doesn't look like it came from Mastodon. And I'm not necessarily only talking about character counts. You can't help but go on confusing them. That is, unless you want to sacrifice all the extra features of the project you use and move to Mastodon itself.

In all honesty, I expect a campaign for fediblocking everything that isn't Mastodon to emerge before the end of the year. And no, the campaigners won't want to hear that this is nigh-impossible. They'll want it to happen, no matter how.

Okay, so you're part of the #TwitterMigration. You wanted to get away from the #birdsite as it started to gradually turn into another Nazi hive after the #TwitterTakeover. Luckily, you've been pointed at the #Fediverse, i.e. #Mastodon. You go there with the following mindset:

• Mastodon is a 1:1 #Twitter clone, just without Elon Musk, but otherwise absolutely identical to Twitter. I mean, how could a microblogging service possibly be any different from Twitter? That's just as strange an idea as a desktop operating system that isn't exactly like Windows. Unless you're a Mac user, that is.
  
• Mastodon.social is Mastodon. Because that's the website you've been pointed at on Twitter.
  
• Also, the Fediverse = Mastodon. Only Mastodon.

Now you try to register an account on Mastodon. Which means on mastodon.social. And you discover you can't do that because registrations on mastodon.social are closed, because mastodon.social is full.

Either you can't be bothered to read what the pop-up says. Then your understanding is that Mastodon itself is full. And you're back at Twitter. Avoidable mistake; see right below.

Or you can be bothered to read what the pop-up says. Then you discover the blue button that takes you to a list of public Mastodon instances on the actual Mastodon website.

Um, instances? Servers? What the...? What's that?!

Okay, this'll be hard to wrap your mind around if the entire IT world has only consisted of commercial, corporate-owned walled gardens so far. Windows/macOS, iOS/manufacturer-provided Android, Microsoft Office, Photoshop, Adobe Reader, Internet Explorer/Edge/Safari/Google Chrome, Google Search, Google Maps, Amazon, Twitter, Facebook, Instagram, WhatsApp, Spotify, maybe iTunes, your Microsoft/Apple/Google cloud etc. You couldn't even imagine that alternatives to these exist, much less alternatives that don't belong to yet another U.S. gigacorporation. Or even alternatives that aren't as monolithic as these.

Mastodon feels like a revelation to you, an epiphany. All this commercial, corporate-owned stuff is, in fact, not the entire IT world. It's a bubble. And there's a world outside this bubble. And this outside world is strange.

For starters, Eugen Rochko is the core developer of Mastodon. And yes, he is also the admin of mastodon.social. But that does not make him the owner and overlord of the entirety of Mastodon, just like Elon Musk is the owner and overlord of Twitter.

Also because Mastodon is, in fact, not mastodon.social. Not only. Mastodon.social is only one out of many Mastodon servers or instances. Thousands of them. Literally. Those listed on the official website are only those recommended by "the makers" of Mastodon. Here are even more.

There are instances for all kinds of special interests. There are also instances for lots of places in the world. People have set up instances for cities; Chicago actually has two of these.

Mind-blowing, right?

Okay, so you still absolutely have to join mastodon.social because that's where people went whom you know from Twitter. You want to stay in contact with them. So you can't join a different instance.

Wait, wait, wait, calm down. You can. And you can still get back in contact with your acquaintances on mastodon.social.

Even more mind-blowing, right? How can this possibly work?

Well, I take it you use e-mail. You need an e-mail account to use Mastodon after all. Most likely, you're on Google Mail. Are all your e-mail contacts on Google Mail, too? Do you only ever receive mails from accounts on Google Mail? Does Facebook send mails from a Google Mail account?

No, Facebook doesn't send mails from a Google Mail account. Facebook runs its own mail service. And yet, Facebook's mails get through to your Google Mail account. And that has probably been perfectly normal for you.

This is made possible through a technological miracle known as "federation". Basically, all e-mail servers in the world can communicate with one another, send mails to one another, receive mails from one another.

It's the same with the Fediverse. After all, the "Fed" in "Fediverse" comes from "federation". Generally, all Mastodon instances can communicate with each other. Unless one instance has "defederated" (completely blocked) another instance. There are actually Mastodon instances which are defederated by most other public Mastodon instances. But otherwise, everything connects to everything.

Once you've joined an instance, you'll discover first-hand that you can, in fact, follow people who are on mastodon.social. Or just about any other instance, all without having accounts there.

There goes the second bullet point.

And the first one will quickly start to crumble, too. First of all, Mastodon looks nothing like Twitter. Also, everything is named differently. Tweets aren't named "tweets" but "toots". You don't retweet, you don't even "retoot", you "boost".

And Mastodon works quite a bit differently from Twitter.

• You've got three timelines. Next to your personal timeline which lists whatever your contacts have tooted or boosted, there's the local timeline which lists what the other users on your instance have tooted or boosted (this is how and why special interest instances or local instances make sense), and there's the federated timeline which is the local timeline plus what local users' contacts on other instances have tooted or boosted.
  There is, however, no timeline for the entire Fediverse.
  
• There's no full-text search for the entire Fediverse. Deal with it.
  
• There's no secret algorithm telling you what to read or whom to follow. All timelines are strictly chronological.
  
• This also means that there's no secret algorithm shoving your toots into other people's faces. If you want people to discover your toots, use #hashtags. On Twitter, hashtags are a gimmick. In the Fediverse, they're vital.
  
• There's a #newhere hashtag. It matters. As someone who is new here, you're expected to write an introduction, use the #newhere hashtag in it and then pin your introduction so that it's always on top or near the top of your personal timeline for others to read.
  
• There's no quote retweet. And there will never be. Eugen Rochko has a very strong opinion on that, he doesn't want that popular trolling tool on Mastodon, so this won't happen.
  
• Privacy settings per toot. You can choose who can read your toot. If you write threads, it's common practice to only set the first toot to public and all other ones to unlisted so that they don't clutter the public timelines.
  
• Delayed toots. You can choose when your toot goes out.
  
• Content warnings (CW) that blank out your toot. And yes, they're taken very seriously. People are likely to demand you use them when you don't.
  
• Alt-text for images. Again, people are likely to demand you create them when you don't. Some people on the Fediverse are blind and use screen readers, and they, too, want to know what that picture in your toot is.
  
• Not to mention that toots can be almost twice as long as tweets, namely 500 characters. Unless the owner of an instance has changed that number.

Speaking of the latter: As the first bullet point from the beginning crumbles to dust, the one about Mastodon being Twitter minus Elon Musk, you may have been rubbing your eyes in disbelief already.

How can I possibly write more than 500 characters in a toot? How can you write in italics on Mastodon? Or use lists with bullet points in a toot? Where on Mastodon are the buttons for that?

Well, you are right now having a glimpse at the Fediverse beyond Mastodon. As in: There is a Fediverse beyond Mastodon. The Fediverse is not only Mastodon. There are other projects out there which are federated with Mastodon just like Mastodon instances are federated with one another. This is possible because they speak one common language: #ActivityPub. And they're all decentralised themselves with multiple instances each. For example:

• Not all of them are "not Twitter clones", i.e. microblogging services. Pleroma is another one which was created out of disagreements with how Mastodon works. Akkoma is a Pleroma fork which came to exist because someone didn't like where Pleroma went. There's also Misskey. Obviously, they aren't "Mastodon clones" either, they were designed to be different from each other. And there's GNU social, the oldest one on the list.
  
• Pixelfed is "not an #Instagram clone".
  
• Friendica is definitely "not a #Facebook clone" because, while created for a similar purpose, it's still vastly different. And it federates with just about everything that moves including e-mail or WordPress. It even used to federate with Facebook itself eons ago. By the way, #Friendica makes everything possible that I've done in this post which is also why it's usually filed under "macroblogging". But I'm not on Friendica; I'll get to that. Also, Friendica is the second-oldest one on the list.
  
• Mobilizon is "not a #GoogleCalendar or #Doodle clone".
  
• Funkwhale is "not a #SoundCloud or #BandCamp or #Spotify clone", also because you're unlikely to find mainstream commercial music on it. Castopod: ditto, but specialising on podcasts.
  
• PeerTube is "not a #YouTube clone".
  
• Owncast is "not a #Twitch clone".
  
• Lemmy is "not a #Reddit or #HackerNews clone", although the "not a Reddit clone" part can be debated.
  
• WriteFreely and Plume are "not #Medium clones".
  
• BookWyrm is "not a #GoodReads clone".
  
• Flockingbird is "not a #LinkedIn clone" at all, also because rather than being a service of its own, it piggybacks on the rest of the Fediverse by picking up hashtags.
  
• Hubzilla was a successor to Friendica, but it's much more than "not a Facebook clone". It's also not a clone of whichever CMS and/or cloud service you use. It can provide you with your own personal organiser including a #CalDAV calendar (next to the public event calendar) and a #CardDAV addressbook, your own #WebDAV cloud space, your own online photo album, your own website, your own blog and/or your own wiki on top of just about everything that Friendica does. It's the third-oldest on the list and still older than Mastodon.
  
• And there's much more.

Thanks to ActivityPub, these services are federated with Mastodon which means that you can follow their users from your Mastodon account. You don't necessarily need accounts on these services. Okay, you need them to fully make use of them. You can't start discussions on #Lemmy or upload videos to #PeerTube without having an account there, but you can follow and comment on PeerTube channels and reply to discussions on Lemmy from your Mastodon account.

Want proof? Well, this post came from a #Hubzilla channel. You can still read it on Mastodon. And if you reply to it, I can still see it on Hubzilla.

And there went the misconception that the Fediverse is only Mastodon.

Stay tuned until next time when I explain to you how "Facebook's #Metaverse" (it's called #HorizonWorlds, in case you don't know) is not and will never be #TheMetaverse, and that free, open-source, (largely) non-commercial, decentral #VirtualWorlds exist already now.

Obligatory hashtags: #Pleroma #Akkoma #MissKey #Pixelfed #Mobilizon #Funkwhale #PeerTube #Owncast #Lemmy #WriteFreely #Plume #Flockingbird

Allow me to digress from the usual topic on this channel once more.

I'm pretty sure that no human being on this planet has created nearly as many federated social platforms as @mike. But all these (actually not always so) different platforms can be a bit confusing. Even I may be wrong here and there, but I'll try to make some sense of them by putting them into a kind of chronology.


So first, there was #Friendica. Only that it started out under the name of #Mistpark. I'll get to the name later.

Remember #Diaspora? Remember summer 2010 when the crowdfunding run was launched so that those four guys could spend all their time creating a free, #OpenSource, decentralised, federated social network (a.k.a. #Facebook killer) which they wanted to name Diaspora*?

Well, they unknowingly wanted to re-invent the wheel. #StatusNet was already there, #GNUsocial was already there, and especially, Mistpark was already there with a 1.x release and more powerful than both, actually, more powerful than Diaspora would ever become. I think Mistpark even already had Diaspora*'s aspects, only that they were called groups.

As for its concept, Mistpark went beyond that of Diaspora*. Mistpark didn't only want a bunch of instances ("nodes" in this case) of its own kind to connect with one another, it also wanted to federate with everything else that moved, be it e-mail, be it StatusNet, be it Twitter, be it whatever.

The first name change was from Mistpark to #Friendika. The reason was that the original name sounded repelling to German speakers. "Mist" means "fog" in English, but "dung" or "manure" in German, not to mention that it's a German curse word.

When Diaspora* was finally there, Friendika didn't see it as competition, it saw it as another federation target. To this day, Friendica is fully federated with Diaspora*, and that has exclusively been the work of the Friendika developers who studied Diaspora*'s source code and reverse-engineer it because it didn't have an API.

Probably the biggest coup was the bidirectional federation with Facebook. This was what everyone was waiting for. This, however, was also where the trouble started. Facebook didn't want to be federated with a non-commercial social network and started taking defensive measures. Also, Friendica users (the second name change was through meanwhile) who used the Facebook connector had their entire and often very busy Facebook timelines mirrored onto Friendica nodes, one of the reasons why even nodes on powerful root servers often had to close new registrations even though they only had a little over a hundred users. So there were several reasons why Facebook federation was axed again.

Internally, Friendica uses its own protocol named #DFRN. But I guess Mike had meanwhile seen it as a dead end, also because he had a new idea: #NomadicIdentity, not only the ability to easily take your account from one instance to another, but the possibility to have it on multiple instances at the same time, keeping the copies in sync.

That's why he laid the foundation for a new protocol that could do that: #Zot.


And with it came the next social platform. It was first just simply named Red from Spanish "red" = "net". Red was based on Zot from the beginning, and as an experimental platform, it only understood Zot. On Friendica which was now running at full steam on dozens upon dozens of nodes, and which Mike had passed on to the community, the development was followed with interest. And just like later platforms, I think Red actually got a few small public instances because someone really wanted to try it out. Red eventually changed its name to #RedMatrix.

Also, Red didn't just want to be a social network like Friendica. The idea was rather to have a "social content management system" that could do just about everything you could do with a website and/or a cloud server. Third-party federation was slightly reduced, connections to commercial platforms didn't come back. But as Red evolved, the Diaspora* connector was included which was also used to federate Red with Friendica.


From the Red Matrix emerged #Hubzilla, the Swiss Army knife of the #Fediverse. Still today, its possibilities have rarely ever been fleshed out: not only microblogging, but macroblogging, article publication, websites, wikis (no, I'm not kidding), #WebDAV, #CalDAV and #CardDAV server and so forth.

Next to the nomadic identity that came with Zot, Hubzilla introduced another killer feature: one account, many separate channels. Each one of these channels is basically like one Friendica account. You can have multiple fully separate identities on one account, and nobody (except the instance admin) can tell that they're all you. So this goes way beyond Friendica's multiple profiles. By the way, Hubzilla still has multiple profiles per channel.

Some say that the Red Matrix was renamed Hubzilla. This isn't true. Hubzilla is a fork of the Red Matrix, one could say it was a stable snapshot of the Red Matrix.

For the development of the Red Matrix continued. Planned advancements on Zot couldn't be tested on stable Hubzilla, they needed their own testbed. Eventually, the last Red Matrix instance was Mike's personal one with himself as the only user. It still federated with Friendica and, of course, Hubzilla.

In the meantime, #ActivityPub came along. It wasn't just another obscure networking protocol, though, because #Mastodon made it huge. So at least Friendica and Hubzilla had to adopt it. Friendica firmly integrated it. Hubzilla made it into an app just like all other protocols that aren't Zot because they stand in the way of fully nomadic identity. By the way, both profited from its introduction because the federation between each other no longer had to use the Diaspora* protocol.


For the next advancements of Zot, two new platforms were forked from the Red Matrix or Hubzilla. At this point, Mike wasn't involved with Hubzilla anymore either. First, there was #Osada, an early testbed for what would become #Zot6, but still with ActivityPub. For pure Zot6, #Zap followed suit. Most connectors that are neither Zot nor ActivityPub, including the one to Diaspora*, weren't taken over, as were many of Hubzilla's extra abilities (websites, articles, wiki, CardDAV, two parallel calendar systems etc.) to keep it slim. It did get to keep the various types of channels as well as one CalDAV server and the WebDAV connection, though.

Eventually, when Mike handed them over to the community, they used the exact same code base. The only differences between Osada and Zap was whether or not the admin had ActivityPub on (Osada) or off (Zap) and the name.

As having two different names for the same thing, depending on the instance configuration, Osada was discontinued in favour of Zap which now included ActivityPub itself. In the meantime, Zot6 became stable and was backported into Hubzilla which thereby became fully compatible to Zap, only that what Hubzilla can that Zap can't cannot be mirrored to Zap.

Then Osada re-emerged as Zap's unstable branch. Along with it came a new Red Matrix which, as far as I could see, was now an even more purist, even more unstable branch that only served for testing Zot8 and lacked all other protocols.

To top this off, in 2020, Zap itself got a stable branch even more intended for productive use. For this purpose, the name Mistpark was dusted off. The new stable branch was named #Mistpark2020 or simply #Misty. Misty was the first of its kind to not even get an announcement anymore, though. Its home page on Zotlabs disappeared along with Zotlabs before it could be filled with any useful information.

Two things were interesting: Red Matrix, Osada, Zap and Misty were based on various states of the same code base. It was possible to switch from one to another by rebasing the local code repository on your server. This became obvious through instances that carry the name of one project but run another one.


It must have been in 2021 when #Roadhouse showed up, again, unannounced. It seemed to be nothing more than a concept for the next generation of distributed social platforms. Roadhouse was the first of its kind to use the #Nomad protocol which, I guess, is forked from #Zot because it serves the same purpose. It got its own home page on Zotlabs which remained as uninformational as Misty's.


And then the most recent name popped up: #Streams. At first, it was even less clear what Streams was supposed to be and what set it apart from Roadhouse, not to mention Red Matrix, Osada, Zap and Misty, also because Zotlabs didn't say what Streams was either.

But I guess Streams' purpose has emerged in the meantime through word-of-mouth: It's the experimental successor of all five and the solution to this maze of names. Streams isn't even a product with a name, it's a concept that uses Nomad for nomadic identity and that is in constant flux, hence Streams. The idea was to do away with fixed names to get rid of the previous chaos. Everyone can name whatever they do with Streams however they want.

There is currently only one more or less public Streams instance, but it still carries "Stream" in its name. At least two more instances which may be private are named something with "Streams", too. So whether Mike wants or not, Streams has become a name of its own, and people use it.

How many Streams instances exactly exist right now is hard to tell, even from Communities pages on Streams instances or Sites pages on older platforms, because they don't necessarily identify themselves as Streams instances. So if you go through one of these pages, and there are names in the Projects column which you don't know as Fediverse platforms, check out what's behind them. It's often only one instance. Open the instance, click its burger menu, and if there's a Communities link, it's a Streams instance. I've discovered a lot of Streams instances not named anything with Streams this way. Private instances included, I guess Streams must have more than a dozen instances already.

There has even already been a request to launch a Streams support forum much like the one for Hubzilla; after all, Streams still supports forums. It's safe to say that Streams is doing quite well for something so obscure.

Feature-wise, Streams is the same as Zap and Misty.


But what became of the six platforms between Hubzilla and Streams?

• Red Matrix kept having only this one single-user instance because nobody else dared to touch it and set up another instance. It's a Zap instance now as far as I can see.
  
• Osada never really took off, Zap probably did only after Osada was merged into it, and some Osada instances became Zap instances. This explains why Zap has got comparably many instances. Most of them, however, are tiny, probably private and utterly undermaintained as they run rather old Zap versions. Zap only lives by numbers, and it's the only one of the five listed on Fediverse Observer. Also, while the FediDB lists all five, it only knows that one Dominican public Zap instance and none of the others (looking through its connected sites reveals many unlisted instances of Zot-based networks, by the way). Still, it seems to be on the deathbed, being superseded by Streams, experimental as the latter may be.
  There still seem to be a very few running Osada instances, but Osada can be considered dead as the focus is on Streams now.
  
• Misty didn't take off either, even though it was considered more stable and more production-grade than Zap. This time, the reason may simply be because Misty got zero advertising, so nobody heard about it, probably not even some of the Zap crowd. Misty never had many instances, they weren't properly advertised either (the same applies to most Zap instances, by the way), and Misty's death knell may have been the unannounced shutdown of its largest instance. Basically, there was little room for Misty next to less obscure Zap.
  
• Roadhouse didn't even manage to get much limelight before Streams appeared shortly afterwards. In both cases, the only way to find out what they were and what they did was by either studying the source code or installing a private instance. Streams, however, had the advantage of being even newer. The-Federation.info knows exactly one German Roadhouse instance which was originally set up as Misty and has meanwhile been upgraded beyond Roadhouse to Streams, and there only seems to be one remaining unlisted Roadhouse instance.
  
• I've seen another result of an upgrade from Zap to Misty. So it's safe to assume that you can upgrade all five to Streams. If this is the case, then now that Streams is here, it probably isn't worth spreading the developer community across six almost identical platforms. Basically, Streams has become the latest version of Red Matrix, Osada, Zap, Misty and Roadhouse.
  
• At least Red Matrix, Osada, Zap and Misty are still being maintained in a sense, though. All four got the same small Git commit from Mike a good month ago. Roadhouse got one four months ago.

As of now, Friendica is still going strong, so is Hubzilla, and Streams seems to be cleaning up the mess that came after Hubzilla.

If you really want to try out something with Zot, my current recommendation is Hubzilla, even if it may seem bloated and cumbersome to you, even if you'll never harness its full power. Many of its extra functions are additional apps and switched off by default; this includes ActivityPub, by the way, this is important to know.

It's hard to find a public Streams instance with open registrations currently, much less multiple ones that'd be required for a nomadic identity. Neither Fediverse.party nor the FediDB nor The-Federation.info nor Fediverse.info even knows Streams, and existing Streams instances usually don't identify to other Fediverse servers as Streams instances. It's still a rather underground and grass-roots project with no publicity at all. As Streams is rather experimental, however, you may want a nomadic home on at least two instances to have an instant backup, should one of them shut down.

Zap has got exactly one instance open to the public, and seeing as Zap may be shrinking rather than growing, I don't expect this to change. Again, due to Zap's still small size and unclear future, I wouldn't recommend using it without nomadic identity as a safety net.

As for Osada or Misty, good luck finding an instance to join, much less one that's here to stay and ideally be upgraded to Streams one day.

Hubzilla may not be as bleeding-edge as Streams, and it may be overkill for your purposes if Zap or Streams would be sufficient, but it's stable, it's big enough, it's established, and it's different enough from Streams to not be endangered by it. I mean, Hubzilla hasn't managed to kill off Friendica either, right?

I keep thinking about a couple #Twitter threads criticizing #Mastodon (the #Fediverse, really) for being inherently different than closed commercial platforms using far-fetched hypotheticals and extraordinary occurrences; while I do not want to make a useless point-by-point response, instead I'll tell you what I like about federated social media and #Friendica in particular.

After #Facebook froze my account for using a pseudonym (a spottily enforced rule), I started hosting my own #Diaspora pod because I could.

I didn't know anyone so I initially made contacts with other podmins and progressively extended my circle through shared posts. This is how I learned about #Friendica, a platform that was compatible with both #Diaspora and #OStatus (#GNUSocial, #StatusNet ) because it could.

Written in #PHP, liked both the multi-protocol approach and that I could contribute code to it. So I started hosting my #Friendica node and I kept following the same Diaspora accounts, because I could.

When #Mastodon was first released based on OStatus, I started following several accounts on there because I could. When #ActivityPub was released and supported by Mastodon, we followed suite a few months later, because we could.

With popularity came the right-wing trolls and free speech extremists who organized their own federated instances, but they never bothered me much as I blocked their entire instance domains because I could.

None of these are currently possible with commercial platforms. Not all people will end up hosting their own node and it's fine, but the breadth of possibility is what makes federated social network attractive.