• Socsa@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    7
    ·
    edit-2
    1 year ago

    I don’t know if that’s a great example tbh. How does Google know it’s a medically necessary picture of a child’s genitals? Just don’t do that. Don’t send anyone pictures of your kid’s junk. Or anyone’s junk for that matter, except maybe your own if you really want to. Certainly not over unencrypted channels. That seems very obvious to me. If your kid’s dick is falling off, go to the ER

    • deweydecibel@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      1 year ago

      You missed the point of the examples.

      They’re cases of people who did nothing wrong but none the less found themselves in trouble because they didn’t appreciate how their privacy was being invaded. You can argue about the merits of invading one’s privacy to look for child porn, but it is an invasion of privacy, and it’s one that a tremendous amount of people are complete unaware of.

      That man presumed his phone was secure, and presumed the channel to his doctor was secure. So he sent sensitive images believing the only people that would see them would be the recipient, a licensed medical professional who presumably asked for or at least expected the photos. If what he believed had been true, there’d be no story.

      He didn’t realize that his photos were synced to g-drive, and he didn’t appreciate that images backed up to a cloud are not private, and that no matter what the context, those images would trigger a response. These are all things they were ignorant of until it was too late.

      The larger point is that he is not alone. A lot of people truly don’t appreciate just how much information of theirs is out there on somebody else’s computer, and they do not have the knowledge or the imagination to know how much trouble they could be in one day.