@keyoxide could this be used for #NomadicIdentity as an alternative to DIDs? 🤔

See https://aumetra.xyz/posts/nomad-id-first-steps

@ntnsndr I do agree with the last point. But I think #NomadicIdentity is even less VC-friendly, since it’s fundamentally about removing the moats of service providers.

@liaizon as long as I get #NomadicIdentity I’m good. I don’t need the fediverse to be a reliable storage of my data; that’s what my website/blog is for.

I think of my fedi posts as letters I send out into the ether.

@PavelVoronezh
> the ability to back up data on one of the friendly servers

Have you looked into the Zot protocol and its Nomadic Identity? It does exactly that. Of all the fediverse software I'm aware of, only Hubzilla and Streams implement Zot. I'm pretty sure Zot apps could already do this when ActivityPub was being drafted. Not sure why this capability wasn't included in AP

#Zot #NomadicIdentity

@smallcircles @rolle @wrigleyfield

I know this much is true: I cannot and should not have to rely on someone else’s ‘server instance’ as the primary keeper of my social graph, I.e. my internet address book.

My personal connections should first and foremost be under my personal control.

Only I get to decide who I’m connected to. And I decide how many of those connections are public.

I will share those connections with a server which will store and relay my post broadcast to my connects.

#NomadicIdentity #fediverse #ActivityPub

@0x0 👏

Essential reading for anyone interested in #NomadicIdentity on #ActivityPub

cc @shadowfacts @silverpill @liaizon

@Wander Such a design would also provide #NomadicIdentity for free by quite simply not tying you to an instance in the first place.

#P2P gossiping is also perfectly viable and could be used alongside the nexus/repeater/propagation nodes.

It would unfortunately be very awkward to backport onto ActivityPub as it currently is.

The actor@uri assumption runs deep in the spec and DIDs (https://www.w3.org/TR/did-core/) are a troublesome patch on that.

@ifixcoinops great example of why #NomadicIdentity is sorely needed, so our accounts + connections are separate and independent from our post content.

We can’t have servers quietly undoing our follows.

On a separate note, I feel like defederation should normally be enacted as a server-wide vote over the course of several weeks:

W1: Vote on this poll to decide whether we should defederate from X.

W2: Poll has concluded. >60% are in favor of defed, so it’s happening.

W3: Block

W4: Defederate

@laurenshof for me specifically, the 150 people is everyone involved in a ‘social enterprise’ project.

Using that server as primary host (although I’d love for that not to be a big deal with the introduction of #nomadicidentity ) makes sense to anyone whose content is primarily regarding that project.

In any case, solving for 5 vs 200 users is roughly the same thing as far as technical design constraints go.

@erlend
Why not make #NomadicIdentity a reality *before* federating with any Facebook-related servers, and see if they're willing to extend that functionality to their users? (Hint: Facebook will never do this, as it runs counter to their legal obligation to shareholders)

I see #P92 as the best opportunity I’ll ever get to bridge my own social network presence with that of my less techy friends.

We know Meta will attempt an EEE play, but what if we play the reverse UNO card and EE(E) them instead?

Embrace: Carefully federate in a minimum-viable fashion that doesn’t overrun the existing #fediverse

Extend: Make #NomadicIdentity a reality, so accounts can be moved effortlessly.

Extinguish: In case of misconduct, defederate and provide mass-migration assistance.

@sirius @Rcassano por isso acho a idéia de #nomadicidentity interessante. Sua identidade basicamente não depender da instancia, inclusive podendo ser replicada em várias

@aswath @reiver @gvlx @atomicpoet @evan @fediversenews

cc @dachary #F3
cc @helge #NomadicIdentity

I've been wondering about #identity support on the #Fediverse.
#Mastodon (and probably others) use the rel=me for external verification.
There is also "alsoKnownAs" that is used for account migration.

Now are there specific reasons why AKA or similar #aliases could not be used to implement something similar to #nomadicIdentity?
Two profiles both indicating one another via AKA/alias would be considered the same person and treated as such by their followers.

1/2

@ConserveChange agreed. We would have to introduce some important mitigations and protections to prevent activity flooding as well as any EEE tactics, but Meta joining the fediverse is ultimately a major compromise on their end, not the other way around.

Getting their currently very locked in users plugged into the #fediverse would give them an incredible new avenue to move off of it completely. Hence why it’s all the more important that we get to work on #nomadicidentity asap.

@alastor8472 Reasonable account portability is #1 on my wish list of next steps that I feel should have been implemented long ago. It also seems like something that the Mastodon devs in particular are not interested in implementing any time soon.

I like what I've seen from #Zot with #NomadicIdentity. I wish more #ActivityPub devs would consider that option.

For those looking to add 3rd party identification services, I just discovered Authl - a python library that supports email “magic link”, fediverse (Mastodon & Pleroma) and IndieAuth.

A side apology to @atomicpoet as I’m sure he’s mentioned IndieAuth many times when I’ve complained about single sign on / nomadic identity. (I could count how many times if only there were full text search for a specific user …)

#sso #Indieauth #NomadicIdentity

https://authl.readthedocs.io/en/stable/

@maegul
@fediversenews

I think this is something future work around #NomadicIdentity or #FederatedIdentity might be able to help with. Beyond users having multiple linked accounts they can use for backup communication, there could (long term) be ways to automatically circumvent "network damage" similar to how the low-level network is defined, because intermediate servers will be able to verify content and share hosting.

@identity

@jon @fediversenews @jupiter_rowland I’m slightly more optimistic.

I think people are getting fed up with having all the apps: Twitter, FB, Tik-Tok, Instagram and the friction going between them all and not being able to find a friend on a given app.

If the Fediverse provides less friction - through new apps that evolve to support multiple services simultaneously along with #NomadicIdentity or #SingleSignOn - then I think folks will migrate.

@bytex64 @lily "encrypted e-mail with account credentials" was fully thought out and implemented before Mastodon/ActivityPub, and is being actively ignored. This was in #Hubzilla called the Zot protocol, continuing as the Nomad protocol in #Streams https://codeberg.org/streams/streams . It is called #NomadicIdentity , and in Hubzilla/Streams, the encrypted credentials backup is just a "Save profile"!