I got into a discussion with a guy at one point. I was on the side of "burn out", recommending work-life balance and keeping to a 40 hour week as being important for both the employee and employer. He claimed for the right team, such as he had, it wasn't an issue (he was in finance in New York). Rather than take the discussion more heated, I just left it at that. 1-2 years later, he had quit his job and was riding a motorcycle down to Mexico.
Unfortunately, life isn't perfect, or fair. Boo hoo.
If you really don't want to move, homeschooling is an option in many places. And contrary to popular propoganda, it's not all being done by radical Christian fundies.
Although I have ridiculed the use of POST and GET to replace cookies above, the truth is that once you have the user logged in with a cookie, it is then trivial to use POST or GET for the actual tracking. Unless the legislation is crafted carefully (haha), it's trivial to get around.
The stateless web was a design flaw based on assumptions about the content and the way things would be organized (the web is far different from what TBL envisioned). It was fixed (though maybe not in the best possible way). People need to get over it.
You're right about the header too. All this post gobblediegook basically translates to "server sends some stuff with a unique identifier, client sends back some stuff with same unique identifier, repeat until done". That's exactly what a cookie is but you don't have to tie your code in knots to accomplish it and management tools can be built into the browser because you're not dealing with some ad-hoc buggy code some backroom developer knocked together. As a bonus, if legislation were ever written properly, it could be targeted correctly. Can you imaging what would happen if they started trying to legislate POSTs and GETs?
The IP address is actually a bigger issue too. I can use private browsing or clear my cookies if I'm paranoid enough with little effort. Masking IP address is a whole other issue. It doesn't expire at the end of the session, typically bears some kind of relation to geographic location, in some cases can be used to see if a person is home/online or not, can remain the same for years at a time and is identical across all websites and services accessed.
Just because you *can* wedge the word "track" in there doesn't mean it's correct usage. They are there to *maintain* state.
To those who are suggesting use of GET and POST instead, that these were less-than-optimal is the whole reason cookies were invented in the first place. I worked with those methods and they were a PITA. And storing that kind of state in a GET is just plain-arsed retarded about any way you slice it.
With that said, that's somewhat orthogonal to the issue of tracking (and third party cookies). I have no idea if this legislation addresses things properly and adequately (given the couple of websites where I have seen this crop up, I assume it's up to the usual competency of such legislation and only inconveniences the good guys while allowing the a-holes to continue unabated)
Slashdot Mirror
Have you considered getting your private pilot's license?
Yes. Anything fares better when it can be funded with apparently unlimited funds coerced from the taxpayer.
I do like the irony that you took the content of an article that says copying is good for innovation, and just copied it.
Yep, you can condemn clock watching when I'm told that when I'm no longer being productive for the day (or maybe week), I can head to the door.
I never plan to retire. I just want to get to where I can work where and when I want to.
I got into a discussion with a guy at one point. I was on the side of "burn out", recommending work-life balance and keeping to a 40 hour week as being important for both the employee and employer. He claimed for the right team, such as he had, it wasn't an issue (he was in finance in New York). Rather than take the discussion more heated, I just left it at that. 1-2 years later, he had quit his job and was riding a motorcycle down to Mexico.
No "What could possibly go wrong" tag?
I'm sure you didn't mean any 'arm by it.
Yeah, you didn't build that!
My god, somebody stop that idiot before he gets the ice-nine out.
Unfortunately, life isn't perfect, or fair. Boo hoo.
If you really don't want to move, homeschooling is an option in many places. And contrary to popular propoganda, it's not all being done by radical Christian fundies.
I agree. Beat it!
But it was undead on arrival.
AC? Really? I guess if I emitted an insult that lame I wouldn't want my name associated with it either.
Although I have ridiculed the use of POST and GET to replace cookies above, the truth is that once you have the user logged in with a cookie, it is then trivial to use POST or GET for the actual tracking. Unless the legislation is crafted carefully (haha), it's trivial to get around.
I stopped receiving spam completely. It's really simple, I'm surprised more people don't do it.
Just bring up one of those command line thingies and type
# apt-get install mysql
My Athlete's foot went away also.
+1
The stateless web was a design flaw based on assumptions about the content and the way things would be organized (the web is far different from what TBL envisioned). It was fixed (though maybe not in the best possible way). People need to get over it.
You're right about the header too. All this post gobblediegook basically translates to "server sends some stuff with a unique identifier, client sends back some stuff with same unique identifier, repeat until done". That's exactly what a cookie is but you don't have to tie your code in knots to accomplish it and management tools can be built into the browser because you're not dealing with some ad-hoc buggy code some backroom developer knocked together. As a bonus, if legislation were ever written properly, it could be targeted correctly. Can you imaging what would happen if they started trying to legislate POSTs and GETs?
So your solution to the "Cookie" fiasco is to require all users to enable Javascripts? Your subtle sense of humor is sublime.
The IP address is actually a bigger issue too. I can use private browsing or clear my cookies if I'm paranoid enough with little effort. Masking IP address is a whole other issue. It doesn't expire at the end of the session, typically bears some kind of relation to geographic location, in some cases can be used to see if a person is home/online or not, can remain the same for years at a time and is identical across all websites and services accessed.
You can roll cookie IDs with every page transition too.
WTF is so special about MySQL?
Hey, I'm a Windows user*. Can I use Access or Excel instead of MySQL?
*Just kidding.
Just because you *can* wedge the word "track" in there doesn't mean it's correct usage. They are there to *maintain* state.
To those who are suggesting use of GET and POST instead, that these were less-than-optimal is the whole reason cookies were invented in the first place. I worked with those methods and they were a PITA. And storing that kind of state in a GET is just plain-arsed retarded about any way you slice it.
With that said, that's somewhat orthogonal to the issue of tracking (and third party cookies). I have no idea if this legislation addresses things properly and adequately (given the couple of websites where I have seen this crop up, I assume it's up to the usual competency of such legislation and only inconveniences the good guys while allowing the a-holes to continue unabated)
Just a tip. If you're a little tired, don't twist your gas cap until it clicks if it's not actually a clicking gas cap. Don't ask me how I know.
You might just be clever yourself, y'know.