The recent startup idea from Matt Cutts reminded me of one of my own. Imagine an email service that acts as a proxy between email senders and your inbox. The senders however have to pay an arbitrary amount of money to get an answer (I won't go into other details, I think you get the point). This seems logical as your time is precious and (in some cases) you should be rewarded for answering emails. This would also filter out spam. On the other hand, my perception of such a service is that it's evil. That's the main reason why I haven't pursued the idea. It certainly would not replace standard, free email, but I can see how people would hate this.<p>What do you think? Do you also see it as evil or would you appreciate this service?
This is an interesting service to consider from the perspective of both the sender and recipient of an email message.<p>The value that you create for the recipient is the spam filtering that you mention only as an aside. If someone is paying to send an email message, it's very unlikely that the message is spam. This form of micropayment makes email cost a little bit to senders, but it makes spam lose its cost-effectiveness. As a recipient, you can pretty much guarantee that email coming from this service is not spam. That makes going through your inbox a lot simpler.<p>On the other hand, value is created for the sender of email too. Because the recipient of the email is (mostly) assured that the message isn't spam, a response is much more likely. It sounds like you have a means (or idea) to guarantee a response too, which obviously amplifies this effect.<p>I think the service has potential. The first question that comes to my mind is who do you charge? You definitely charge the sender, but do you charge the recipient as well? Also, how do you make this work in a user's existing inbox? It seems like having users check another inbox will decrease the effectiveness of the service.<p>It's interesting that your solution is sort of an incremental solution to spam. To me, the best solution to spam would be to add authentication to SMTP or a new protocol with widespread adoption. However, your solution is more realistic.
Microsoft Research has an interesting project along these lines, called "Penny Black".<p><a href="http://en.wikipedia.org/wiki/Penny_Black_(research_project)" rel="nofollow">http://en.wikipedia.org/wiki/Penny_Black_(research_project)</a>
<a href="http://research.microsoft.com/en-us/projects/PennyBlack/" rel="nofollow">http://research.microsoft.com/en-us/projects/PennyBlack/</a><p>It doesn't sound particularly evil to me. What's the danger, in your mind?