There is a constant tension between the web-site owners who want to harvest your email address for marketing and the web-users who want to access content without the bother.
Arguably, there is a (social) contract where you are purchasing the information on the web-site in return for providing permission to receive marketing emails.
However, as someone who fast-forwards through the adverts when watching recorded television, you can guess where I stand on this.
BugMeNot provides one element of the arms race between the reader and the writer. It encourages people to share registration details.
That’s fine for a read-only service, but what if you want, for example, the wiki site to record your edits under your handle but not email you newsletters?
I propose a new service, EmailMeNot (just a placeholder name).
Register at a new site with your name and password, but instead of your email address use someUniqueGibberishString @ emailmenot.com
.
There an automated rule will look for a registration link, and open it automatically. All other email to that address will be discarded.
Security risks include that you are beholden to the emailmenot.com owners not to take over your account whenever they want.
Defeating this system will be trivial to web-masters to do – simply request the password to be re-entered when the link is followed – but it will get you past a lot of registered web-sites now.
Given two major downsides, I can’t see myself ever implementing this, but if someone else wants to…
Comment by Aristotle Pagaltzis on May 11, 2009
I haven’t seen the specific service you talk about, but Mailinator seems to be close enough.
Comment by Julian on May 11, 2009
Mailinator is nice; I’ve seen that before, but EmailMeNot has less steps, due to automated clicking on confirmation links.
Comment by Andrew on May 11, 2009
Yes. As someone who fast-forwards through the adverts when watching recorded television, I can guess where you stand on this.
Comment by Aristotle Pagaltzis on May 12, 2009
I wouldn’t want to run a service that automatically requests URLs in mails it receives… I’m getting a headache just trying to imagine all the ways in which it could be abused, eg. as a DoS vector. (Sure, you can solve each one of them… the question is whether you can think of every possible scenario.)