Yes, this is a terrible move in so many ways. Especially of all platforms. All users of are users. All of 100 million or so of them. And instead of showing them that there is another way, PixelFed is shutting the door on their face!

I have yet to see a worse way to promote the
and the .

I just can't understand this decision.

When a random instance is preemptively blocking Threads, they're only hurting themselves, but a flagship instance?
They think they're "fighting" Meta, but all they're doing is hurting their users and hurting Threads users, who are our friends and families, the people we want to bring over to the Fediverse.

Just when I was starting to love PixelFed and wanted to start promoting it more, I'm seriously reconsidering now, and will probably leave the thing altogether. What's the point of even changing instance when the flagship and the developers are acting against the Fediverse.

This is really upsetting.

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
dansup

@DavidBHimself @alexgranford I should make this clear that this is only for pixelfed.social and pixelfed.art, and it's quite easy to opt-in to Threads federation.

Did you know that Threads is doing the same thing?

1
11mo
Replies