We are thrilled to announce the official release of ActivityPods 2.0, a framework and platform that allows users to create a single account for multiple decentralised social applications while also providing developers with the tools to build and integrate these applications.
Holy shit…I haven’t tried it yet, but this sounds like one of the first ideas I pitched when I got here. One account, multiple platforms!
How do I do this? Can I do it with this account?
looks like its only compatible with mastodon and itself.
Well…that kind of defeats the purpose then.
It needs to be compatible with ALL the things. Lemmy, Mastodon, Pixelfed, Peertube, hell throw Bluesky in there! Get all the fediverse things interconnected. Otherwise, what is the point of having a service that connects all the things, and then making it compatible with none?
That’s not true it’s compatible with anything running ActivityPub. It currently has build a Mastodon client as a demo that’s why right now you can use it with Mastodon. They built Mastopod in a week. Part of the pitch it showing devs how relatively simple it is to build apps on top of it. So if someone builds a Pixelfed, Lemmy etc app then you absolutely can use it
That’s how I thought the Frediverse worked at first lol
It’s how it SHOULD work.
Like if I comment on someones picture on pixelfed, and someone replies to my comment, the notification should go to my inbox.
Then, if I post a video on peertube, and 5 people leave comments, those comments should go in my inbox.
And if 30 people leave replies to my Lemmy comments, I should have 30 comments in my inbox.
And that inbox? It should be one inbox. One account. If I see the notification for pixelfed, and I click the context button, my browser should take me to that pixelfed post. Then, if I click back, to the inbox again, and click context for the peertube comments, it should take me to that video.
That’s what I imagined when I first heard of the fediverse.
From a privacy perspective it’d be annoying if the default weren’t one-identity-per-website, though. That’s how it ought to work. If the user then wants to instead use a single one (akin to how OAuth logins allow you to use a single identity for auth purposes) that’s on them, but it should not work that way without explicit enabling.