119
Fedi Garden to Instance Admins: "Block Threads to Remain Listed"
(wedistribute.org)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
This is completely false. The entire reason they're federating is to instantly get access to a much larger pool of UGC for their users to interact with. And of course they get to also choose who to federate with and who to block, so they can choose instances that have the kind of content they want, all for free, while suppressing instances they don't like. If your instance starts to try to "convert" people off of Threads, they can (and will) just block you.
Threads has more users than ALL fedi.db-tracked fediverse instances combined (Threads: 160m, Fediverse: 10m). They don't need us for users, they need us for content. Just like Reddit, there are usually a few dedicated 'content generator' users on any given instance, who post the bulk of the UGC. Gaining access to those is Threads' goal. Federating is how they achieve that.
"User-generated content". Posts, comments, uploaded files, etc.
Why would they try to prevent users from migrating away from their service? Are you seriously asking this?
You have asserted this in multiple comments, but the only site I can find asserting this link is a blog post by someone who admits to having only a "surface-level understanding" of DMA, and thinks that this is gaining them data portability.
As someone who works at a very large company that is also affected by DMA, this is not how any company whose legal teams we've spoken with are interpreting this requirement. Data portability is being solved with export standards, so that users can (more) easily migrate to other services. Streaming someone's data over to another platform where they may or may not have an account, or ever intend to go, wouldn't fulfill that requirement, because if the user wishes to move to a non-federated instance, that would not be possible. Portability also cannot be 'favored' under DMA.
That is a separate issue from interoperability, which only works if Threads is allowing federated instances to fully interact with their users' posts, with no loss of functionality, which was at least originally not the plan.
Yes, it literally is. You quoted where I said:
And then responded to it by saying:
That is literally asking why they would block instances trying to convert users into fediverse users instead of Threads users.
Do you?
I think you are conflating portability with interoperability. Those are 2 separate requirements.
Portability is about preventing platform lock-in, making it so that users can leave a platform (i.e. Threads), and take their data with them to another platform (any platform, not just ones of the originator's choosing). This is not solved with federation.
Interoperability is the ability for users of one platform to interact with users of another platform, without platform-imposed loss of functionality. Whether ActivityPub can serve as a replacement for an API is something that courts in the EU would have to decide. It is certainly not 1:1.
Yes. Your comment here: https://beehaw.org/comment/3046503
Here's a screenshot of you literally saying what I quoted:
Hope this helps.
I would guess he's talking about "user-generated content", given context ("they need us for content").
Even defederated instances can get UGC