Hello Fediverse,
I would like to receive some feedback on this idea I have been kicking around, and see if others might be interested in contributing. I have a basic prototype that proves out most of the technology, but not much beyond that.
The basic general description is an Iroh based identity layer for the open web. This platform would serve three primary functions:
- Preserve and consolidate social graph data in an encrypted local storage vault, allowing for import, display, and management of media and posts from both walled garden platforms and open platforms.
- A “universal translator” across open platforms, allowing for seamless connection between activitypub, AT protocol, and rss subscriptions. You are able to link mastodon, Lemmy, pixelfed, loops, and blusky accounts and your legacy social media imports can also generate RSS subscription feeds for your previous Instagram or YouTube (among other platforms) subscriptions, with all this content showing up in a single filterable fleed.
- Identities can be linked to any unique URL, using an umbrella DID. That URL can be any location the user chooses, including an indieweb page, a spacehey.com profile, or any other site the user controls and is able to host the corresponding DID document for cross platform identification.
There are many more details and features I have in mind that this architecture could facilitate, but this is the overarching basics of what I had in mind. I am very open to critique or analysis of this architecture, potential issues and limitations, as well as ideas for modification.
I would also welcome collaborators and contributors if there is interest, and I can open up the project for whoever may be interested. Let me know!
This was one of my stretch goals for https://fediverser.io/, and I would definitely be interested in helping with this. Basically, the end goal would be to create ActivityPub actors that are based on the DID to completely decouple their identity from the ActivityPub server that is serving their inbox and outbox.
Yes, that’s exactly it! The identities are linked to a URL that the user chooses, which hosts the DID document and all the identity records. I am working on getting the GitHub ready for public, I will notify you when it has been opened up!
FYI: I am not going to say that I have all the pieces in place, but I will say that if we put what I’'ve done on https://fediverser.io/ with my headless ActivityPub Server, we are like 90% of the way there. The hard part now, believe it or not, is to get other servers to implement the missing parts of AP instead of the selective implementation they have.
@robert.meyer86 See also https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md. This is already part of Fediverse and has multiple implementations.
Oh wow, this is exactly what I had been thinking of! Amazing! This should simplify the development process of this platform significantly. Do you know of any projects using this standard in their platforms?
Forte and tootik use FEP-ef61 with server-managed keys. I am working on an application where keys are stored on the client side: minimitra. This is probably closer to your idea.
Do you want to use iroh for transport, or for identity?