p.s. Please do read the link in the post, it really does answer a lot of common questions about Pixelfed! 🙂

Here it is again:

➡️ https://fedi.tips/pixelfed-photo-sharing-on-the-fediverse ⬅️

p.p.s. A lot of people asking how they can crosspost from Mastodon to Pixelfed. The answer is this:

You do not need to crosspost from Mastodon to Pixelfed. Your posts on Mastodon are already visible to people on Pixelfed, because Mastodon and Pixelfed are both part of the same social network.

(The same in reverse, posts on Pixelfed are visible to people on Mastodon.)

Some of the accounts you see on here are Mastodon, some are Pixelfed, some are other types, but you can follow all of them.

p.p.p.s. People asking about the "log in with Mastodon" option on Pixelfed, the short answer is: you probably shouldn't use this option.

Longer answer: the "log in with Mastodon" option on Pixelfed doesn't actually do what it claims. What it actually does is create a new Pixelfed account for you, and copies over some of the information from your Mastodon account onto that new Pixelfed account.

You end up with two separate accounts (Mastodon and Pixelfed) without any connection between them.

for many/most folk and situations I agree. There are some specific use-cases for this; eg what we've setup on zeroes.ca where the mastodon account is used to sign into a closed pixelfed server, so a second username+password are not required and admins effectively don't have to manage a second user directory.

"Sign in with" is kinda the de facto language for oauth/sso across the web and it mostly operates like this, where the site being logged into essentially creates an account for the user without requiring them have another set of credentials. Doesn't mean it's not confusing, though.

"where the site being logged into essentially creates an account for the user without requiring them have another set of credentials"

SSO that works like that would be fine on centralised sites that have no interoperability with the source of the SSO account.

But SSO like that isn't suited to an interoperable decentralised platform on thousands of servers... it's going to confuse people as they will end up with lots of unconnected but interoperable accounts.