• Bleeping Lobster@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    1 year ago

    I wonder, could this problem be solved by adding some ‘junk’ data to each access request? With that junk data being a unique identifier, so the authorities can setup a sting to catch whoever is selling access

    • NounsAndWords@lemmy.world
      link
      fedilink
      arrow-up
      16
      ·
      edit-2
      1 year ago

      Without legislation forcing it, why would they bother? They already have enough separation from the crimes to avoid legal repercussions, and they get to sell data with the “this will be used for profitable criminal activity” premium baked into the original sale price.

      It’s like expecting Nestle to take any steroids action (weird auto-correct) to prevent child slavery. Why are they going to stir the pot and screw up the nice thing they have going?

      • unomar
        link
        fedilink
        English
        arrow-up
        9
        ·
        1 year ago

        I’m torn, but I think I’d take steroids to prevent child slavery.

      • Bleeping Lobster@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Slight tangent, but autocorrect seems to have gotten terrible the last year or so. My theory: as more and more people are using it, the initial dataset is being diluted by more and more bad typers. Instead of improving the dataset, it’s pulling it in so many different directions that it doesn’t know which way is up anymore