Comment on [deleted]
helenslunch@feddit.nl 8 months agoWhy would they try to prevent users from migrating away from their service? Are you seriously asking this?
No, that’s not what I asked. And you know it’s not. That’s why you tried to rephrase my question.
this is not how any company whose legal teams we’ve spoken with are interpreting this requirement.
Do you work with Meta?
Data portability is being solved with export standards, so that users can (more) easily migrate to other services.
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.
t3rmit3@beehaw.org 8 months ago
Yes. Your comment here: beehaw.org/comment/3046503
Here’s a screenshot of you literally saying what I quoted: Image
helenslunch@feddit.nl 8 months ago
I do not need your help reading my comments. You need help reading them.