The GPDR doesn’t require Lemmy to remove personal data from the entire internet. But when a Lemmy instance gives data to other Lemmy instance, there are legal responsibilities.

https://gdpr-info.eu/art-17-gdpr/ Where the controller has made the personal data public and is obliged pursuant to paragraph 1 to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform controllers which are processing the personal data that the data subject has requested the erasure by such controllers of any links to, or copy or replication of, those personal data.

==========

Maybe this is open to interpretation, but I feel that the same Federation protocol that federates out my personal data (my posts and comments), should also federate out my delete requests. I’m unsure why this would be controversial.

Oh my, you are correct. Images are being federated some of the time.

Like most everything else, the intended behavior isn’t documented anywhere.

Media isn’t federated. The media should just be referenced with a link to the original source.

Normally, the largest use of disk space is the Activity table. It is stored for six months, and only useful for debugging. Below is the Issue, along with SQL commands to check and purge this debugging table. Let us know if this was the issue

https://github.com/LemmyNet/lemmy/issues/3103

See https://gdpr-info.eu/issues/right-to-be-forgotten/

Once the “controller has made the personal data public”, they have legal obligations. When you send an email, you are not making it public.

See https://gdpr-info.eu/issues/right-to-be-forgotten/

Once the “controller has made the personal data public”, they have legal obligations.

Lemmy still has some issues that need to be addressed for it to fully replace Reddit for my needs

Be honest, do you still use reddit?

good job

There is no easy way to do this. Each Lemmy instance uses their own autoincrement ID for posts. So post 12345 here might be post 54321 on another instance.

It has been suggested that each post gets a universal ID (UUID is an example). Then the local server could just examine the URL and redirect the user to the local post. This suggestion hasn’t gotten any traction. The dev team is more focused on fixing the huge performance issues right now.

But when you first subscribe, you’d expect to be missing old posts

OP didn’t expect to be missing old posts, hence his question. I had the same surprising discovery. Not sure how the UX could be improved to convey to the user what is actually happening.