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.
If your instance starts to try to “convert” people off of Threads, they can (and will) just block you.
And then responded to it by saying:
…why would they do that?
That is literally asking why they would block instances trying to convert users into fediverse users instead of Threads users.
Do you work with Meta?
Do you?
me: Data portability is being solved with export standards, so that users can (more) easily migrate to other services.
you: Are you not aware that WhatsApp is also interoperating to comply with DMA? Another Meta company?
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.
“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.
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?
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.
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.
Yes. Your comment here: https://beehaw.org/comment/3046503
Here’s a screenshot of you literally saying what I quoted:
Hope this helps.
Removed by mod