In the old days it was a big insult to call someone 'a horse thief'.
Imagine trying to implement a reliable security scheme to protect horses from theft.
Horses are easy to steal/hard to secure. They provide their own get away vehicle, and even identification/proof of ownership can be unreliable. (Branding is write once, read many)
The result was that punishment for horse theft was DEATH or worse.
The punishment isn't only based on the value of the thing stolen, but also on the consequences to society if the type of behavior continues...
It is because Spamming is so easy to do and easy to get away with/hard to prosecute that the punishment should be harsher than other crimes.
Slashdot Mirror
Great idea!
Maybe instead of the pointer being in the signature it should be in the header.
The pointer would point to an XML document on the net. The XML doc would spell out the restrictions and caviats.
I am thinking along the lines of how P3P will handle privacy in the next generation of browsers.
http://www.w3.org/P3P/
In the old days it was a big insult to call someone 'a horse thief'.
Imagine trying to implement a reliable security scheme to protect horses from theft.
Horses are easy to steal/hard to secure. They provide their own get away vehicle, and even identification/proof of ownership can be unreliable. (Branding is write once, read many)
The result was that punishment for horse theft was DEATH or worse.
The punishment isn't only based on the value of the thing stolen, but also on the consequences to society if the type of behavior continues...
It is because Spamming is so easy to do and easy to get away with/hard to prosecute that the punishment should be harsher than other crimes.