Veganism Social

Feral Ferment@<a href="https://mastodon.social/@rvcx" rel="nofollow noopener" target="_blank">Rob Shearer</a> Excellent write-up, agree with most of the points. On a related note: it is a pity that the poorly thought-out and designed Mastodon became the overwhelmingly popular Fediverse platform. I wish it were one of the Mike Macgirvin creations such as Hubzilla or (streams) or Forte, with their advanced features such as Nomadic Identity, OpenWebAuth (Federated Single Sign On), conversation containers for threaded conversations, extremely fine-grained privacy controls, etc. Nomadic Identity, in particular, is brilliant. This is how it works. You have a channel (that participates in the Fediverse, this is equivalent to an account on Mastodon) on any account on, let us say, Hubzilla instance A. You can open another account on Hubzilla instance B, and create a clone there of your channel on instance A. So this clone becomes a live, real-time backup of your channel; the backup includes your connections as well as your posts. And it is bidirectional. You can log on to your clone channel on B, and use it like your main instance, and now the clone on instance A will mirror your activity. If you wish, you can clone the channel on a third instance C. If one of A or B or C abruptly shuts down, you can continue operating your channel from your clone channel, so you lose nothing. This addresses one of your pain points as to how account migration does not work on Mastodon. By the way: you can have multiple channels per instance, and you can have clones of each channel on different instances. So if you wish, you can have separate channels for your hobbies and your professional activities and your politics; all contained and operated within a single account on a particular instance. You can read more about Nomadic Identity here #^<a class="" href="https://medium.com/@tamanning/nomadic-identity-brought-to-you-by-hubzilla-67eadce13c3b" rel="nofollow noopener" target="_blank">https://medium.com/@tamanning/nomadic-identity-brought-to-you-by-hubzilla-67eadce13c3b</a> and here. #^<a class="" href="https://medium.com/@tamanning/getting-started-with-nomadic-identity-how-to-create-a-personal-channel-on-hubzilla-7d9666a428b" rel="nofollow noopener" target="_blank">https://medium.com/@tamanning/getting-started-with-nomadic-identity-how-to-create-a-personal-channel-on-hubzilla-7d9666a428b</a> It is said that Bluesky is working on pioneering something like Nomadic Identity. Ironically, Mike Macgirvin had already pioneered it all the way back in 2012. He initially did it with Nomad (which underlies Hubzilla and (streams)), a protocol far richer and better-defined than ActivityPub; and recently, he even got Nomadic Identity working on ActivityPub. #^<a class="" href="https://fediversity.site/item/b69ce5a0-0c22-4933-8393-dce7100f4584" rel="nofollow noopener" target="_blank">https://fediversity.site/item/b69ce5a0-0c22-4933-8393-dce7100f4584</a> Unfortunately, the movers and shakers of the ActivityPub world keep pretending that Mike Macgirvin and his work does not exist. Then there’s OpenWebAuth for Federated Single Sign On. This enables seamless granting of permissions for you to operate your social dashboard from different parts of the Fediverse. You can read here how Nomadic Identity and OpenWebAuth together enable network resilience, censorship resistance, and ease of migration. #^<a class="" href="https://wedistribute.org/2024/03/activitypub-nomadic-identity/" rel="nofollow noopener" target="_blank">https://wedistribute.org/2024/03/activitypub-nomadic-identity/</a> There’s also conversation containers—these ensure that unlike on Mastodon, every single post/comment in a conversation thread is visible to every single person participating in or merely viewing the thread. (Also: you don't need @ tagging, anyone who participated in the conversation by replying at least once or by boosting or liking some post is notified of all new posts/comments.) I won’t elaborate on the fine-grained privacy controls, but I think they too address some of your pain points with Mastodon. Having said all that, I must mention that your core criticism of Mastodon also applies to Hubzilla, (streams), and Forte: there is asynchronous distribution of “some subset of a global database across some parts of the network”. I personally think there ought to be a truly universal search and community-controlled user-specific custom algorithms to address this problem, but I doubt the vocal part of the userbase here would agree. And relative to Mastodon, the Hubzilla+(streams)+Forte community is tiny, so there is hardly any local content. #<a class="" href="https://klacker.org/search?tag=Nomad" rel="nofollow noopener" target="_blank">Nomad</a> #<a class="" href="https://klacker.org/search?tag=Zot" rel="nofollow noopener" target="_blank">Zot</a> #<a class="" href="https://klacker.org/search?tag=ActivityPub" rel="nofollow noopener" target="_blank">ActivityPub</a> #<a class="" href="https://klacker.org/search?tag=Mastodon" rel="nofollow noopener" target="_blank">Mastodon</a> #<a class="" href="https://klacker.org/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://klacker.org/search?tag=Forte" rel="nofollow noopener" target="_blank">Forte</a> #<a class="" href="https://klacker.org/search?tag=NomadicIdentity" rel="nofollow noopener" target="_blank">NomadicIdentity</a> #<a class="" href="https://klacker.org/search?tag=OpenWebAuth" rel="nofollow noopener" target="_blank">OpenWebAuth</a> #<a class="" href="https://klacker.org/search?tag=ConversationContainers" rel="nofollow noopener" target="_blank">ConversationContainers</a> #<a class="" href="https://klacker.org/search?tag=PrivacyControls" rel="nofollow noopener" target="_blank">PrivacyControls</a> @<a href="https://infosec.exchange/@codinghorror" rel="nofollow noopener" target="_blank">Jeff Atwood</a>

Jupiter Rowland@<a href="https://io.waxandleather.com/@alisynthesis" rel="nofollow noopener" target="_blank">Alison Wilder</a> Because if you want full-blown user rights and all the same features as a local user on all over 30,000 Fediverse instances, you need a local user account on each one of them. This means two things: <ul><li>If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.</li><li>If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.</li></ul> For one, this is utter overkill. Besides, this is technologically impossible. This would require all Fediverse instances to know all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse. And, of course, it would require a newly-launched instance to know all Fediverse users. Again, with no exception. How and from which source are they supposed to know? That said, there is a single sign-on system for the Fediverse. It's called <a href="https://magicsignon.org/page/openwebauth/home" rel="nofollow noopener" target="_blank">OpenWebAuth</a>. It was created by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener" target="_blank">Mike Macgirvin 🖥️</a> (creator of Friendica and all its descendants) in the late 2010s already for now-defunct <a href="https://joinfediverse.wiki/The_Zotlabs_projects#Zap" rel="nofollow noopener" target="_blank">Zap</a>, a fork (of a fork?) of <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> which, in turn, is a fork of the currently hyped Facebook alternative <a href="https://joinfediverse.wiki/Friendica" rel="nofollow noopener" target="_blank">Friendica</a>. It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener" target="_blank">streams repository</a>, got it, too. However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere. As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop. Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so. OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything. For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile. If you're logged out, and you go to my profile page, you see nothing. But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile. And all of a sudden, you see my profile. That, for example, is what OpenWebAuth is for. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zap" rel="nofollow noopener" target="_blank">Zap</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=SingleSignOn" rel="nofollow noopener" target="_blank">SingleSignOn</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=OpenWebAuth" rel="nofollow noopener" target="_blank">OpenWebAuth</a>

Recent searches

Search options

Administered by:

Server stats:

#OpenWebAuth