Welp, I‘m not gonna see it. My admin blocked threads.
While I am excited at this integration I hope the people at threads would shift to mastodon instead of the opposite if threads ever try to do an EEE move.
More like when than if. They’re already blocking pixelfed. So when is um now
and threads users can’t see the mastodon users comments for now. i think they will prolong this as long as they can while introducing other stuff so that they can force other people to download threads for making comments that they can see.
They’re blocking Pixelfed? In what way?
Blocking Pixelfed from federating with Threads?
Preventing people from mentioning Pixelfed?
under normal circumstances? why would they. but if threads keep rigging the fediverse integration part people might think it’s better to be on threads since the integration is bad even if threads clearly do it to rig the competition.
honestly feel like the instances that are blocking @threads.net before it was even released are missing the point of activitypub and federation completely and are becoming the same type of closed systems that they left before coming to mastodon.
personally i love seeing how excited the threads devs are about activitypub. watching them demo fediverse sharing was super awesome - i hope more socials embrace it. i’d love to see bsky be able to share with activitypub and at proto soon too.
The problem with federating with Threads is that then anyone who wants to join the Fediverse will just join Threads (especially the people already using Instagram or Facebook), leaving the success or failure of the Fediverse in the hands of a company whose interest is to attract as many people as possible to its platform, not contribute as an even partner in a federation.
The problem with federating with Threads is that then anyone who wants to join the Fediverse will just join Threads (especially the people already using Instagram or Facebook), leaving the success or failure of the Fediverse in the hands of a company whose interest is to attract as many people as possible to its platform, not contribute as an even partner in a federation.
says who? and you could just replace threads with mastodon.social in your statement
From what I found, a lot of the people who join Threads, wouldn’t have even looked into joining the Fediverse in the first place. If anything, Threads is bringing the concept of the Fediverse to more people and some of those people may find that Mastodon and the rest of the Fediverse could be what they prefer, especially if you can still talk with your family and friends on here.
Threads are stuck behind dealing with their investors as we can push the Fediverse with new updates all the time
Those that are on Threads are likely not even aware of the rest of the fediverse. I think that when they interact with us they will be. And when Meta decides it’s time to start ads some people will think it’s better over here. Also, some people won’t like Threads using an algorithm on their feed.
If the instance owner doesn’t block it would we be able to block all threads (and twitter) on our profiles?
Yeah in mastodon you can block a whole instance. That’s why some servers are against threads but don’t want to defederate as they see it as the users choice
There’s also some sort of soft blocking option, which largely hides the instance AIUI but still gives the ability to follow users. This seems like a better option rather than completely defederating.
If Meta want to scrape your data they can do that anyway. All defederation does is stops you looking at their stuff (which, as you say, can be blocked at the user level anyway)
