About a year ago I dropped a rough thought on how @yarmoâs Keyoxide could be used on the Fediverse:
That wasnât very concrete.. here a further idea:
Keyoxide Profile component
Idea boils to the following UI to be hydrated (almost) competely via a reference given to oneâs Keyoxide Profile. Just drop the URL and fedi profile is filled out with all profile links verified.
I think thatâs a clever application. So roughly:
1- You configure somewhere on the fedi profile your Keyoxide profile
2- Clients get the verified identities from Keyoxide, and show the matching links as verified
Is this the idea? And how would this work for fedi instances that do not have these âattached linksâ like Mastodon has?
I think implementation-wise there should be multiple version of this component, dependent on what lang the app is using, but once the component is created in a language for one app it might be easily reusable in others. On Keyoxide side I donât know requirement to best serve the hydration, but seems like this is not a tough requirement.
With clients you mean devs adopting the component, or people using it in an app? In both cases it may be a âthorough documentationâ bullet point to addressâŠ
Yes, I meant clients = devs adopting the component. But whose âinitiativeâ should this be? Keyoxide? Or ActivityPub? It will be quite the responsibility if you envision this being âKeyoxide extending ActivityPubâ. Though granted, it will likely be the only possibility for this to ever see the light of day.
There are multiple ways this can be implemented. What I had in mind does not involve extending ActivityPub. It would more an app codebase integration of the component that stands on itself. The app would fetch the data, and also be responsible to keep it in sync, then uses that for communicating any Actor messages it sends across the wire, but no different than what it already does.