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
8
Replies
5
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
@thisismissem@hachyderm.io interesting! how are you distinguishing the last screenshot ("saving an account" for FedCM) from the password manager "saving an account"? I think I'd read that popup as the latter, not the former.
@c what would you use instead? (Copy isn't final in these designs)
@c it's one of a few designs, but these accounts (well identity providers really) have a settings screen to manage them, much like passwords — the UI shown in screenshot 4 is one of a few different designs we have, but where we're leaning towards.
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.
FediPod uses client-based creds too.
@thisismissem Would it also be possible to be signed in to different Fediverse servers at the same time? I'm still hoping for a Fediverse client that just combines the different timelines and lets me choose from which account to reply...
