Yeah. That’s what I said

In this case, the “lemmy devs” and the operators of lemmy.ml are the same people and it’s hosted within EU.
But - that’s still a far cry from getting any kind of GDPR violation report going, much less getting it through the process to actual fines.
People like to bring up GDPR violations as a some kind of super-moderator tool, but it isn’t that easy and it definitely isn’t automated.

Effect of ActivityPub, not Lemmy. All federating systems function similarly, because it’s a feature of the protocol.
If instances want, they can ignore delete requests and your content stays in their cache forever (remember Pleroma nazis from couple of years ago?) - now, that is an instance problem that might be a GDPR issue, but good luck reporting it to anyone who cares. At best you can block and defederate, but that doesn’t mean your posts are removed.

The fediverse has no privacy, it’s “public Internet”. Probably a good idea to treat it as such.

It’s also a matter of scale. FB has 3 billion users and it’s all centralized. They are able to police that. Their Trust and Safety team is large (which has its own problems, because they outsource that - but that’s another story). The fedi is somewhere around 11M (according to fedidb.org).
The federated model doesn’t really “remove” anything, it just segregates the network to “moderated, good instances” and “others”.

I don’t think most fedi admins are actually following the law by reporting CSAM to the police (because that kind of thing requires a lot resources), they just remove it from their servers and defederate. Bottom line is that the protocols and tools built to combat CSAM don’t work too well in the context of federated networks - we need new tools and new reporting protocols.

Reading the Stanford Internet Observatory report on fedi CSAM gives a pretty good picture of the current situation, it is fairly fresh:
https://cyber.fsi.stanford.edu/io/news/addressing-child-exploitation-federated-social-media

This is a good start: https://cyber.fsi.stanford.edu/io/news/addressing-child-exploitation-federated-social-media

I find it interesting that Meta Platforms, Inc., a company known for harvesting user data, is blocking some servers from fetching its public posts. They decided to implement a feature Mastodon calls Authorized fetch.

This was always going to happen. They will block agressively, because they can’t have their precious advertising money mixed with CSAM, nazis and other illegal content. And the fedi is full of that.

I hope not

I’ve been using Debian since 1.3. Haven’t really ever needed anything else.
I did “experiment” a bit when the decision to go with systemd was taken, but in the end, most distros went with it and it really isn’t that big deal for me.

So it’s just Debian. I need a computer that works.

Pleroma in that case I guess

Gates is probably just as bad and evil as the global 0.1%:er billionaire cabal members come, but that site gave me a crackpot conspiracy brainrot.

It’s wild that a site with hundreds of millions of users, didn’t invest into multiple-account deletion tools.
True start-up mentality, that one.

Just shows how our “critical” social media is really just some hasty tape and bubblegum behind the scenes to keep the front from falling apart.

I guess majority on fedi are dumbasses in that case ¯\_(ツ)_/¯
Mastodon is pretty fucked up anyway because everyone is on mastodon.social.

Because the people signed the pact did it long time ago, before any details about Threads federation was known. It was a typical fedi kneejerk reaction.

It’s a silly hashtag för instances that are in a “pact” to block Threads

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.

How do we accomplish that?

Why spend the money up front? That’s just bad business.

Yeah agreed. They’re building a multi-million dollar social network - why spend all that money up front when they could have just installed small anonymous Pleroma on Raspberry Pi for under 100 bucks if they’d wanted to mine our data.

I don’t think fedi is their “target”.

I bet he does. You can block/mute influencers pretty easily and you can block the whole domain if you so wish.
He’s talking about some kind of nefarious ad injection into ActivityPub objects as part of server to server activities.

I think he’s talking about people on his own instance.
He’s Fosstodon admin, so pretty sure he knows how federation works.

doesn’t mean we have to hand it to them on a silverplatter and allow them to scrape it legally

They could have just set up a simple Pleroma on Raspberry Pi and it would have been just as “legal” as any other instance. You’d need to turn on AUTHORIZED_FETCH and set up authentication on the Mastodon API, otherwise everything is public and unauthenticated (even if the instance is suspended/defederated).

But if enough instances say no, that means they are not welcome. Democracy and all

mastodon.social has already said yes. So have all the other big instances. Most of them have said “we’ll wait and see”. So democracy served I guess

And the last point is the dumbest: Threads will just include a revenue sharing model like Youtube does

Yeah, maybe. Who knows. I’ll deal with it when it happens rather than knee-jerk years in advance. Threads has a long way to go, it’s missing a lot of features to put it on par with their other commercial competitors, so I think they’re going to be busy doing other things.