|
Top-level
I’d really like to see single signon for #ActivityPub servers. I could see it working in one of two ways: 1. (easier for users) Each server software allow signon and posting (etc.) from accounts to Fediverse instances that aren’t the same as the home instance. For example, using a kbin account to post on Mastodon. Each server software would need to know how to interact with the other kinds. 3 comments
Option 2 might be as simple (ha!) as someone writing a credential-syncing server for the landing page where you tell it the subdomains, so it knows where to push those. Not sure the Mastodon, Pixelfed, etc. servers would need to be modified. Option 1 could (on the desktop web app) appear as different tabs for Mastodon, kbin, Pixelfed, etc., all using the same singon to a single instance (doesn't matter which kind). |
Gregory's Server
@pixelfed @dansup
…
2. (easier for software devs) Let’s say I setup these #ActivityPub servers as subdomains on the same domain:
• toot.example.com (Mastodon)
• doot.example.com (kbin or Lenmy)
• pixs.example.com (Pixelfed)
• vids.example.com (PeerTube)
You’d signup on the example.com landing page, and it would sync credentials to the subdomains. It would work like using your Google account to login on different (sub)domains to Docs, Gmail, and YouTube.