In order for this idea to be a success, then user authenticity must be addressed first enabling me to choose not to receive email from accounts without a verified real-world identity.
Well, if they pay (i.e., present a certificate that the micropayment has come through certified by some respectable authority), then what the heck, take it, even if they don't have the verified identity. I really don't see what the problem is with not having user-authenticity (on the email level, not micropayment level).
All we all need is Microsoft to introduce a new email variant where the sending party is charged for each email sent, hence diminishing the wish of users to impose unnecessary noise.
What's funny about this one? Take the Microsoft crap out of it, have new email standard designed by some standards organization or a group of professionals (i.e., put into it good analysis). Spin some cryptography around (or better to say under it), and you can have half of the problems solved. Actually, in his Designing Web Usability Nielsen suggests charging people for incoming emails by selling special certificates that one would attach to an email, and giving some unlimited-use free certificates to friends and members of the family. It won't solve all problems but would simplify many things: first of all, it would allow for much better and easier sorting; second, if servers know how to handle these certificates - the price for spam will go to the sending server rather than the receiving one.
I was just wondering. I installed jEdit recently (after not using it for a while) under Linux-Mandrake, and if I choose anti-aliasing in there (within the program itself), it's gorgeous - comparable if not better than I've seen in Windows, really eye-pleasing. The question is how do they do it, and is there a way to take it from there and put into X or KDE or whereever appropriate?
Slashdot Mirror
In order for this idea to be a success, then user authenticity must be addressed first enabling me to choose not to receive email from accounts without a verified real-world identity.
Well, if they pay (i.e., present a certificate that the micropayment has come through certified by some respectable authority), then what the heck, take it, even if they don't have the verified identity. I really don't see what the problem is with not having user-authenticity (on the email level, not micropayment level).
All we all need is Microsoft to introduce a new email variant where the sending party is charged for each email sent, hence diminishing the wish of users to impose unnecessary noise.
What's funny about this one? Take the Microsoft crap out of it, have new email standard designed by some standards organization or a group of professionals (i.e., put into it good analysis). Spin some cryptography around (or better to say under it), and you can have half of the problems solved. Actually, in his Designing Web Usability Nielsen suggests charging people for incoming emails by selling special certificates that one would attach to an email, and giving some unlimited-use free certificates to friends and members of the family. It won't solve all problems but would simplify many things: first of all, it would allow for much better and easier sorting; second, if servers know how to handle these certificates - the price for spam will go to the sending server rather than the receiving one.
I was just wondering. I installed jEdit recently (after not using it for a while) under Linux-Mandrake, and if I choose anti-aliasing in there (within the program itself), it's gorgeous - comparable if not better than I've seen in Windows, really eye-pleasing. The question is how do they do it, and is there a way to take it from there and put into X or KDE or whereever appropriate?