korendianRequest for Feedback/Collaboration - Bytescape, an Iroh based identity layer for the open web
tuckermUnfortunately, I’m not familiar enough with Iroh to understand what exactly this is, but point #3 sounds interesting. Does this mean that, if a user has linked their identity to this service (and the other special media sites they are using support it), would I be able to see all of a user’s posts across multiple social media sites? E.g. filtering the feed by a certain user, and it shows all of that users’ posts on Mastodon and Pixelfed?
Yes, that’s the goal. It would be like an external facing version of emissary or bridgey fed, so you could set up a web portal for all of your social media presence, if you want. Iroh is just a p2p encryption protocol that allows data to be stored and transferred independently of central servers (although relay servers can and likely would be used for reliability and discoverability). So you can have a master copy of all of your data stored on your phone or PC or cloud hosting service or self hosted server, and display that data in one place for your reference/management or for others to view.
Sure. Iroh facilitates local storage and direct device to device encrypted connections. So basically, it allows you to store your online data on your own devices, encrypted with a secure key, that can be sent to a variety of different end points.
So for example, you import your mastodon profile, it downloads that data to a local vault, and the vault can then be viewed on any other platform that is able to visit your profile. So if a user signs up to the proposed Bytescape platform using a bluesky account, they could search for your mastodon handle, view your posts, and even be updated of your content, thanks to the Iroh syncing of the users local master vault and the cloud storage for their social accounts. This could be shared either through cloud relays for reliability, or you could retrieve it directly from the users local vault via direct p2p connections.
rglullisThis was one of my stretch goals for 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 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.
silverpill@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?
