- 4chan hell raisers finding fame brings heat?
- The 10 dumbest mistakes network managers make
- NetApp quits bidding war in face of EMC opposition
- CompuServe closes after 30 years
- Google to launch open-source Chrome OS this year
There is now no doubt that spam is on the top of your minds. The response to last week's column regarding the bad ideas being proposed to fix the spam problem was overwhelming - greater than I've ever had.
Reader Arthur Byrne pointed me to a well-written paper, "Information Asymmetry and Thwarting Spam", which discusses the mechanism that Bill Gates touted as "payment at risk." The basic idea is a message recipient could set a price to be paid by the sender if the recipient rejected a message as unwanted. The paper is worth reading and does make it sound reasonable.
But Byrne commented: "The technical formatting of the required infrastructure and [other details] are a non-trivial set of problems." He also was kind enough to go into these problems in some depth. As usual, the devil is in the details and the simple solution becomes really, really complicated, which makes the chances of it working next to zero.
Reader Benjamin Vogel wrote: "Let's not also forget the legal issues if we need to pay for e-mail. If I send an e-mail and I am charged for that service, I can reasonably expect a level of service. If my e-mail is bounced, delayed or somehow lost, I could hold the ISP responsible for that lost data. In a day and age where viruses are rampant and denial-of-service attacks are common, we would be hard-pressed to find any ISP that would guarantee any level of service for their e-mail transfer. Thus, many ISPs would not even offer e-mail as a service. But no e-mail means no spam, right?"
Reader David Neill wrote: "You're all wet, and so is Bill Gates (nice to be in the same league with that guy on something, isn't it?). Charging for e-mail is the only way spam is ever going to come under control, because you make it advantageous for anyone with any significant volume of received mail to collect from those who originated it, with charges maybe being forwarded through those who relay mail."
Neill adds: "The billing infrastructure can be written in Perl in less than a day. It probably can be a one-liner. Have a contest. How hard can it be?"
How optimistic can you be? Neill, if you ever had anything to do with billing systems you would understand what a nightmare they are. Tracking charges is not the only thing they have to do. There are all the supporting operations, such as reconciling accounts, authorizing payments, checking credit, chasing late payments, meeting auditing and tax requirements . . . in short, it is anything but simple.
Comment