Add your comments
DLS Archives
May 2012
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | 31 | ||
Essential Windows Apps | Do Not Track | Microsoft Office | SayNow | LibreOffice | Zeam Android Launcher | Dead Space iPhone | Firefox 4 Mobile | Firefox 4 Release | PlayStation iPhone App | Excel Tips | Android Launcher | Google One Pass | Dead Space | Google Cloud Print | Songbird for Android | NBA Jam | Internet Explorer 9 | Windows 7 Connector for Mac | Office Mac 2011 | IE9 RC
Gadget News
- Amazon offers prepaid 4G LTE data in Japan, gets you online 500MB at a time
- Lenovo ThinkPad Edge S430 readies to enter Euro market, gets priced at €809 on German site
- Precise Biometrics' Tactivo for iPhone, iPad locks data by fingerprint and smart card, is overkill for your diary (video)
- Volvo's driverless road train in Spain is public mainly on the plain (video)






Reader Comments (Page 1 of 1)
(Unverified)Apr 17th 2008 4:00PM
This would be much simpler to implement as an RFC, which could later be mandated by law. That is, the RFC that defines how cookies work could be expanded to carry metadata about the cookies that identifies tracking cookies in a unique way, then consumer web browsers could decide whether or not to keep/honor those cookies. Sort of like the idea behind .xxx domains, only less controversial -- require that American companies simply follow a certain convention, and let the technology handle the rest.
They would build on the existing "cookie RFCs":
http://www.ietf.org/rfc/rfc2109.txt
http://www.ietf.org/rfc/rfc2964.txt
http://www.ietf.org/rfc/rfc2965.txt