So who made a product like the iPad before the iPad?

lost humor aside...

You make a good point. So my comments are to the OP.

If I use Client side Javascipt to generate the MD5 hash then the "secret" key has to be sent to the client. Otherwise how would it know the secret key to use to create the hash.

I would struggle with a law like that. Next thing you know they will require you to have zippers on all of your pockets and if you get pickpocketed its your fault for not having your zippers zipped.

I lived in Denver Colorado during the late nineties. I had a Jeep Cherokee which is probably the easiest car to steal so it was a big target for people that just wanted to joyride.

It was stolen/attempted 4 times in the eight years I lived there. Each time it was recovered usually within a day. The last time it was stolen I called my insurance company to file a claim. The guy asked me if I had locked the door. I told him no. After a bit of silence he asked me why. I told him I didn't lock the door because I didn't want to drive around with a broken glass while I waited to get it fixed. He looked at my history and said I see it looks like we have replaced the glass in this vehicle 3 times and we wont have to this time.

Since then I never lock my car. People that do not know the story usually say things like "naive" but actually the opposite is true.

You see performing is work and they are bemoaning the work. So they slam their fans for not buying more of the stuff that requires no work.

There are ways to make various aspects of various operating systems easier to see by enlarging them, but none are done at a level where they affect everything in the operating system. I may be able to make certain things bigger but those are localized and not global to all the things on the screen.

The reason people "prefer" a lower DPI is because that is the only way on most operating systems to get the stuff onscreen to be bigger. Wouldn't it be nice if Operating systems didn't use pixels as a metric for point size but instead user a ruler as a metric for point size.

iOS4 is the only operating system I know of that get this simple concept right.

Thank you for restating my point. They get you back the way you were when you purchased it then they determine if there is anything that needs to be replaced under warranty (No, didn't mean HD meant CD, as in CD-ROM drive)

While certainly Apple may be able to detect things like that it would be more trouble then loading up the original stuff and telling you here it works.

The "voids your warranty" bit seems like a scare tactic to me. Lets suppose I do something to my phone (jailbreak) and it gets bricked. Wont turn on nothing works. Ok so I take it to Apple and ask for a replacement for my broken iPhone. They will have to be able to show me that it is still working (the hardware), and so they do some magic sequence of pushing buttons iTunes USB wizardry and boom its working again. Then they tell me its working so we don't need to replace it.

Its the same thing computer manufacurers have been doing for the last 10-15 years. If you call telling them your CD is broken the first thing they do is have you restore so its just like they sent it to you from the factory. Once you do that if the CD works they hang up. If it doesn't then they go down the warranty path.

Why the attack on DJB? Why is parent modded infomative? Sounds like parent has issues with DJB that calls into question the rest of what he writes.

Cookies have limitations. Evercookie helps me overcome some of those limitations. That could be a good thing and that could be a bad thing depending on who is using it and for what purpose. It also depends on whether you are iformed of this use.

But what evercookie is doing is NOT blackhat and is perfectly acceptable. There is nothing hidden about what Evercookie is doing. Now someone could use the technology that evercookie is offering in an unacceptable way that is no more the fault of evercookie than copyright infringment is the fault of the internet.

Or perhaps people like devices that pack a lot of functionality into a small footprint.

I'm old but I loved the walkman because it was small. I loved the iPod because it was small, I love my iPhone because it is small, and I love the small size of the iPad.

Well, actually there are other ways to do it like putting that infomation in the URL, or hidden form elements, or http://samy.pl/evercookie/...

Here is what evercookie tells me when I go there...

Cookie found: id = 34452062

cookieData mechanism: 34452062
localData mechanism: 34452062
globalData mechanism: undefined
sessionData mechanism: 34452062
historyData mechanism: undefined
dbData mechanism: 34452062
pngData mechanism: 23235035
lsoData mechanism: 34452062

Interesting to note that on my system the pngData doesn't match the rest. Perhaps thats because I am using OS X with Safari and ColorSync.

For that you would want the server to enforce IP security, and alternatively... put a cookie there, but looks like were full circle again.

I have a web based application that uses cookies to validate a single machine, or a group of machines.

An administrator goes to each machine and logs in as the administrator and clicks "AUTHORIZE" this authorizes this machine for use. If a user attempts to use the application on any other machine/browser they will not be allowed access.

When a user uses the machine the cookie is rewritten with session information and that last used session validates the next use. The means the "valid" cookie changes with each new session. This makes copying the cookie difficult.

The application is a Time Clock and is designed with the premise that trust must be ensured to both the employee and also to the employer. So by design employees and also employers are not able to change any punch data, but employers are able to add notations that include adjustments.

I can see that evercookie would be a great way to allow my users to create more resilient cookies. I wonder if using cookies that are not the same but keypairs would help in my situationto to validate the machine more accurately. That way simply copying the cookie without copying the RGB data would not be sufficient to spoof a machine/browser. Hmmm. Interesting.