5 ms·

The thing that annoys me is that there is no propper way (at least to my knowledge) to run multiple linked fedi accounts. I have a selfhosted misskey instance,

by Kab1r 3y ago

The thing that annoys me is that there is no propper way (at least to my knowledge) to run multiple linked fedi accounts. I have a selfhosted misskey instance, but then should I also run pixelfed? Or should I just use the singular instance?

kevincox 3y ago
I have the same problem. I would love to be able to toot from mastodon and post videos from PeerTube to the same account. Right now it is very segmented, even though most fediverse apps can process incoming posts of various formats (so you can follow PeerTube users from Mastodon no problem) but you can only post a limited set of content. They have mixed identity and applications.
- iameli 3y ago
  This is where the Web3 ecosystem is ahead right now. One address, log into a hundred different apps with the same wallet identity.
tedunangst 3y ago
Everyone just has multiple accounts, but I'd say it still works better than having separate twitter, instagram, reddit, and youtube accounts. You may need a peertube account to post a video, but just about anyone can comment if they like. Can't comment on a youtube video from twitter.
- robertlagrant 3y ago
  To be fair, you can comment on a Twitter video from Twitter :-)
3np 3y ago
I've been toying around with the idea of an ActivityPub proxy/aggregator/delegation which would "front" all your services and act as a unified identity for the proxied instances. It would inherently require trust, so the only way it would scale beyond self-hosters controlling their own domain would be co-hosted alongside some SSO-unified fedi services (or if S2S delegation becomes an adopted thing). (If you run with this idea, consider AGPL for all parts :))
- mariusor 3y ago
  It would also require that (almost)all the existing fediverse services be redone from scratch because each of them owns the underlying ActivityPub actor (that represents a user) and are unable to work with one coming from a third party.
  - 3np 3y ago
    Only in case of "proper" delegation, and in either case not "from scratch", I think.
erlend_sh 3y ago
What you want is account aliases: https://github.com/mastodon/mastodon/issues/3796 https://github.com/mastodon/mastodon/issues/3796
- Kab1r 3y ago
  I don't think that would suffice. I want all my data to be in one place, hosting one service, while still being able to use frontends for all of the different applications. It's a big ask for sure.

by Kab1r 3y ago

kevincox 3y ago

I have the same problem. I would love to be able to toot from mastodon and post videos from PeerTube to the same account. Right now it is very segmented, even though most fediverse apps can process incoming posts of various formats (so you can follow PeerTube users from Mastodon no problem) but you can only post a limited set of content. They have mixed identity and applications.

iameli 3y ago
This is where the Web3 ecosystem is ahead right now. One address, log into a hundred different apps with the same wallet identity.

tedunangst 3y ago

Everyone just has multiple accounts, but I'd say it still works better than having separate twitter, instagram, reddit, and youtube accounts. You may need a peertube account to post a video, but just about anyone can comment if they like. Can't comment on a youtube video from twitter.

robertlagrant 3y ago
To be fair, you can comment on a Twitter video from Twitter :-)

3np 3y ago

I've been toying around with the idea of an ActivityPub proxy/aggregator/delegation which would "front" all your services and act as a unified identity for the proxied instances. It would inherently require trust, so the only way it would scale beyond self-hosters controlling their own domain would be co-hosted alongside some SSO-unified fedi services (or if S2S delegation becomes an adopted thing). (If you run with this idea, consider AGPL for all parts :))

mariusor 3y ago
It would also require that (almost)all the existing fediverse services be redone from scratch because each of them owns the underlying ActivityPub actor (that represents a user) and are unable to work with one coming from a third party.
- 3np 3y ago
  Only in case of "proper" delegation, and in either case not "from scratch", I think.

erlend_sh 3y ago

What you want is account aliases: https://github.com/mastodon/mastodon/issues/3796 https://github.com/mastodon/mastodon/issues/3796

Kab1r 3y ago
I don't think that would suffice. I want all my data to be in one place, hosting one service, while still being able to use frontends for all of the different applications. It's a big ask for sure.