News for hackers. Stuff that matters.
Re:Rethinking Cookies: originOnly by mwexler on Thursday February 07, 2013 @02:46PM (#5184110)
That "every other use is generally not good for the consumer" is a broad generalization, I think.
Re:Rethinking Cookies: originOnly by ChuckMcM on Thursday February 07, 2013 @03:32PM (#5184332)
I don't disagree. One way to look at the question is "if we ban all other uses we cripple case X, Y, and Z" vs "if we allow other uses we allow X, Y, and Z but enable P, Q, and R type problems."

Lots of things in the world have similar tradeoffs, to use a silly example "Leave your front door unlocked" makes it easy for anyone to come in, but also makes it easy for crooks to come in, so a common solution is to lock it and give certain folks the key.

Cookies came about as a way for a web service to retain state across sessions, and then that concept got applied to lots and lots and lots of things, some good some bad. Perhaps there are two things here we should have "originHostState" and "GenericUserState". We could then see how many people allowed the latter type of cookie to be set.