Gregory's Server
@Hrefna (DHC) @Johannes Ernst All this has already been covered years before there even was ActivityPub, namely with the Zot protocol from 2011 and its first implementation, the Red Matrix from 2012 which became Hubzilla in 2015.
Zot was designed with two features in mind which the current ActivityPub-based Fediverse doesn't cover: advanced permission control and instance-independent ownership of all your data. The latter was made possible by so-called nomadic identity which allows you not only to move your channel from instance to instance with ease, but to actually have your channel on multiple instances simultaneously. The former ranges from a new single-sign-on system named OpenWebAuth to a blog-like/Tumblr-like/Facebook-like one-post-many-comments thread model inherited from Friendica, but which now allows the thread starter to moderate their own threads, including deleting comments.
Zot eventually evolved into Nomad which is even more advanced and the base protocol of a slimmed-down Hubzilla descendant commonly referred to as (streams) which takes especially permission control even further.
Before someone asks: Both have always been bidirectionally federated with Mastodon & Co. In fact, one advancement of (streams) is that ActivityPub compatibility no longer only comes from an add-on, but it's tied deeply into the core now.
@Mike Macgirvin 🖥️, an experienced communications protocol designer who single-handedly created all of this, had actually also tried to advance ActivityPub to something that'd follow his ideas of what a good federated protocol should be capable of. AFAIK, all of his ideas were turned down. This is the only reason why he keeps developing and maintaining a separate protocol: The Federated Web desperately needs features which whoever has the power over ActivityPub stubbornly refuses to even consider, let alone implement.
#Long #LongPost #CWLong #CWLongPost #Fediverse #ActivityPub #Zot #Hubzilla #Nomad #Streams #NomadicIdentity
Zot was designed with two features in mind which the current ActivityPub-based Fediverse doesn't cover: advanced permission control and instance-independent ownership of all your data. The latter was made possible by so-called nomadic identity which allows you not only to move your channel from instance to instance with ease, but to actually have your channel on multiple instances simultaneously. The former ranges from a new single-sign-on system named OpenWebAuth to a blog-like/Tumblr-like/Facebook-like one-post-many-comments thread model inherited from Friendica, but which now allows the thread starter to moderate their own threads, including deleting comments.
Zot eventually evolved into Nomad which is even more advanced and the base protocol of a slimmed-down Hubzilla descendant commonly referred to as (streams) which takes especially permission control even further.
Before someone asks: Both have always been bidirectionally federated with Mastodon & Co. In fact, one advancement of (streams) is that ActivityPub compatibility no longer only comes from an add-on, but it's tied deeply into the core now.
@Mike Macgirvin 🖥️, an experienced communications protocol designer who single-handedly created all of this, had actually also tried to advance ActivityPub to something that'd follow his ideas of what a good federated protocol should be capable of. AFAIK, all of his ideas were turned down. This is the only reason why he keeps developing and maintaining a separate protocol: The Federated Web desperately needs features which whoever has the power over ActivityPub stubbornly refuses to even consider, let alone implement.
#Long #LongPost #CWLong #CWLongPost #Fediverse #ActivityPub #Zot #Hubzilla #Nomad #Streams #NomadicIdentity