We've been working hard on FedCM to make it work better for the decentralised web!
These new designs should enable us to support the Atmosphere (AT Protocol) and Fediverse (ActivityPub) better, including parity with centralised identity providers.
RE: https://bsky.app/profile/did:plc:thaoj4hhvraos7y6v3yog7re/post/3mui4mejurc2x
3
Replies
4
Boosts
Here's what the new designs look like:
(Someone help me out with alt text because I don't think I can accurately describe these screenshots in a way that'd make sense)
4 media files
Yes, those screenshots are using Atmosphere (AT Protocol) accounts in them, but this design is intended to work for the fediverse as well!
Generally we're thinking that client applications (e.g., phanpy and elk) would use a login to get a credential back, but for jumping between different fediverse servers we would use the fields API to retrieve the account identifier and then pair that with @benpate's activity intents FEP.
Why? Because you can probably trust a client app deployed in a known location, but you'd be less likely to trust a random server with a credential.
