Login

Recent searches

No recent searches

Search options

Not available on writing.exchange.
writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

334
active users

writing.exchange: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#nomadicidentity

0 posts0 participants0 posts today
Replied in thread
Public
Jupiter Rowland
@Joaquim Homrighausen @Kevin Beaumont To be fair, full data portability via ActivityPub has only been available in a stable release of anything for two weeks.

That was when @Mike Macgirvin 🖥️'s Forte, created in mid-August of 2024 as a fork of his own streams repository and the latest member of a family of software that started in 2010 with Friendica, had its very first official stable release.

And, in fact, Forte just uses ActivityPub to do something that (streams) and its predecessors all the way to the Red Matrix from 2012 (known as Hubzilla since 2015) have been doing using the Nomad protocol (formerly known as Zot). It's called nomadic identity. This is technology that's over a dozen years old on software that was built around this technology from the get-go, only that it was recently ported to ActivityPub.

Now, nomadic identity via ActivityPub was @silverpill's idea. He wanted to make his Mitra nomadic. He started working in 2023. The first conversion of existing non-nomadic server software to nomadic still isn't fully done, much less officially rolled out as a stable release.

If Mastodon actually wanted to implement nomadic identity, they would first have to wait until Mitra has a first stable nomadic release. Then they would have to wait until nomadic identity on Mitra (and between Mitra and Forte) has become stable and reliable under daily non-lab conditions. (Support for nomadic identity via ActivityPub on (streams) worked nicely under lab conditions. When it was rolled out to the release branch, and existing instances upgraded to it, it blew up in everyone's faces, and it took months for things to stabilise again.)

Then they would have to look at how silverpill has done it and how Mike has done it. Then they would have to swallow their pride and decide to adopt technology that they can't present as their own original invention because it clearly isn't. And they would have to swallow their pride again and decide against making it incompatible with Mitra, Forte and (streams) just to make these three look broken and inferior to Mastodon.

And only then they could actually start coding.

Now look at how long silverpill has been working on rebuilding Mitra into something nomadic. This takes a whole lot of modifications because the concept of identity itself has to be thrown overboard and redefined because your account will no longer be your identity and vice versa. Don't expect them to be done in a few months.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mitra #RedMatrix #Friendica #Hubzilla #Streams #(streams) #Forte #DataPortability #NomadicIdentity
Forgejo: Beyond coding. We Forge.forteNomadic fediverse server.
#nomadicidentity
Public
silverpill

FEP-ef61 "Portable Objects" update:

https://codeberg.org/fediverse/fep/pulls/529

The role of decentralized identifiers in FEP-ef61 is similar to "servers" in vanilla ActivityPub: they control all actors within a certain namespace.
When multiple actors exist under DID's authority, they will likely use same gateways. I added a sentence saying that gateways can be advertised via DID document as DID services (an example of that can be found in did:fedi spec). This is not possible with did:key, but might be useful with other DID methods.
I am also considering moving gateways property to actor's endpoints mapping, where server-wide endpoints such as sharedInbox are usually defined (in our case they are "DID-wide").

Forgejo: Beyond coding. We Forge.FEP-ef61: Endpoints and services- Added `endpoints.gateways` to the list of `gateways` alternatives. - Specified optional publishing of gateways as DID sarvices. - Added note about ActivityPub compatibility. - Added warning about changing URI scheme. - Added `type` to proposal metadata. - Changed "Controller Documents" to ...
#fep_ef61#NomadicIdentity
Public
silverpill

Today, on the anniversary of publishing FEP-ef61, nomadic actors on Streams and Mitra made their first contact.

I created a signed Follow activity using the nomadic client and sent it to the Mitra gateway, which delivered activity to a nomadic actor on the Streams server. The Streams actor sent an Accept activity back, which I then picked from my inbox on the gateway.

Summary card of repository fediverse/fep
Codeberg.orgfep/fep/ef61/fep-ef61.md at mainfep - Fediverse Enhancement Proposals
#fep_ef61#NomadicIdentity
Public
silverpill

FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/455

I added a couple of sentences clarifying FEP-ef61 design goals. In particular:

1. "This document describes web gateways, which use HTTP transport. However, the data model and authentication mechanism are transport-agnostic and other types of gateways could exist."

FEP-ef61 is designed to be compatible with any transport protocol, including the sneakernet. For example, it should be possible to replace web gateways with iroh nodes.

2. Location discovery using DID services. It came to my attention that some developers are trying to implement a variation of FEP-ef61 where gateways are specified in a DID document instead of an actor document. That significantly differs from existing FEP-ef61 implementations (Streams and Mitra), and has a serious practical disadvantage: it doesn't work with generative DID methods such as did:key. Support for pure key-based identities is important for several reasons:

- It is very useful for client-to-client (#p2p) communication without servers.
- Interoperability with other protocols that use public keys as identities. #Nostr is probably the most popular, but there are many more.
- It lowers the barriers to entry for client developers, who otherwise would need to deploy a did:web or something more complicated like did:webvh.

So, don't do that.

Also added a discussion section about media access control.

If media identifier only contains a digest, the gateway can't restrict access to it. This may not be a big problem because digest is very hard to guess, but an access control mechanism still might be useful. One way to implement it is to add an 'ap' identifier of a parent document to a hashlink and make it mandatory.

Codeberg.orgFEP-ef61: Update proposal- Updated "History". - Replaced did:tdw with did:webvh. - Added a note about non-web gateways. - Describe location discovery using DID services. - Clarified how gateways with arbitrary paths can work. - Added a section about media access control.
#fep_ef61#NomadicIdentity#DataPortability
Replied in thread
Public
Jupiter Rowland
@Jenniferplusplus I sincerely hope that you aren't building Letterbook to only interact with itself and Mastodon.

Sooner or later, Letterbook will encounter content coming in from instances of software created by @Mike Macgirvin ?️, namely Friendica, Hubzilla (these two are actually older than Mastodon), (streams) or Forte. For reference: I am on Hubzilla.

You/it will have to expect and be able to deal with the following:
  • Enclosed one-post-many-comments conversations instead of threads that consist of posts loosely tied together
  • Permissions of all comments/replies firmly defined by the start post; permissions/visibility can't be changed within a running conversation
  • "Monster posts" of any length because none of them has a character limit
  • Not just Note-type objects, but also Article-type objects (from Friendica right now, the others may implement them once Mastodon introduces sensible support for them)
  • Full HTML text formatting, up to and including numbered lists, tables, horizontal lines, character size and character colour
  • Both quotes (as done in bulletin-board forums) and quote-posts (posts fully embedded in other posts like quote-tweets)
  • Embedded links (this comment makes a whole lot of use of them)
  • Inline images embedded within the text, and more than four of these in one post
  • Inline audio streams embedded within the text
  • Inline videos embedded within the text
  • "Weird" mentions and hashtags with the @ or the # not part of the link (look at the mentions and the hashtags in this comment, then look at mentions and hashtags on Mastodon and compare them)
  • "Summaries in the CW field" (because Mastodon repurposed StatusNet's summary field, which was used by StatusNet, Friendica and Hubzilla as an actual summary field, for content warnings in 2017; several Fediverse server apps continue to use it for summaries)
  • All four support titles in addition to summaries

Some of the above may also come in from elsewhere, e.g. a wider range of text formatting than Mastodon allows itself to render is fully supported by just about everything that isn't Mastodon.

Also, ActivityPub is currently evolving. New FEPs are being put to use and bringing in new features far away from how Mastodon is working. In particular, (streams) and Forte and @silverpill's Mitra use decentralised identifiers as per FEP-ef61 (Portable Objects). Forte has nomadic identity fully implemented via ActivityPub while (streams) at least supports it. And all three have conversation containers implemented, silverpill wants to make them an FEP, and Hubzilla is planning to implement them with version 10.

This means three things. One, weird identifiers. Two, weird actor identities: What looks like one user automatically cross-posting to another account on another instance to non-nomadic ActivityPub implementations is actually the very same actor residing simultaneously on multiple server instances. Three, again, conversations work drastically different from Twitter and Mastodon.

Lastly, it may be a good idea to implement a little server type display from the get-go so that the user knows what kind of Fediverse instance something comes from. Misskey and its forks have it, Friendica has it, (streams) has it, Forte has it. Just because Mastodon doesn't have it, doesn't mean it's a good idea not to have it. Besides, if content from certain server applications malfunctions on Letterbook, users can pinpoint right away what server application causes that trouble when submitting a bug report.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Conversations #ConversationContainers #FEP_ef61 #NomadicIdentity
joinfediverse.wikiWhat is Friendica? - Join the Fediverse
#nomadicidentity
Replied in thread
Public
Jupiter Rowland
@Ben Werdmuller What Bluesky is planning to do with the AT protocol looks like nomadic identity as ordered from Temu.

And nomadic identity is not a vague concept. It isn't futuristic technology either. It has been reality in the Fediverse for longer than Mastodon has been around. It was invented by @Mike Macgirvin ?️ in 2011 and then implemented in his own Zot protocol. Zot, in turn, was first implemented in 2012 in a project named Red, later the Red Matrix, known since 2015 as Hubzilla. And almost everything that Mike has made after Hubzilla had or still has nomadic identity implemented.

I'm writing to you from Hubzilla right now, so yes, it's very much part of the Fediverse. It's a rock-solid daily driver with a stable release (9.4.3).

Nomadic identity does not do away with a domain being part of your ID. What it does away with is the connection between account and identity and the connection between server and identity.

Nomadic identity means that your identity with everything that belongs to it (profile, posts, comments, DMs, connections, files, settings etc. etc. pp.) is no longer bound to any one Fediverse server. It can exist on multiple servers simultaneously. Not as dumb copies, but as clones. Bidirectional, live, hot backups in near-real-time.

Your identity always has one main instance which also lends the domain name. In addition, it can have one or multiple copies on different servers of your choice. Your accounts only serve to grant you access to the instances of your identity on a specific server. The main instance and the clones are constantly sync'd against each other in both directions. For example, after I've sent this comment, it was mirrored over to my clone.

Notice how I've written "bidirectional". For I can also log into my clone and use it just the same as my main instance. This is useful for when the server with my main instance on it is offline. When it comes back online, everything that has happened on my clone in the meantime is being sync'd to the main instance.

Granted, Mastodon and most of the rest of the Fediverse don't understand nomadic identity. When I post from my clone, they take my clone as an independent account with the ID jupiter_rowland@hub.hubzilla.de. But Hubzilla and (streams) do understand nomadic identity. Whatever comes from my clone, they'll correctly identify as being sent by jupter_rowland@hub.netzgemeinde.eu in spite of not coming from hub.netzgemeinde.eu.

Even "moving instances" is greatly facilitated. For example, if the server with the main instance of my channel shuts down permanently, I can make my clone my new main instance. That's easy-peasy: two mouse clicks and some 15 minutes of letting things settle, also because Hubzilla will have to go around and change all my connections from jupiter_rowland@hub.netzgemeinde.eu to jupiter_rowland@hub.hubzilla.de. On the remote side, on people's Hubzilla and (streams) servers.

You've read that right: If you move, nomadic identity makes your nomadic followers automatically follow you at your new home. What's beyond science-fiction on Mastodon has been daily-driven reality on Hubzilla since its inception in 2015.

While nomadic identity currently only has stable support via Mike's Zot and Nomad protocols and on Hubzilla and (streams), its implementation using only ActivityPub has been in the making since last year.

CC: @glyn

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #DecentralizedIdentity #DecentralisedIdentity #NomadicIdentity #ActivityPub #Zot #Nomad #Hubzilla #Streams #(streams)
joinfediverse.wikiWhat is nomadic identity? - Join the Fediverse
Replied to Strypey
Public
Jupiter Rowland
@Strypey A few more details:

* FEP-ef61: Portable Objects

https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md

Invented in, I think, 2023 by @silverpill for Mitra (based on ActivityPub). Currently implemented there and in @Mike Macgirvin ?️'s streams repository and Forte. Part of the plan to introduce almost Nomad-level, but cross-project nomadic identity to ActivityPub.

* FEP-61cf: The OpenWebAuth Protocol

https://codeberg.org/fediverse/fep/src/branch/main/fep/61cf/fep-61cf.md

Invented in 2018 by Mike Macgirvin for Zap (Zot6 development platform; discontinued 2022). Backported to Hubzilla in 2020. Full server-side and client-side implementation only in Hubzilla (based on Zot6, also supports ActivityPub etc.), (streams) (based on Nomad, also supports Zot6 and ActivityPub) and Forte (based on ActivityPub). Friendica has a client-side implementation. Mastodon has a client-side implementation pull request that has to be merged eventually.

CC: @Laurens Hof

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Zap #Streams #(streams) #Forte #Zot #Zot6 #Nomad #ActivityPub #FEP #FEP_ef61 #FEP_61cf #DecentralizedIdentity #NomadicIdentity #OpenWebAuth #SingleSignOn
Mastodon - NZOSSStrypey (@strypey@mastodon.nzoss.nz)39.7K Posts, 2.99K Following, 3K Followers · Free human being of this Earth. Pākeha in Aotearoa. Be excellent to each other! Matrix: @strypey:matrix.iridescent.nz All my posts here are CC BY-SA 4.0 (or later). #Vegan #Permaculture #PeerProduction #SoftwareFreedom #PlatformCooperatives #FreeCode #CreativeCommons #SciFi #Comedy #Juggling #fedi22
#singlesignon
Public
Alexander Goeres 𒀯
Hurray! They are reinventing the wheel! So that we all can be drivimg from now on. A miracle ...

#internet #socialMedia #hubzilla #nomadicIdentity

Tim Schlotfeldt ⚓?️‍? schrieb den folgenden Beitrag Mon, 14 Oct 2024 08:29:53 +0200 This thread is well worth reading. It's about the #W3C standard DID: "Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity.". The take away: We already had a solution for Decentralized identifiers but … #NIH.  

My #Hubzilla had this (here it is called "Nomadic Identity") and it rescued my fediverse identity.


It starts with this posting:

#^glyn (@underlap@fosstodon.org)
What would it take to add decentralised identity (e.g. W3C DIDs) to the Fediverse? Who is already working on this?

Bluesky's AT Protocol is a great proof of concept, but probably isn't the endgame. Abstracting Fediverse identity using hostnames and WebFinger is another useful experiment, but again probably not the endgame.

#DecentralizedIdentity #ATProtocol #W3C #ActivityPub



The Folks from #Hubzilla are stepping in and explain, that this problem was already solved even before  #ActivityPub existed:

#^Jupiter Rowland
@glyn Decentralised identity has been available for longer than Mastodon, let alone ActivityPub. Only that it is known as "nomadic identity" here.

It was first implemented by Friendica creator @Mike Macgirvin Macgirvin ?️ in the Zot protocol in 2011 and in a Friendica fork named Red in 2012, later renamed into the Red Matrix, eventually reworked and renamed into Hubzilla in 2015.

Proof: This Hubzilla channel of mine actually simultaneously resides on two servers.

(Almost) everything that Mike has made afterwards, forks and forks of forks of Hubzilla, used to have or still have nomadic identity implemented.


#ActivityPub #Mastodon #Fediverse
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
Public
Jupiter Rowland
@glyn Decentralised identity has been available for longer than Mastodon, let alone ActivityPub. Only that it is known as "nomadic identity" here.

It was first implemented by Friendica creator @Mike Macgirvin ?️ in the Zot protocol in 2011 and in a Friendica fork named Red in 2012, later renamed into the Red Matrix, eventually reworked and renamed into Hubzilla in 2015.

Proof: This Hubzilla channel of mine actually simultaneously resides on two servers.

(Almost) everything that Mike has made afterwards, forks and forks of forks of Hubzilla, used to have or still have nomadic identity implemented.

His streams repository contains a fork of a fork... of Hubzilla that intentionally has no name, and that offers nomadic identity via the Nomad protocol with better compatibility with non-nomadic ActivityPub. In July, it had decentralised IDs as per FEP-ef61 (see also here) implemented, a first step by Mike to fully implement nomadic identity in ActivityPub.

Forte, Mike's most recent fork from August, had all support for Nomad and Zot6 removed and only uses ActivityPub anymore while still offering nomadic identity. To my best knowledge, however, it has yet to be declared stable enough to be daily-driven, and it has no public instances.

Other than all this, a non-public development version of @silverpill's Mitra has nomadic identity via ActivityPub in development. I'm not sure whether FEP-ef61 is implemented in the release version yet. It's the only Fediverse project aiming to implement nomadic identity which Mike Macgirvin has nothing directly to do with.

The ultimate goal is to be able to clone a Fediverse identity across project borders. Only considering stable releases, it's currently only possible to clone Hubzilla channels within Hubzilla, using Zot6, or (streams) channels within (streams), using Nomad.

Unfortunately, Mike has officially retired from Fediverse development and only occasionally submits code to the streams repository and Forte anymore.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #DecentralizedIdentity #NomadicIdentity #ActivityPub #FEP_ef61 #Zot #Zot6 #Nomad #Hubzilla #Streams #(streams) #Mitra
joinfediverse.wikiWhat is nomadic identity? - Join the Fediverse
#mitra
Public *
silverpill

FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/397

I fixed proof.verificationMethod values in examples, as well as accompanying text. These values should include fragments that identify a specific key in a DID document, so they are not actually DIDs but DID URLs (a similar change was made in FEP-8b32).
I also added a paragraph on authentication and authorization (with a normative reference to FEP-c7d3), and described WebFinger address reverse discovery in compatibility mode.

Codeberg.orgFEP-ef61: Update proposal- Require path to be an opaque string. - Clarify that custom query parameters should not be used. - Added "Authentication and authorization" section. - Added description of WebFinger address reverse discovery in compatibility mode. - Corrected description of a relationship between proof.verif...
#NomadicIdentity#fep_ef61
Replied in thread
Public
Jupiter Rowland
@Johannes Ernst
We need to get to identities that aren't tethered to particular instances. Various approaches have been discussed, all more or less valid IMHO, we just need to get them implemented.

We have had one working implementation for 13 years now. In the Fediverse. In stuff that's federated with Mastodon.

@Mike Macgirvin 🖥️, creator of Friendica (2010), creator of Hubzilla (2015), creator and maintainer of the streams repository (2021) and, most recently, creator and maintainer of Forte (all four are being actively maintained, part of the Fediverse and federated with Mastodon), invented the concept of nomadic identity in 2011.

The same year, he implemented it in his own Zot protocol. Zot came to use first in 2012 in a Friendica fork named Red, later the Red Matrix, which became Hubzilla in 2015. Hubzilla still uses the latest stable version of the Zot protocol that's still called Zot. Everything that Mike did since 2012, with the exception of the first Osada from 2018, featured nomadic identity, including (streams) which is based on an "offspring" of Zot called Nomad.

I'm writing to you from a Hubzilla channel that simultaneously resides on two server instances. Not in the shape of a dumb copy, but in the shape of a real-time, bidirectional, live, hot backup.

It's basically what Bluesky has claimed to be a revolutionary new and never-done-before feature in the AT protocol, only that a) it's even more advanced, b) it's older than Bluesky, c) it has been proven to actually work in daily use, and d) it is in daily use.

Right now, Mike is working on implementing nomadic identity using only ActivityPub, specifically FEP-ef61. Even this has advanced beyond theoretical. (streams) has it implemented already. All channels created on accounts that were registered on versions 24.07.20 and newer are made compatible with nomadic ActivityPub. I have two such channels, although neither has a clone yet.

In fact, it could be that at least Forte, which is in a very early stage right now, will have Nomad and maybe even support for Zot6 removed and go nomadic using only ActivityPub. Mike said he wants to sunset Nomad and Zot6 once nomadic identity via ActivityPub is ready for prime time.

@silverpill is working closely together with Mike to implement nomadic identity via ActivityPub on the Fediverse microblogging project Mitra. It has taken the switch to nomadic ActivityPub itself.

Just because Mastodon doesn't have it, doesn't mean it doesn't exist.

CC: @ShadSterling @damon

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mitra #Hubzilla #Streams #(streams) #Forte #FEP_ef61 #NomadicIdentity
joinfediverse.wikiWhat is Friendica? - Join the Fediverse
#nomadicidentity
Public
Jupiter Rowland
@Fediverse News

The cat is out of the bag. Mike Macgirvin's family of Fediverse server applications has a new member: Forte which he has forked off his own streams repository some three weeks ago.

The first announcement came in a comment on a post about Friendica with which everything had begun, just three days ago. The same day, the up-until-then still unannounced Forte repository was discovered. Unlike what's in the streams repository, Forte seems to have a name again, and Mike refers to it as a "project".

(streams), as its predecessor is colloquially being referred to, is already one of the most advanced and innovative server applications in the Fediverse. It has the most elaborate set of permission controls as of yet, even surpassing Hubzilla, the younger one of its surviving ancestors. Also, Mike uses it to develop the implementation of nomadic identity, his own invention from as early as 2011, purely via ActivityPub, including FEP-ef61. So (streams) itself is already a pioneering work, and its development is far from done.

And now we have Forte which promises to be even more advanced. There are no specs yet, much less any public instances. And even if it's the latest fork in 14 years of Fediverse development, I guess it's far from being ready for prime time. But seriously, it's a (streams) fork.

#Fediverse #NomadicIdentity #FEP_ef61 #Friendica #Hubzilla #Streams #(streams) #Forte
Summary card of repository streams/streams
Codeberg.orgstreamsConsent based public domain federated communications server. Provides a feature rich ActivityPub and Nomad communication node.
#forte
Replied in thread
Public
Jupiter Rowland
@Cătă
c) ActivityPub is off by default, not to mention d) how to turn it on which is anything but straight-forward.

Holly cow. I guess I'll stay on Friendica for the foreseeable future :D

To be fair, ActivityPub is off by default because it makes nomadic identity more difficult on the level that Zot6 offers. And it's off by default at channel level only whereas it's on by default at hub level.

With "anything but straight-foward", I mean it isn't like on (streams) where you have an ActivityPub on/off switch in the settings which is usually even on when you first discover it.

Instead, ActivityPub is an add-on, an "app" that has to be "installed". But newbies don't expect Hubzilla to have add-ons at all because Twitter has none, and Mastodon has none. And they certainly wouldn't expect ActivityPub, of all things, to be an add-on and off by default. In fact, most probably join Hubzilla in the belief that it is based on ActivityPub like "everything else" in the Fediverse.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #ActivityPub #NomadicIdentity
hub.netzgemeinde.euNetzgemeinde/Hubzilla
#nomadicidentity
Continued thread
Public
Strypey

I wonder how this might fit with the work done to extend easy account migration across the fediverse, with Portable Objects (FEP-ef61)?

codeberg.org/fediverse/fep/src

The developer of Streams contributed a lot to this FEP, based on the NomadicIdentity features it's shared with Hubzilla for years(1). So it's already been implemented in Streams.

I'm curious to see it added to other ActivityPubs apps so I can test an app-to-app migration.

Summary card of repository fediverse/fep
Codeberg.orgfep/fep/ef61/fep-ef61.md at mainfep - Fediverse Enhancement Proposals
#NomadicIdentity#PortableObjects#Streams
Replied to Strypey
Public
Jupiter Rowland
@Strypey @Laurens Hof I think I have to jump into this conversation here.

> Fediverse platform Streams has added nomadic identity to their platform, based on ActivityPub

To be clear, Streams has always had Nomadic Identity, using their own protocol (Zot/ Zap/ Nomad, whatever it's currently called).

First of all, a little nitpicking: It is not "officially named 'Streams'" like other projects are officially named "Mastodon" or "Friendica" or "Hubzilla".

It's officially and intentionally unnamed. It's intentionally nameless and brandless. Not even its instances have a unified identifier like "mastodon" or "friendica" or "hubzilla". "Streams" is the name of the code repository which was absolutely required to have a name, so Mike only speaks of the repository, and the community speaks of "(streams)" in parentheses.

And yes, it has always had nomadic identity. And it's at the end of a long string of forks, all by Mike himself, that have been supporting nomadic identity since 2012 when Mike forked Friendica into something named Red and ported it from Friendica's DFRN to his new nomadic Zot protocol.

In other words, nomadic identity has been in use for almost four years longer than Mastodon has been around. And the idea itself is from 2011 when Mike discovered one critical shortcoming of decentralised networks, and that's people losing their online identities when the instances they're on shut down.

Red still exists, only that it has been Hubzilla since 2015.

(streams) is based on a protocol named Nomad. Technically speaking, Nomad would be Zot12, but when Zot11 was reached during the development of Roadhouse which (streams) is a fork of, it had become incompatible with Hubzilla's Zot6. So in order not to confuse people, this version was renamed Nomad.

What's changed is ...

> Streams is using FEP-ef61

Mike is actually a big contributor to FEP-ef61 because what FEP-ef61 tries to do, he has done before way back in 2011 when he conceived the Zot protocol and in 2012 when he implemented it for the first time.

So thanks to Mike, the wheel doesn't have to be re-invented from scratch by someone who has never heard of the existence of wheels before, much less seen or even used them.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Zot #Zot6 #Nomad #ActivityPub #FEP_fe61 #NomadicIdentity
Mastodon - NZOSSStrypey (@strypey@mastodon.nzoss.nz)39.7K Posts, 2.99K Following, 3K Followers · Free human being of this Earth. Pākeha in Aotearoa. Be excellent to each other! Matrix: @strypey:matrix.iridescent.nz All my posts here are CC BY-SA 4.0 (or later). #Vegan #Permaculture #PeerProduction #SoftwareFreedom #PlatformCooperatives #FreeCode #CreativeCommons #SciFi #Comedy #Juggling #fedi22
#nomadicidentity
Public
Jupiter Rowland
@Johannes Ernst
same account for multiple instances

This in its pure, nomadic form and with proven stability is only available on Hubzilla and (streams) anyway.

They're also the only ones whose instances can detect off-site users' logins and grant them rights that other visitors don't have, provided said off-site users are on either of the two or Friendica. All thanks to OpenWebAuth.

@Mike Macgirvin 🖥️, creator of all three and maintainer of the streams repository, is currently working on implementing nomadic identity and (streams)' set of permissions using nothing but ActivityPub so it can become available to everything else in the Fediverse as well.

share to fediverse

I'm not quite sure, but I think @Stefan Bohacek or someone who commented on one of his posts has figured out how to share at least to Hubzilla.

However, actual share buttons are all geared only towards Mastodon and hit-and-miss at best when it comes to anything else. The less something is like Mastodon, the less they work with it.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NomadicIdentity #OpenWebAuth #Friendica #Hubzilla #Streams #(streams) #ShareButton #ShareButtons
social.coopJohannes Ernst (@J12t@social.coop)35 Posts, 837 Following, 695 Followers · Technologist, founder, organizer. Let's put people back in control of their technology. The Fediverse is a good start. Also wondering aloud where we are taking this planet. Check out my home page for more info and links. He/him. tfr
#sharebuttons
Replied in thread
Public
Erlend Sogge Heggen

@mikedev @streams congrats! 🎉

over ActivityPub is a big deal; might this release be accompanied by a blog post or other such technical writeup about the implications of these new features?

Where should we be referring instance developers who’d like to implement their own version of nomadic identity?

ExploreLive feeds
About