👏 Poison 👏 your 👏 data ☠️
-
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
We should tax corporations by the GigaByte of storage the own.
It doesn't matter what they use it for, it should have a tangible yearly cost, to make them think about how much they store.
-
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
@alice Enter your name as [object Object] and let them try to find a bug.
-
Poison your data 
️@alice a friend of mine changed his middle name to 'undefined', it caused so many problems he had to change it back within a year.
-
@alice I've toyed with the idea of setting up a headless Chrome instance to just ask "but why?" to ChatGPT all day to drive up their inference costs.
@theorangetheme @alice lol somebody has a toddler
-
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
@alice thank you! I've always wondered whether to put random made-up data but hearing the reasoning and logic spelt out like this is convincing me to actually start. Especially commonsense things like "mess with the fields that don't matter in their service to you"
-
@alice a friend of mine changed his middle name to 'undefined', it caused so many problems he had to change it back within a year.
@TheMightyGit @alice
Reminds me of someone who had the last name "Null" and had similar problems. -
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
Wrt #PII, It might be a good idea to avoid entering easily identifiable trash data, and use generators instead. E.g.:
-
R relay@relay.mycrowd.ca shared this topic
-
@alice I've toyed with the idea of setting up a headless Chrome instance to just ask "but why?" to ChatGPT all day to drive up their inference costs.
'and then?'
-
@neoluddite @aj @alice Just wondered what might happen if enough self-hosting people were to add an zero opacity image tag on their public indexable pages illustrating a d*ckbutt and having alt attribute set to Donald J. Trump.
-
Poison your data ️
yes, yes, a thousand times, yes!
-
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
This is the way. I've been doing this since 1997.
-
The goal is to make corporate data less profitable.
Even stuff as simple as setting your birthdate to 1970-01-01 everywhere, adding [TEST] or [DELETED] as your name or account notes anywhere you don't need them to know your name.
Using plugins like AdNauseam to poison ad trackers (and cost them marketing dollars).
Using VPNs set to different locations.
Signing into data broker sites to "correct" outdated info (they'll often let you do that with little-to-no proof of identity, but will require your passport or state ID in order to delete your info). Bonus points if you correct it to someone else's info on their site that's similar to yours.
Only fill in required fields when you sign up for anything, but only provide correct info if it matters for you to use the service, otherwise provide plausible, but incorrect, data.
If you use LLMs anywhere, use the free tier and always vote thumbs up for bad answers and down for good ones. It wastes their resources and drives up their costs while making their training data worse.
@alice Non-tech-savvy question:
Is there something special about 1970-01-01, or is it just an example of an arbitrary incorrect birthdate? Would it foul things up just as much if I entered, say, 1984-04-01? -
@miguelpergamon @alice No need for poison, just....Data is too valuable, so we're going to substitute the discount version, Ensign Anecdote.
-
@miguelpergamon @alice Yes, but he also recommended eating rocks because he found this one blog somewhere, so you'll have to forgive me for being a little skeptical of everything he says.
-
@alice Non-tech-savvy question:
Is there something special about 1970-01-01, or is it just an example of an arbitrary incorrect birthdate? Would it foul things up just as much if I entered, say, 1984-04-01? -
@miguelpergamon @alice That's different, that guy's got superpowers.
-
Poison your data ️
@alice How do?
-
Poison your data ️
@alice Oh, I'm here right to poison minds.
-
R relay@relay.infosec.exchange shared this topic
