Programmer Humor

19809 readers

274 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

[email protected]

993

Detailed Error Messages (lemmy.zip)

submitted 4 months ago by [email protected] to c/[email protected]

76 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] x00z 3 points 4 months ago (1 children)

None of these require your account to “exist”.

It's actually much more technical than theoretical. When you delete an account on a website, that is being kept for a little while longer, it merely has field in the database that gets updated. (often with a removal date as well for the automatic removal after x amount of days). This field needs to be checked everywhere the account is used. And account recovery is mostly a part where this is forgotten, or possibly not even wanted.

And to claim this as fact, I just realized that the website I work on allows recovering of banned accounts. (Removed accounts are completely removed though because we don't need to retain any data).

This is the only valid reason. But even then this could be stated so that the user is fully aware.

Keeping the records for a little while longer is actually implied to be known. It's in their privacy policy, and is legal.

Whether or not services should make this easier to know exactly what is happening I definitely agree. Personally I think post history without user identifiable data should also be removed, but this is even less common practice (and is why tools exist to delete all your reddit posts for example).

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago) (1 children)

This field needs to be checked everywhere the account is used.

Usually something like this would be enforced once in a centralized location (in the data layer / domain model), rather than at every call site.

for the automatic removal after x amount of days

This gets tricky because in many jurisdictions, you need to ensure that you don't just delete the user, but also any data associated with the user (data they created, data collected about them, data provided by third-parties, etc). The fan-out logic can get pretty complex :)

[–] x00z 2 points 4 months ago

Usually something like this would be enforced once in a centralized location (in the data layer / domain model), rather than at every call site.

True. Although not every endpoint is the same, nor is every website or service.

This gets tricky because in many jurisdictions, you need to ensure that you don’t just delete the user, but also any data associated with the user

GDPR specifically mentions user identifiable data. I don't know about others.