- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
Meta’s microblogging platform and X rival, Threads, has taken another step closer to two-way connectivity to the Fediverse.
You can now follow fediverse accounts on Threads, but the accounts aren’t searchable and their posts won’t show in feeds
what’s the point then
Fediverse users are sceptical, so for now threads uses can only find users who willingly intact with people on threads. They’re taking a carefcareful approach.
I assume if threads users follow fediverse users the content makes its way to their feed as normal.
I assume if threads users follow fediverse users the content makes its way to their feed as normal.
Oh wow. They’re taking their sweet time.
Pretty useless then. Oh well, I’m European, and I am not aware of anyone in my network using Threads. So I can’t say I care all that much.
It says “Beta Feature” after all.
I’m not tho. Wish someone would just bridge everything into one platform seamlessly and the zealots could fight it out in the background.
Strong agree. Mastodon already works so that your feed won’t be filled up with shit you don’t want to see.
On a personal level, I couldn’t care less.
On a professional level, I want people to be able to follow me no matter which idiotic service they are using. So I’m bridging to Bluesky and I would be happy with my content being spread on Threads as well, though it doesn’t seem to attract many academic users. I have no idea who that platform is for. But if they’re interested in seeing my boring academic self-promotion, that’s cool with me.
Gross
My guess is that Threads implementation and Meta capital is necessary if ActivityPub and fediverse is to ever go mainstream. Mastodon just sucks too much and Threads might introduce some healthy competition that will make Mastodon survive long term.
I have no ideological problem with this. I believe that for-profit and non-profit complement each other. I’m a Social Democrat after all.
And I’m really annoyed by Mastodon instances that block Threads content. That’s just so extremely stupid from a fediverse strategy and a content quality perspective.
Large corporations tend to put profit over morality and the legal machinery to even try to bring them back into line moves slowly (and expensively) when they do so.
If your Mastodon posts are visible from Threads, Threads may “accidentally” determine that that content was posted by one of their own accounts covered by their own Terms of Service and so choose to do something with it that the Mastodon user did not agree to.
Now consider that Meta, Threads’ parent company has put things in both its Facebook and Instagram Terms of Service that say they can do whatever they like with content posted on their platforms, including feed it to any “AI” as they see fit.
And what about responses to Threads posts from the Fediverse? What rights do Meta have to those? I’m sure you can imagine what Meta thinks, or might allow themselves to think, in that regard.
Presumably you can now understand why some Mastodon instances (and other Fediverse places) don’t want anything to do with Meta or their products and wish to protect their users from that abuse.
You might argue that it will happen anyway, but in their view, any protection is better than none.
And the great thing about the Fediverse is that you’re welcome to find, or even run, an instance that leaves itself open to such “interoperability”.
But if they want to train AI, can’t they already scrape Fediverse since it’s open to everyone?
The hilarious thing is that if they did that the resulting LLM chatbot would shit on AI and large corporations constantly.