-

2025-01-25 17:44:19

DavidNason@caneandable.social

Forgive the possibly stupid question, but… If I were to join #PixelFed, is that a totally separate account to this #Mastodon account? And then what is #Loops? #fediverse #Fedi #FediHelp

2025-01-25 18:43:31

Oblomov

oblomov@sociale.network

@DavidNason you can interact (follow/like/boost/comment) with PixelFed accounts without a new account, but if you want to join a PixelFed instance that'll be a separate account.

2025-01-25 18:51:28

FoolishOwl

foolishowl@social.coop

@oblomov @DavidNason As I understand it -- and from my experience with Bookwyrm -- you can follow a Pixelfed account on Mastodon, or vice versa. But there's no single sign-on.

2025-01-25 19:21:05

Mark Stosberg

markstos@urbanists.social

@foolishowl @oblomov @DavidNason Using these services from a single account could be made to work in the future, but doesn’t now. For example, it’s already possible for post and comment on Lemmy using a Mastodon account.

More interoperability can be expected over time.

2025-01-26 01:06:34

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@David Nason Pixelfed is wholly separate software from Mastodon on wholly separate servers with wholly separate owners. So yes, you need a separate Pixelfed account. It's a bit easier on Pixelfed if you're already on Mastodon: Pixelfed lets you automatically create a new user account by "logging in" with your Mastodon login credentials. But only Pixelfed has this as far as I know.

Loops is wholly separate again, but there's only one instance so far because it's too unfinished to even be open-source. So you'll need a Loops account next to your Mastodon account and your Pixelfed account.

Also, you'll have different followers on Mastodon, on Pixelfed and on Loops. But what you could do if you want your followers on Mastodon to see your Pixelfed posts is: Follow your own Pixelfed account from Mastodon. And then, whenever you post something interesting on Pixelfed, wait for it to arrive on your Mastodon timeline, and then boost it.

@Mark Stosberg There's one thing that exists already now: OpenWebAuth magic single sign-on. But it's only available on Hubzilla, (streams) and Forte and partially on Friendica.

What it does is recognise your login on another instance, even on an instance of another server application. Hubzilla, (streams) and Forte recognise logins from Friendica, Hubzilla, (streams) and Forte, but Friendica can't recognise logins.

However, this is only used by the permissions system. For example, someone whom I'm connected to could have made their profile only visible to a certain subset of their connections, including myself. If you visit their profile, you won't see anything. If I visit their profile, their home instance recognises my Hubzilla login, and I can see the profile.

What it does not do is give you the same full-blown rights as a user with a local account. I can't just, like, go to some (streams) instance and post away as, what, jupiter_rowland@rumbly.net or go to a Hubzilla hub where I don't have an account and create a webpage or a wiki or a CalDAV calendar right away without logging in. That's not how it works.

By the way, client-side OpenWebAuth support (= your login is recognised on Hubzilla, (streams) and Forte) was proposed and actually developed to the point of a pull request for Mastodon. As far as I know, it was rejected. OpenWebAuth won't come to Mastodon.

CC: @FoolishOwl @Oblomov

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #Friendica #Hubzilla #Streams #(streams) #Forte #OpenWebAuth #SingleSignOn