@julian @mariusor @BeAware @aj There is also nomadic identity, which is not attached to any server to begin with. I'm sure that OAuth will win (by user count) though - because of Mastodon
Conversation
Notices
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Thursday, 23-Jan-2025 03:49:07 JST silverpill
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Thursday, 23-Jan-2025 04:28:35 JST silverpill
@mariusor Yes, it is like standard AP C2S (another solution for this problem), but with DID as identity root instead of server.
You register with your DID and application starts constructing objects with IDs based on it. Then you sign those objects.This is similar to Nostr where people can simply copy-paste their secret key into a different client and start sending messages. Except with FEP-ef61 we are not limited to plain cryptographic keys, and may use more advanced identities (any kind of DID).
-
Embed this notice
marius (mariusor@metalhead.club)'s status on Thursday, 23-Jan-2025 04:28:36 JST marius
@silverpill how does nomadic identity solve the problem of using multiple types of fediverse applications with a single identity?
Is it because multiple individual applications can show the same did:: ?
-
Embed this notice
silverpill (silverpill@mitra.social)'s status on Thursday, 23-Jan-2025 05:26:59 JST silverpill
@mariusor In FEP-ef61 world, HTTP inboxes still exist, and provided by servers. However, actor can have more than one HTTP inbox.
-
Embed this notice
marius (mariusor@metalhead.club)'s status on Thursday, 23-Jan-2025 05:27:01 JST marius
@silverpill I feel like thinking about the problem like that ignores one of the main tenets of the ActivityPub protocol: An Actor has An Inbox. :)
-
Embed this notice