• 4 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle





  • digdilem@feddit.uktoMildly Infuriating@lemmy.worldThanks Spez!
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Ah yes, the “Right to be forgotten”

    You are correct, of course. However, they are well within their rights to not delete your data. Look up “Legitimate interest” - it’s a huge GDPR loophole and widely abused. (Certainly in charity fundraising in which I used to work)

    The LI can be for their own business purposes, including profiling, machine learning and of course, advertising.

    It can also, and usually is, need to keep data in case they receive a legal order to provide it. In the event of Reddit being used for terrorism purposes (which I’m sure it has, along with every other messaging platform), they will be required to produce that information. Which they can’t if it’s gone.

    We wave the GDPR around like it solves all our problems. And whilst it does add a huge amount of public protection and it’s impressive it made it into law given those objecting to it, it does not give you the right to your own data above all else.


  • digdilem@feddit.uktoMildly Infuriating@lemmy.worldThanks Spez!
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 year ago

    Whilst I totally understand your comments and even appreciate them, I still believe I am right.

    About four years ago I used NukeReddit - a similar script that loads your comment history, edits each posts, replaces the text with nonsense and saves it. Then deletes the post. I did that because someone got close to identifying me IRL and I didn’t want them to, and wanted to tidy up my own data leakage.

    After that, I continued using Reddit until the recent nonsense when I decided to leave to good. First, I used Power Delete, repeating it over several days to delete thousands of comments and hundreds of posts. About a week after that, I submitted a GDPR data request. Another week, I deleted my account. About a week after /that/, I received the GDPR response containing several CSV files containing my data. That included posts and comments I’d made from 11 years ago when I had created that account.

    That data had survived two quite thorough scrubs and deletions, and whilst I no longer have access to that account, I believe my data and my account are still there - just unavailable to me.

    I do know a little about data and databases, and in many mature projects, deleting posts simply sets an is_deleted column with the date it’s deleted. Editing a message simply creates a copy of that message, sets the original as is_deleted with a date, and sets the copy with the edited text. That’s standard and honestly, I don’t know why Reddit would not do that.

    Also consider that Reddit may be under a legal obligation NOT to delete data. If there is a criminal investigation at a later date, they will need to be able to provide that information. “Sorry Mr Government, we deleted Bin Laden’s posts where he incited terrorism to dozens of other suspects” is not going to be received well.

    The bottom line is that only Reddit architects will know for certain, but I’d put real money on betting that I’m right.#




  • Nice quote - but I don’t think it does hold up as truly as it did in the 80s. There is an unimaginable wealth of systems and design tools available now that were not around then. Even something take for granted like a gui schema designer - hell, even SQL itself wouldn’t be around until almost a decade later, and that was partly designed to simplify database queries. Every step like that has simplified what we do today. Debugging tools are light years ahead of when I was writing C in the early 90s. Debugging then was pretty much “try and compile it and then fix the errors”. Now there’s linters, memory profilers, automatic pipelines and all the rest of that. Much of that is offset by the fact we do far more complicated things than we did, and that those very tools mean there’s a lot more to learn and master beyond the mere language.

    I do concede and agree with your last paragraph. Design is more important than implementation, and elegance of code and concept is a timeless beauty. One of the hardest things I’ve had to learn is that thinking about coding is often far more productive than actually coding, and too many times I’ve been a busy fool, re-writing and starting over many times because I later found out a better way.









  • Nah, it’s fine. Boot times are considerably faster than sys.v in most cases, and it has a huge amount of functionality. Most people I work with have adopted it and much prefer it to the old init.d and sys.v systems.

    People’s problem with systemd (and there are fewer people strongly against it than before) seem to break down into two groups:

    1. They were happy with sys.v and didn’t like change. Some were unhappy with how distros adopted it. (The debian wars in particular were really quite vicious)

    2. It does too much. systemd is modular, but even so does break one of the core linux tenets - “do one thing well”. Despite the modularity, it’s easy to see it as monolithic.

    But regardless of feelings, systemd has achieved what it set out to do and is the defacto choice for the vast majority of distros, and they adopted it because it’s better. Nobody really cares if a user tries to make a point by not using it any more, they’re just isolating themselves. The battle was fought and systemd won it.