I’m getting a bit sick of large corporations a) demanding excess data as a condition of doing business with me, b) allowing it to be stolen, and c) giving zero fucks about it.

What are some things that us netizens can do to make our displeasure known.

Extra points for funny ideas.

  • OsrsNeedsF2P@lemmy.ml
    link
    fedilink
    arrow-up
    6
    ·
    7 hours ago

    Report bugs that don’t actually exist. Keep reporting the same bug from different emails. Works especially well for apps.

  • MojoMcJojo@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    8 hours ago

    Do not use actual names, birthdays, phone numbers, addresses, email addresses, etc. There’s no reason they need to know that info and I love/hate seeing physical mail and email show up with my made up info. Doesn’t work when paying for stuff though.

  • Captain Aggravated@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    20
    ·
    12 hours ago

    Stop using as many services as possible. It might not be funny but, I mean, what if you went to a music store and bought used CDs instead of using Spotify? Do all of that you can.

  • JoeKrogan@lemmy.world
    link
    fedilink
    arrow-up
    20
    ·
    12 hours ago

    Use bots to apply for the open positions to waste time. Reject them all for not enough pay.

    Post public info of the CEO class

    Piracy

    Give fake data when using all services.

    Start and join boycott groups.

    Use their social media against them. Eg post their dirty laundry as a comment on their post.

  • QuantumEyetanglement@lemdro.id
    link
    fedilink
    English
    arrow-up
    4
    ·
    8 hours ago

    If anyone has one specifically for airlines, I’d love to hear it! Got plenty of time to read the comments with my cancelled flight

  • GHiLA@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    9 hours ago

    he doesn’t rename low res episodes of the golden girls to “tax return[year].docx” and hide them in plain sight.

  • bufalo1973@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 hours ago

    If someone stoles the data then the corp can’t be trusted. Punishment: erase ALL records from ALL of their databases and forbid that corp to take data for at least one year. The time would depend on the severity of the leak. If the leak if catastrophic, 10 years minimum.

  • hansolo@lemm.ee
    link
    fedilink
    English
    arrow-up
    21
    ·
    20 hours ago

    If a company is publicly traded, then all leaked individuals are given 50.1% controlling stock in the company, split among the victims with new stocks created for them, with unclaimed stocks held in a trust controlled by anyone that did respond to claim stocks. They can sell the stocks, or drive the company into the ground out of spite. Maybe even both.

    Companies not publicly traded have 3 months to make all code used, trademarked material, and patents open source in perpetuity, and 1 year to convert their corporate structure into a non-profit.

    Regardless of the size of the company, the CEO, CTO, and board must eat their weight in fried bugs. They get to pick the type of bug from a list of 5 options, and any seasoning they want. Live streams of the bug eating will be monetized and the proceeds given to orphans, under the title of “It’s not a bug, its a feature.”

  • BigDanishGuy@sh.itjust.works
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    19 hours ago

    Edit: whoops, I missed the “il” part in “not illegal”. Anyway you should definitely not do the following. Allegedly doing the following would be arson, and society frowns upon such things.

    Easy:

    1. Identify company
    2. Wait until it’s a weekend night. We’re not after the wage slaves after all.
    3. Mix polystyrene and gasoline. Remember that gasoline can melt some plastics, so if using a plastic container for mixing do a test first. You do not want napalm all over the place.
    4. Fill the gooey substance in glass bottles.
    5. Cap the bottles. (see #7)
    6. Drive to the company.
    7. Open bottles and put wicks in them. (important not to do this earlier. Driving with open gasoline containers in your car will make you drowsy and is a fire hazard)
    8. If you haven’t already got gloves on, put them on and wipe down the bottles - you may have to leave some at some point.
    9. Have accomplices trigger fire alarms all over the local fire department’s district. Either automatic fire alarms will be discarded for a bit or the marshall will be tied up investigating.
    10. Light a wick, throw the bottle at the company, try to get it to break a window.
    11. If you’re out of bottles or you see blue lights cheese it. Otherwise go back a step and repeat it.
      • PM_Your_Nudes_Please@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        9 hours ago

        It’s an SQL injection joke.

        Basically, when dealing with databases, you can use SQL to search or modify the data in that database. By default, you can do this by polling the database with an SQL query. But this introduces a vulnerability called SQL injection. Basically, imagine if instead of filling in a name in the “Name” field, you filled in an SQL query. If the database admins haven’t protected themselves against it, then the database will happily run that query; You have just injected an SQL query into their database. Maybe you’re a malicious attacker, looking to get a virus onto the system, or looking to extract the data.

        Protecting the database from injection is done with something called sanitizing. Basically, you set up filters to disallow SQL, so it can’t touch your database. In this comic, the database admins didn’t do that, so they were unprotected.

        The actual SQL uses the student’s middle name to search for any tables named “Students” and permanently delete it. The joke is that when the school admin staff enters his name into their database, it will delete any tables named “Students” and wreck their database.

        • mnemonicmonkeys@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          19
          ·
          1 day ago

          Still, any programmer worth their salt should filter their inputs. One group at work refuses to do it and they always get away with it and it’s infuriating

          • PM_Your_Nudes_Please@lemmy.world
            link
            fedilink
            arrow-up
            4
            ·
            9 hours ago

            One group at work refuses to do it

            Sounds like a huge liability to the company.

            and they always get away with it

            Until they don’t. All it would take is one malicious actor (competing company, spurned employee, data thief, etc) wrecking/stealing their entire database with an injection attack.

            • mnemonicmonkeys@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              8 hours ago

              Their exact position would make it significantly less likely, since they aren’t working with databases, but software for individual products. That being said, it’s still shitty practice

  • slazer2au@lemmy.world
    link
    fedilink
    English
    arrow-up
    93
    arrow-down
    5
    ·
    1 day ago

    Use EICAR test strings as your password.

    If they store your password in plain text the AV will lock the user database.

    If your password gets leaked and they are using bad password security, when your password is cracked the AV will isolate the file.

      • PM_Your_Nudes_Please@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        9 hours ago

        EICAR test strings are strings of text that can be used to test an antivirus. Basically, you bury the file somewhere, and see if your AV picks it up. The joke being that if they’re storing your password in plaintext (a big no-no from a security standpoint) then their AV will clamp down on the database once you create your account and the test string is embedded.

        It wouldn’t work in this instance, unfortunately; EICAR test strings are only meant to work when embedded in files that are shorter than 128 bytes. And every database is almost certainly larger than that.

    • shrodes@lemmy.world
      link
      fedilink
      English
      arrow-up
      69
      arrow-down
      1
      ·
      1 day ago

      Bold of you to assume a corporation storing passwords in plain text would be using AV

    • qaz@lemmy.world
      link
      fedilink
      English
      arrow-up
      38
      ·
      1 day ago

      According to EICAR’s specification the antivirus detects the test file only if it starts with the 68-byte test string and is not more than 128 bytes long. As a result, antiviruses are not expected to raise an alarm on some other document containing the test string.

      This won’t work, assuming the database file is more than 128 bytes long

      • Talaraine@fedia.io
        link
        fedilink
        arrow-up
        8
        ·
        1 day ago

        I think the important distinction would be ‘file’ or ‘record’. Passwords aren’t really a file in a database iirc and records in a database have a storage limit