If Threads wants to join the Fediverse, will it be possible to view Threads content using FOSS frontends?
![](https://lemmy.world/pictrs/image/eb9cfeb5-4eb5-4b1b-a75c-8d9e04c3f856.png)
I see it as a win if all instances defederate with Threads but several "read-only" instances federates with it. At least it can be viewed in privacy friendly way.
Yes, that's the point
I'm pretty sure that would not be in Meta's best interest, from their point of view. After all, Meta is all about harvesting your personal data. I believe whether to federate or not will come down to how egregious the federation terms are that Meta will propose because you know they will want to access user data in some fashion for their own profit. If they want the same kind of data from the Fediverse as they get from their native app, the answer will be a resounding "no". If they ask for even 20% of that data, the answer will remain the same.
If things played out in just the right way, this could push them away from the Fediverse entirely, I'd think. Seems it would be hard to monetize any traffic coming from the Fediverse end of things, which would make the whole thing more of a headache than it's worth for them.
An instance that was explicitly set up as a read-only backdoor to Threads probably wouldn't stay federated long, but is a cool idea at least.
I don't know, they could be using the federverse as content provision. They get better data on all their users based on where they go and what they see on the federiverse.
Yes, and that's likely why Threads uses ActivityPub to begin with. See the EU's Digital Markets Act: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/digital-markets-act-ensuring-fair-and-open-digital-markets\_en
The interoperability is the big one. Being federated means that Threads isn't considered a "gatekeeper platform". I wouldn't be surprised if Instagram and maybe even Facebook itself start to federate as well. Since Threads isn't currently connected to the wider fediverse, that's probably why they're not in the EU yet.
This also means that fears of "Embrace, Extend, Extinguish" are likely overblown. Breaking fediverse interoperability means that they'd be a gatekeeper again and subject to EU regulations against gatekeepers. The whole reason why Facebook is making Threads ActivityPub is so they don't get hit by EU rules about being gatekeepers of content.
This means your normal fediverse apps (e.g. Fedilab) would be able to work with Threads natively, without any need for "read-only" instances like you say.
Does this also apply to Twitter? The EU regulations could be the only way to get projects like Nitter back.
Yes. Here are the timelines:
So we should start hearing things in about 2-3 months, with compliance in 8-9 months.
Relevant sections:
Pretty clear legislation - no lock-in, don't block access to content, you must publish your API for others to use. Very good legislation.
Threads should have an instance where there own users get there data plowed through by people who want it and sign up for it. But of course once they federate our instances will be free from advertisers. Thatās what itās all about each instance got itās own rules!