Some web applications force me to use an email address that I can actually get at the emails to, by sending my first password to that address. I use throwaway accounts for this, or my "don't give a clang" account: tonywalters@totalise.co.uk. I clear out the reams of spam this one takes once every couple of months. My browngirl one (this one) is my proper one, but I've still managed to end up getting SOME spam to uit, about one spammail a day on average.
I use privacy.net addresses for logging onto or entering my password onto apps that I don't need to use a valid address on.
Before I knew about privacy.net, I was guilty of using fake ones I'd made up. Like Jake says, it's a bit unfair on whoever owns the domain you use. I used to use dave@dave.com, or dave@dave.dave for web applications without validation of TLDs. For those that wouldn't accpet a .dave TLD I did use dave.com. I apologise for this.
Another one was arse@arse.com. I apologise for this too. Although I suspect it's just a porn site anyway, I can't remember checking and can't access porn from work (ahem, not that I want to).
When I get spam from addresses that are actually real addresses, I have sometimes stung them back by using their real address to register with apps I don't trust. What goes around comes around.
Jake once blogged or wrote an article suggesting the possiblilt of using an address @ thedomainname.com, where thedomainname.com is the domain name of the application you're registering with. This means that they get their own spam stright back, which also amused me as a concept.
Some web applications force me to use an email address that I can actually get at the emails to, by sending my first password to that address. I use throwaway accounts for this, or my "don't give a clang" account: tonywalters@totalise.co.uk. I clear out the reams of spam this one takes once every couple of months. My browngirl one (this one) is my proper one, but I've still managed to end up getting SOME spam to uit, about one spammail a day on average.
I use privacy.net addresses for logging onto or entering my password onto apps that I don't need to use a valid address on.
Before I knew about privacy.net, I was guilty of using fake ones I'd made up. Like Jake says, it's a bit unfair on whoever owns the domain you use. I used to use dave@dave.com, or dave@dave.dave for web applications without validation of TLDs. For those that wouldn't accpet a .dave TLD I did use dave.com. I apologise for this.
Another one was arse@arse.com. I apologise for this too. Although I suspect it's just a porn site anyway, I can't remember checking and can't access porn from work (ahem, not that I want to).
When I get spam from addresses that are actually real addresses, I have sometimes stung them back by using their real address to register with apps I don't trust. What goes around comes around.
Jake once blogged or wrote an article suggesting the possiblilt of using an address @ thedomainname.com, where thedomainname.com is the domain name of the application you're registering with. This means that they get their own spam stright back, which also amused me as a concept.