Are you going to explain what UGC means?
I would guess he’s talking about “user-generated content”, given context.
Comment on [deleted]
helenslunch@feddit.nl 8 months agoThis is completely false.
It’s absolutely not.
The entire reason they’re federating is to instantly get access to a much larger pool of UGC for their users to interact with
Are you going to explain what UGC means?
The reason they’re federating is because of the Digital Markets Act. Same reason WhatsApp is going to interoperate.
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.
Okay, and? What instances do you think they’re going to choose and why?
If your instance starts to try to “convert” people off of Threads, they can (and will) just block you.
…why would they do that? Why would they introduce something new just to turn around and try to prevent you from using it?
They don’t need us for users, they need us for content.
LOL they only need us to comply with regulations. You said it yourself, they have hundreds of millions of users, they don’t need more content. And they sure as shit don’t need content from users that overwhelmingly hate Meta.
tal@lemmy.today 8 months ago
t3rmit3@beehaw.org 8 months ago
“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.
helenslunch@feddit.nl 8 months ago
No, that’s not what I asked. And you know it’s not. That’s why you tried to rephrase my question.
Do you work with Meta?
Are you not aware that WhatsApp is also interoperating to comply with DMA? Another Meta company?
t3rmit3@beehaw.org 8 months ago
Yes, it literally is. I said:
Which you then responded to by saying:
That is literally asking why they would block instances trying to convert users into fediverse users instead of Threads users.
Do you, to back up your claim?
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).
Interoperability is the ability for users of one platform to interact with users of another platform, without platform-imposed loss of functionality.
helenslunch@feddit.nl 8 months ago
I mean, you can lie about it, but everyone can see it, so I don’t know who you think you’re fooling.
You’re wrong. I’m talking about interoperability. You’re the only one talking about portability.