Conversation
Notices
-
So here's the high level overview...
The first component is your external identity manager. This will behave somewhat like Mastodon's current external account verification interface. Links are created based on the existence of a secure relationship with rel="me" links (secure meaning https with no http redirects in the redirect chain).
This module just creates and manages verified links.
The second component is the Channel Manager (which anybody using streams or zap or hubzilla is already familiar with). This currently provides a selector for your local channels (on this instance), and channels you can moderate (on any instance). What we're going to do is add another section so you can teleport to your external identities (which includes nomadic identities and any rel="me" identities you added via the external Identity Manager). So basically a single dropdown will let you visit any of your identities from the channel menu. OpenWebAuth would be nice, but chances are high that you've got a long-life cookie on these sites and it will work without authentication.
This gets you 90% of the way there.
Next comes the Channel Sources module which lets you re-publish any posts that arrive from certain connections. Anybody with a rel="me" relationship will automatically become potential channel sources. This lets you automatically re-publish any content that you published on these separate accounts to your streams channel (with an optional category or tag, depending on the source). So your streams account can (if you want) be a central aggregator for all your fediverse accounts and will boost or share all the content from your additional identities to the followers of your streams identity. This part is completely optional if you want to have separate followers on each service.
This provides the basic functionality. Then further down the road, we'll probably do some follower merging from your linked accounts and let you address these external followers to your other accounts from posts you make in streams. The goal is provide the inverse of using your streams account as the aggregator, and let you use your Mastodon as the aggregator (for instance). This may not be possible unless the other service provides re-publishing tools. But I'm also looking at some other possibilities since I don't like depending on any projects which are resistant to innovation. Will try to find a way to achieve our desired goals without requiring any other projects to evolve.
That's the high level overview. As always, once these pieces start coming together, the feature is likely to evolve in different directions as people start to explore the new possibilities.
-
We've discussed this earlier... Currently working on federated identities for the #fediverse. You know, to link your Akkoma account with your Pixelfed account and your streams account - and maybe your Mastodon account (if any of you have one of those). Hoping to have at least an identity management interface to demo sometime in the next several days.