Comment on Nomad-capable server for an NGO
jupiter_rowland@hub.netzgemeinde.eu@hub.netzgemeinde.eu 20 hours ago @Jakub Urbanowicz Mastodon users would cheer if they got nomadic identity. Maybe unless it made things significantly more difficult for them because their identity was channelised.
Mastodon developers, however, would only implement nomadic identity under pressure, if at all. That pressure would be most of the rest of the Fediverse being nomadic and at least one nomadic microblogging/social networking application offering a fairly easy import of Mastodon accounts.
They would only implement nomadic identity if people started running away from Mastodon because it doesn't have nomadic identity. In all other cases, they'd refuse to implement it, at least pan-Fediverse nomadic identity, out of fear that Mastodon users would run away from Mastodon because it's so easy now. If anything, they'd implement nomadic identity in a way that still makes it impossible to move or clone from Mastodon to elsewhere.
But they probably wouldn't implement it if they didn't have to. After all, they refused to implement client-side OpenWebAuth support as well. There's literally a merge request on Mastodon's GitHub that'd implement client-side OpenWebAuth support, and that has been lingering since 2023, completely ignored by the devs. Back then, one merge would have been sufficient to give Mastodon client-side OpenWebAuth support.
So much about whether the Mastodon devs are willing to implement something that Mike Macgirvin has invented. Especially if they can't sell it to their faithful followers as their own original invention, and if they can't sell it to their faithful followers without admitting that there's something else than Mastodon out there in the Fediverse.
But even if Mastodon's devs wanted to implement full server-side nomadic identity, that doesn't mean it'll be easy. Basically, large parts of Mastodon's server backend would have to be rewritten. I guess this is why silverpill threw in the towel, gave up trying to implement nomadic identity on Mitra server-side and built a nomadic client instead.
There is no case of Hubzilla-level nomadic identity having been implemented in non-nomadic, ActivityPub-only, login-equals-identity Fediverse software after the fact. And there won't be any for quite a while.
Mastodon developers, however, would only implement nomadic identity under pressure, if at all. That pressure would be most of the rest of the Fediverse being nomadic and at least one nomadic microblogging/social networking application offering a fairly easy import of Mastodon accounts.
They would only implement nomadic identity if people started running away from Mastodon because it doesn't have nomadic identity. In all other cases, they'd refuse to implement it, at least pan-Fediverse nomadic identity, out of fear that Mastodon users would run away from Mastodon because it's so easy now. If anything, they'd implement nomadic identity in a way that still makes it impossible to move or clone from Mastodon to elsewhere.
But they probably wouldn't implement it if they didn't have to. After all, they refused to implement client-side OpenWebAuth support as well. There's literally a merge request on Mastodon's GitHub that'd implement client-side OpenWebAuth support, and that has been lingering since 2023, completely ignored by the devs. Back then, one merge would have been sufficient to give Mastodon client-side OpenWebAuth support.
So much about whether the Mastodon devs are willing to implement something that Mike Macgirvin has invented. Especially if they can't sell it to their faithful followers as their own original invention, and if they can't sell it to their faithful followers without admitting that there's something else than Mastodon out there in the Fediverse.
But even if Mastodon's devs wanted to implement full server-side nomadic identity, that doesn't mean it'll be easy. Basically, large parts of Mastodon's server backend would have to be rewritten. I guess this is why silverpill threw in the towel, gave up trying to implement nomadic identity on Mitra server-side and built a nomadic client instead.
There is no case of Hubzilla-level nomadic identity having been implemented in non-nomadic, ActivityPub-only, login-equals-identity Fediverse software after the fact. And there won't be any for quite a while.