19
How do we feel about federating with Threads?
(kbin.social)
Did we not learn anything from Google and XMPP?
Refusing to federate with Threads would achieve exactly that outcome. Most people on Threads wouldn't know the Fediverse existed any more than most people on Google knew XMPP existed.
The Fediverse is struggling to get a large enough userbase to be as useful as the mega-services it replaces. Threads can gift that userbase and make people more aware that the Fediverse exists.
FWIW this is exactly why Threads didn't join the Fediverse until they'd overcome the legal obstacles to operating in the EU. If they'd federated first they risked losing all their potential EU users to the Fediverse.
The quickest way to lose this game is not to play it and the Google/XMPP example iillustrates why.
Alright, so the plan is to federate with Threads but to not implement any of their extensions?
I really don't see the issue. So more users is bad? I thought our issue is the lack of users currently.
I've seen people complain about ads and data harvesting here. But instances can already do that. Meta joining would change nothing about that. Actually, being a proper legal company, it might be easier to sue them over misusing your data than random instances.
"Embrace. Extend. Extinguish"? Let's stop between the last two steps then, not before the first one.
Kbin would be crippled by the amount of Threads content? I thought federation only happened if one kbin.social user is following a user on Threads? Should be as easily manageable then as Mastodon is currently. Or am I misunderstanding how this works?
To me, big sites federating looks like a clear advantage. I don't really get the big problem.
My understanding of the EEE doctrine is that the large company/userbase pervades, overshadows, and quite literally takes over, so the fediverse wouldn't really get a say in the matter.
So block them, block them hard, block them now and forever
I'm not super familiar with the right terminology, but in short I think users should be able to follow whoever they want, but restrictions on how it is interacted with is fair game. I think following and replying to threads accounts is sort of a must, even if boosting and other functions are disabled. Also on favor of preventing non-replies from being sent to threads.
The real issue issue is interop with Threads means surveillance of users. Limiting the info going from here to there is essential. However a read-only mode that lets us get some value out of it is fine
this post was submitted on 13 Dec 2023
19 points (100.0% liked)
Moving to: m/AskMbin!
22 readers
1 users here now
### We are moving! **Join us in our new journey as we take a new direction towards the future for this community at mbin, find our new community here and read this post to know more about why we are moving. Thank you and we hope to see you there!**
founded 1 year ago