All the “but muh datas” pearl clutching is just annoying and frankly, ridiculous. If they wanted to mine us, they already would have. They’re probably doing it as we speak. They didn’t have to create a multi-million social network for it. A raspberry pi on someones desk would have sufficed. Fedi doesn’t have any (/very much) privacy.
They’re doing this to escape the wrath of EU privacy watchdogs. They were already fined for $1.3bn and more is coming. Running their Twitter killer on interoperable protocol is nice, because it’s free and they get to point at W3C and say they’re LIKE TOTALLY supporting data portability. Why would they “extend and extinguish” that? It’s their alibi.
I don’t like Meta. It’s a shit company ran by shit people. I hope they burn in hell.
But I can’t really get my panties in a twist about threads.net existing.
I’ll get angry if they somehow figure out to push ads to my face.
But for now. Maybe I’ll block it. Maybe I won’t. We’ll see.
Agreed it would be trivial for Meta to obtain the posts. But I think the concern of most people here isn’t Meta obtaining the posts, it’s Meta monetizing them through ads and training. Would it not be in our best interest to try to prevent this?
Oddly enough, my understanding is that in many jurisdictions it is a matter explicitly asserting these rights. Aside from that, requesting that they be enforced when they are violated.
Somehow I don’t think many instance admins have resources or knowhow to drive legal processes against Meta?
And while a disclaimer on the instance page might have some effect, the Federation protocol makes it hard to avoid getting a copy of the said content in your cache.
Yeah, that’s pretty much my take as well.
All the “but muh datas” pearl clutching is just annoying and frankly, ridiculous. If they wanted to mine us, they already would have. They’re probably doing it as we speak. They didn’t have to create a multi-million social network for it. A raspberry pi on someones desk would have sufficed. Fedi doesn’t have any (/very much) privacy.
They’re doing this to escape the wrath of EU privacy watchdogs. They were already fined for $1.3bn and more is coming. Running their Twitter killer on interoperable protocol is nice, because it’s free and they get to point at W3C and say they’re LIKE TOTALLY supporting data portability. Why would they “extend and extinguish” that? It’s their alibi.
I don’t like Meta. It’s a shit company ran by shit people. I hope they burn in hell.
But I can’t really get my panties in a twist about threads.net existing.
I’ll get angry if they somehow figure out to push ads to my face.
But for now. Maybe I’ll block it. Maybe I won’t. We’ll see.
Agreed it would be trivial for Meta to obtain the posts. But I think the concern of most people here isn’t Meta obtaining the posts, it’s Meta monetizing them through ads and training. Would it not be in our best interest to try to prevent this?
How do we accomplish that?
Oddly enough, my understanding is that in many jurisdictions it is a matter explicitly asserting these rights. Aside from that, requesting that they be enforced when they are violated.
Somehow I don’t think many instance admins have resources or knowhow to drive legal processes against Meta?
And while a disclaimer on the instance page might have some effect, the Federation protocol makes it hard to avoid getting a copy of the said content in your cache.
Agreed that instance admins might not be expected to handle this sort of thing.
Agreed that it is easy to get a copy of the content.
I think we might handle this best as a cumulative platform and community.