3 ms·
> For email uses, a textual encoding of a hashcash stamp is added to the header of an email to prove the sender has expended a modest amount of CPU time calcula
by 0xdeadb00f 5y ago
> For email uses, a textual encoding of a hashcash stamp is added to the header of an email to prove the sender has expended a modest amount of CPU time calculating the stamp prior to sending the email. In other words, as the sender has taken a certain amount of time to generate the stamp and send the email, it is unlikely that they are a spammer.
I can see exactly why this wouldn't work - nowadays wouldn't spammers have enough processing power to just do this for every spam email? And how does this not slow down email processing for the end-user, sending an email now requires me to brute-force a hash, right?
- lozenge 5y agoThe idea was it would be adjusted to take a reasonable amount of time for legitimate users, say a second per email. The problem was it didn't predict the use of viruses to misuse computing resources of end users. Actually, nowadays this could even be done in JavaScript and pushed through an ad network.