πŸ‘ 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.

@alice NULL is also a good answer for when you don't want to give out a particular personal detail.

Aside from phone, date of birth, and email, most of the time the front end form fields will accept NULL as an answer.

https://en.wikipedia.org/wiki/Null_(SQL)
Null (SQL) - Wikipedia

@aj @alice Mind you, a well designed application should not interpret a string saying null as a null value.
You probably won't pull a Bobby Tables off on Facebook.
@flesh @alice @aj Probably not. However, corpo software is not always well-designed, and the current crop of layoffs + executives vibe coding make those sorts of vulnerabilities more likely.

@rabidchaos @flesh @alice @aj
If it is treating that null as a proper null there's a good chance there's constraints in place that'll fail and the app won't even check the failure...

Which can be fun, or not, depending on if it counts you as logged in after you submit the form or not