Imagine being able to post only to Alice, Bob and Carol and nobody else ever laying their eyes on the post. Not in the Fediverse, not outside the Fediverse.

Imagine only Alice, Bob and Carol being able to reply to your posts, but all three being able to see and reply to each other’s replies.

Imagine being able to define groups of connections with which you can do the above.

Sounds like utopian science-fiction. Is reality.

Hubzilla (official website), a Friendica fork by Friendica’s own creator, offers literally what I’ve described above. It has since 2012, almost four years longer than Mastodon has been around.

If you want something more lightweight with not quite such a steep learning curve, there’s also (streams) (code repository from 2021 from the same creator, the result of a whole series of forks. Similar advanced and fine-grained permissions system, but somewhat easier to use.

Common misconception by Fediverse newbies: “Fediverse” is an umbrella term for a bunch of decentralised walled gardens. Like, Lemmy only connects to Lemmy, Mastodon only connects to Mastodon, Pixelfed only connects to Pixelfed etc. And if you’re on Mastodon, and your Facebook friends join Friendica, you need a Friendica account to get back in touch with them.

In reality, just about everything is interconnected with everything. No matter what it is.

You can use your Mastodon account to follow people on Pixelfed, on Friendica, on Misskey, whatever.

That said, having a separate Lemmy account makes sense because Lemmy/the Threadiverse is somewhat special in operation. Also, it’s all about conversations and groups, and Mastodon doesn’t understand neither. And starting a thread on Lemmy from Mastodon is not as straight-forward as starting a thread on Mastodon from Mastodon.

The closest you’d get would be with Hubzilla or (streams). Or Forte if it wasn’t experimental with no public instances yet. They even have file spaces with WebDAV on which you can upload files and then define who is permitted to see/access these files or the folders they’re in.

However:

What you want isn’t their default M.O. You’ll have to get used to and think yourself into something with a learning curve that’s even steeper than Friendica’s. You’ll have to learn and understand the permissions system, including giving nobody permission to see your connections. Ideally, all your connections would have to be smart enough to know how to to hide being connected to you from the public and to actually do so.

Encryption is optional and “uninstalled” by default for everyone, and it isn’t even available on all server instances (it’s up to the admin to activate that add-on, and then the user has to activate it, too). Also, it uses passphrases and not automatically generated key pairs.

Finally, if you insist in using it with a mobile app, you’re completely out of luck. It’s browser or PWA for all of them.

What really needs contributors are the streams repository and probably also Forte. They’re very powerful, they’re highly advanced, they’re secure and resilient, they’re basically what the whole Fediverse should be like, and they can blow not only Mastodon out of the water, but also Pleroma, Misskey and all their forks. But they only have half a maintainer at best because their creator has officially retired.

Allow me to elaborate:

These are the youngest offspring of a family of roughly Facebook-like Fediverse server applications created by Mike Macgirvin. They started in 2010 with Mistpark, later Friendika, now known as Friendica. The focus has never been on aping the UI/UX of something commercial and centralised, like Lemmy apes Reddit, but to create a replacement that’s actually better. Toss out stuff that sucks, add features that could be useful like full-blown blogging capability, including blogging-level text formatting, and a built-in file space with its own file manager.

The next in the family was a 2012 Friendica fork originally named Red that introduced the concept of nomadic identity. As of now, and outside developer instances, nomadic identity is a feature exclusive to Mike’s creations. Red became the Red Matrix, and in 2015, it was renamed and redesigned into Hubzilla, a “decentralised social CMS” and the Fediverse’s biggest feature monster.

What followed was a whole bunch of forks, mostly development forks, only one of which was officially declared stable. This led to the creation of the streams repository in October, 2021. It’s a fork of a fork of three forks of a fork (of a fork?) of Hubzilla, but the first fork already lost many of Hubzilla’s extra features and a lot of Hubzilla’s connectivity.

The streams repository contains a Fediverse server application that is officially and intentionally nameless and brandless (“streams” is the name of the repository, not the name of the application), that is not a product, that is not a project, and that is just as intentionally released into the public domain, save for 3rd-party contributions inherited from Hubzilla that are under various free licenses.

While (streams), as it is colloquially called, may not have Hubzilla’s wealth of features, it has to be one of the two most advanced pieces of Fediverse software out there. With its permissions system that is even improved over Hubzilla’s, hardly anything can match it in safety, security and privacy. On top comes resilience through nomadic identity. Also, (streams) is more adapted to a Fediverse that’s driven by ActivityPub and dominated by Mastodon whereas Hubzilla seems stuck in the mid-2010s in some regards.

At this point, it should be mentioned that while Friendica, Hubzilla and (streams) can communicate through ActivityPub, none of them is based on it. AFAIK, Friendica is still based on its own protocol, DFRN, which is used by nothing else. Hubzilla is based on an older version of the Nomad protocol known as Zot6. (streams) is based on the current version of Nomad and also understands Zot6 for the best possible connectivity with Hubzilla.

So one of the latest development goals for the streams repository was the introduction of nomadic identity via ActivityPub, a concept that first appeared in 2023. I’m not sure how far this has been developed. But Mike created a new (streams) fork named Forte in August this year which had all support for non-ActivityPub protocols removed, probably also to cut down the maze of ID for everything which blew up on (streams) when support for FEP-ef61 was pushed to the release branch in July. Also, Forte has a name, it has a brand, it has a license, it has fully functional nodeinfo, and it is a project. Otherwise, Forte is identical to (streams).

Currently, there is only one Forte instance with one user, and that’s Mike’s private channel which mostly only his friends know about. Forte can be considered very experimental at this point, at least until Mike declares it ready for prime-time. After all, Forte has to handle nomadic identity via ActivityPub which, so far, is only proven to work under developer lab conditions at best.

However, there isn’t much going on in terms of development. After the hassle that was getting malfunctioning (streams) back on track this summer, Mike officially retired from Fediverse development at the turn from August to September. He hasn’t quit entirely, but he only works on (streams) and Forte sparsely. At the same time, the (streams) community was and still is too small to have a willing and able developer amongst themselves, and Forte has no community.

According to Mike, Forte could (and should) be “the Fediverse of 2030”. It only needs more people working on it.

And what do you know, HUGO was bolted to Hubzilla.

Not more than mentioned in that thread.

But I guess the cat’s out the bag, it’s known that this is doable, so maybe this won’t stay the only time.

That, and/or people might bolt other stuff to Hubzilla.

A lot is going on in and around Hubzilla recently. Version 9.4 has only been released a couple of weeks ago, and it already got four bugfix releases. We might actually be approaching Hubzilla 10 in the not-so-distant future which will adopt a few features from (streams).

Scott M. Stolz is back at developing his new third-party themes which we expect to improve Hubzilla’s UX. On top of that, he plans to launch a bunch of new public hubs, also so aspiring users in North America won’t have to resort to overseas hubs.

The re-writing of Hubzilla’s entire help in German and English is on-going.

Most recent surprise: Someone has managed to integrate the Bandcamp alternative Faircamp into a Hubzilla channel.

If only (streams) had more people taking care of it…

Also, let Mastodon shrink if that means that the “market share” of other native Fediverse server apps grows.

The fewer people think the Fediverse is Mastodon, and the more exposure the other stuff in the Fediverse gets and what features it has over Mastodon, the better.

Mastodon wasn’t launched by a VC-backed Silicon Valley startup to become the phone app that replaces Twitter.

It was created by a German high school graduate and metalhead all alone as not much more than StatusNet with a different UI and some features cut for simplicity. It was designed by a nerd for nerds, nerds who didn’t rely on phone apps for everything. At this level, and back in 2016, not even an official native iPhone app was mandatory.

Luckily, Mastodon is working on a discorvery protocol that should offer a way to find people across the board, which will hopefully make the Fediverse “appear” centralized to the average Joe while maintaining all the benefits of decentralization to the advanced users.

I’d bet that this will be so proprietary and non-standard again that it’ll only work within Mastodon, maybe plus a few of its own soft-forks, effectively ignoring 30% of the Fediverse.

Decentralisation and having multiple instances isn’t even that much of an issue. 99.999% of all Twitter refugees were railroaded to Mastodon and what seems like 99% of these straight to mastodon.social. They genuinely thought mastodon.social was “the Mastodon website”, just like twitter.com was the Twitter website. It took many of them months to even notice that Mastodon is decentralised. And it took some of them even longer to notice that the Fediverse is, in fact, more than just Mastodon while half of them think that Fediverse = Mastodon after almost two years.

No, the biggest issue is: What they were looking for was not something radically different from Twitter, now that Twitter sucked. They were looking for a Twitter without Musk. Like, a drop-in replacement that doesn’t require them to adjust in any way. A 1:1, 100% identical clone of Twitter how it was the day before Musk took over with the same UI and the same UX and the same culture.

When they were railroaded to mastodon.social, they were told that Mastodon is “literally Twitter without Musk”. And they took it as literally. By face value. And then they ended up on something that looked and felt nothing like Twitter. No matter how many of Twitter’s limitations Gargron arbitrarily and unnecessarily implemented into Mastodon, he never got close enough to Twitter itself.

People would stick around because Mastodon felt like the only alternative to Twitter there was. Of course, they kept using Mastodon exactly like Twitter, not adopting to Mastodon’s culture and relying on their toots being delivered to people by an algorithm that Mastodon simply doesn’t have. Hashtag? Fuck hashtags, I didn’t need no hashtags on Twitter, so I ain’t gonna use none on Mastodon. And then they wondered why so few people discovered them and their content.

They didn’t want to adapt. They were waiting for Mastodon to finally “fix the bugs” that made it different from Twitter. Which it didn’t.

Instead, Mastodon developed its own culture (which is a story of its own). And they were pressured to adopt Mastodon’s culture. CWs for sensitive content for any definition of “sensitive”. Twitter ain’t got no CW field. Alt-texts for all images, and it had to be actually useful and informative. They ain’t never done no alt-texts on Twitter. Of course, the right hashtags. See above.

Also, Mastodon-the-app is lack-lustre. Whereas the official apps for just about everything else are fully-featured, the Mastodon mobile app is only there for there to be a mobile app named “Mastodon” for those people who join a new online service by grabbing their iPhones and loading the app with the same name as the service from the App Store. Especially newbies often can’t wrap their minds around using an online service with an app that doesn’t have the same name. But the official Mastodon app is actually just about the worst Mastodon app out there. At the same time, for many Mastodon users, this app IS Mastodon. They’ve never seen the Web interface. What the app can’t do, Mastodon can’t do.

Lastly, Mastodon was probably also way too techy. Like, you had people talking about Linux and Open Source and Web design and whatnot all over the place, something that they themselves knew nothing about and weren’t interested in. On top came those people with their weird-looking monster posts that said the Fediverse is not only Mastodon, and they were posting from something that is not and has never even been affiliated with Mastodon.

And then Bluesky came along. And Bluesky looked exactly like what they’ve been wanting all the time: a 1:1 Twitter clone. One big reason for Bluesky’s success is that it shamelessly ripped off the UI of immediately-pre-Musk-takeover Twitter, both the website and the mobile app. A fully-featured, well-polished mobile app with all the same features as the website. And at first glance, it feels like the same monolithic walled-garden silo as Twitter with the same kinds of users as Twitter, minus the Nazis. At least not as ripe with übergeeks as Mastodon.

Also, Bluesky grew faster and quickly had more users than Mastodon. Which sounded like more followers in less time. Exactly what all those famewhores that brag about their Twitter follower counts were craving.

People wanted a pre-Musk Twitter clone. Mastodon isn’t one. Everything else in the Fediverse is one even less. Bluesky is just that. Bluesky is what people had wanted all the time.

The six accounts of the Confederation had around 3,500 subscribers in total. Seriously, what did they expect?

As many followers as they’ve built up in the Birdcage? With maybe 1% of users altogether? In a much shorter timespan?

And by running the accounts as pure shoutboxes with no interaction with replies that could just as well be unmarked crossposter bots?

No time to run and moderate it. I’m not primarily a Lemmy user, I’m mostly on Hubzilla and (streams). It can happen that I’m absent from Lemmy for weeks.