- cross-posted to:
- fediverse@lemmy.world
- cross-posted to:
- fediverse@lemmy.world
This shouldn’t come as a huge surprise. Meta is moving forward with their plans for Theads and the Fediverse, and their adjusted terms reflect a new impending reality for Fediverse users.
Isn’t this just public information anyway, what’s the problem with them taking it?
It’s Meta. This is just the beginning. Stop them right from the start. Fuck these corporations.
How does defederating them stop them from getting this public information if they want it?
Good point. I guess they could just fire up a shell instance and get all the good stuff. I wouldn’t be too surprised, actually.
They don’t even need an instance to get they can just scrape it, like anyone can with public info. They wouldn’t even need to make an account for the scraper.
Public? Idk, maybe. I wouldn’t generally consider my IP to username to be public. Comment and post stuff, sort of. But even if it’s public, I still wouldn’t want Meta consuming it.
Are they talking about your IP address or the service’s? Does ActivityPub even share the user’s IP address with other nodes in the network? That’d be crazy, so I assume that it doesn’t. Then Meta can’t find out your IP address.
If a Threads user posts an image, and Meta hosts it, and I scroll through my feed and see it, my client will hit their server for said image. And Meta can collect my IP.
Meta basically invented this shit.
Because fuck them. This is step one of their 20 step plan to do evil shit.
What if my instance says other services and instances can’t do that? Are meta then breaking the law?