silverpill@silverpill@mitra.social: @jupiter_rowland @valorzardI mean, @silverpill had to implement nomadic identity on Mitra client-side. That wouldn't be possible on MastodonI think they can do the same thing I did - rebuild server as a client. It would be a pain to package though, given that Mastodon is written in Ruby.

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @valorzard@mastodon.gamedev.place
Jupiter Rowland@jupiter_rowland@hub.netzgemeinde.eu (2026-04-21 02:32:27)
@ValorZard No dice.

First of all, implementing nomadic identity would drastically alter the way how Mastodon works. It would make Mastodon, something that's supposed to be dead-simple, a great deal more complex.

I mean, in order to really pull this through all the way (as in Hubzilla/(streams)/Forte-level nomadic identity), your identity, your posts, your followers, your followed, your settings, your filters, your everything, all this must no longer directly reside in your account. It must be containerised in something that Hubzilla calls "channel", and that container would then reside in your account and be able to reside in multiple accounts on multiple independent servers.

Next, when Mastodon introduces a new feature, they tend to try to market it as their own original pioneering invention. They can't do that with nomadic identity. There are already enough people who know that nomadic identity was actually pioneered by Hubzilla before Mastodon even existed.

Furthermore, before Gargron implements something invented by Mike Macgirvin, hell will freeze over. Even if he tried to sell it as a unique feature of Mastodon, he'd still secretly have to admit that there's something that Mike did right. And quite a few eyes would be on him in hope of Mastodon getting more features from stuff created by Mike.

Ever heard of OpenWebAuth magic sign-on? Invented by Mike for Osada and Zap in the late 2010s, then backported to Hubzilla.

It was proposed for Mastodon, even if it was only client-side (as in, Mastodon logins would be detected by Hubzilla, (streams) and Forte, but Mastodon wouldn't be able to detect OpenWebAuth logins itself). This went as far as a merge request on GitHub. It could have been built into Mastodon. The code was literally there.

The merge request was silently rejected. And that would have been a fairly small change in comparison to the complete rebuild that'd be necessary for a full-blown, Forte-level, server-side implementation of nomadic identity.
---Reply---
silverpill@silverpill@mitra.social (2026-04-21 23:25:33)
@jupiter_rowland @valorzardI mean, @silverpill had to implement nomadic identity on Mitra client-side. That wouldn't be possible on MastodonI think they can do the same thing I did - rebuild server as a client. It would be a pain to package though, given that Mastodon is written in Ruby.