@DavidBHimself @dansup I also think it is wrong to apply blocks on interoperability and freedom of communication - by the very people who stand in the heart of fediverse applications, and in such authoritarian way.
Instead of fixing some of the fundamental gaps of your platform, like inability to set detailed dynamic locations to Pixelfed posts as on Instagram, you have spent time and effort on something taking your community away from other popular authors.
Yes, this is a terrible move in so many ways. Especially #PixelFed of all platforms. All users of #Threads are #Instagram 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 #Fediverse and the #OpenWeb.
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.
