3 ms·
Websites are the problem. You can't say "no thanks" to a required form field. (The obvious retort of "well don't shop there" is a no-go.) I've given "none-of-y
by inanutshellus 3y ago
Websites are the problem. You can't say "no thanks" to a required form field. (The obvious retort of "well don't shop there" is a no-go.)
I've given "none-of-your-business" data to companies that don't need it for a long time, (e.g. my middle name, shockingly, is your domain name, so weird!) but it CAN bite you if you forget your password and they ask for your birthday as proof of who you are.
I get asked my birthday so seldomly that I always forget what my new forever birthday is going to be by the next time I need it.
- Suppafly 3y agoDoesn't work for birthday, but for random none of your business fields, I often use data about the site itself. Give them their own address and use abuse@theirdomain.com for the email.
- vineyardmike 3y agoFor birthdays, I always just pick the nearest static holiday. So eg if you’re born July 9th, I’d just put July 4th for everything. Then when it’s time for recall, it’s as simple as “does this need a real birthday or a marketing birthday” and pick July 4th or 9th.
- rubinlinux 3y agoFor years I have been putting postmaster@<domain> for required email-to-download forms. Enjoy reading your own spam, jerks.