My one frustration with #ActivityPub federated stuff right now is that they integrate, but only partially. I have this account, but I can't use this account to access #PixelFed. I have to create an account on pixelfed.social, and then I can follow myself from my Mastodon account? People who follow me here on Fosstodon don't follow the PixelFed account. I COULD boost my PixelFed account from Mastodon, but things just get awkward. Then we add #PeerTube into the mix, or other federated stuff.
@mike Just learned a bunch by reading up on all the terms you used that I'd never heard before - thanks!
@mike Not at all - I'm excited to see what they become
@mike This is actually being worked on currently by the PixelFed dev - the stack does not yet fully support federation for production environments.
You're right in the sense that each platform dev has to put extra work into interop, but there is an ongoing effort to develop a sane basis to conform to on a protocol level called #Litepub.
One thing in the future that would be nice would be the ability to authorize accounts against each other and tie them together for automated syndication.
With AP, there really hasn't been much of a discussion (that I'm aware of) pertaining to the notion of "one account authorized against multiple web applications that all store content as different kinds of activity types under that account's instance"
The closest thing, maybe, would be the server-to-client API, but no one has ever adopted it.
#BLOCKCHAIN!!! Do it! Do it!!
I'm kidding. I am glad that it's being worked on because I do feel that this is a one of the more frustrating things about #ActivityPub integration. It's like having multiple accounts that SHOULD work together, and kind of do, but kind of don't. Even tying accounts together in some way would be preferable. If I post on my #PixelFed account, it automatically posts that content to my Mastodon account? That would work, but the inverse?
i know at this point its super akward because you basically have two accounts on the same social networks to be able to do two different things.
I think another solution could be an activitypub implemation for identity and is integrated with all the other activitypub implementations. Eg you have an @firstname.lastname@example.org that syncs everything together and mastodon and per say pixeled automaticly redirect people to @email@example.com when ever they click on your mastodon account
Well, you could tether identities together as a starting point - basically each identity could make an OAuth request to one another or something.
Nomadic identity is basically the concept that you could migrate your core account onto a different node, but few federated platforms have really gone into that.
@mike @deadsuperhero @0x1C3B00DA
Take keybase but federate it. If you mastodon account says you are someone on federated keybase, and federated keybase says your someone on that mastodon account, then they must be the same person. Just have settings in mastodon and federated keybase to point the accounts at eachother.
Then people would follow your federated keybase account from mastodon because it doesn't look any different from just clicking on your mastodon account in the begining.
We could implement something like Hydra https://github.com/ory/hydra
But then you need to bring oauth/openID/identity to the base install of Mastodon otherwise if only some instances have it then you just have the XMPP fragmentation problem all over again
Fosstodon is a Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.