It is obvious to anyone with a clue that abusing GET/POST that was was not intended, which is ironic, since you were in your other post going on about what HTTP/HTML was somehow intended to be. Every "bad" kind of tracking is just as easily possible on the server side, if not more so. Cookies are enforced per-domain. Access-based tracking is effectively cross-domain. Embed an image linked from Facebook in your website? There is a VERY good chance Facebook is recording the views, IPs, and domains from which they come, and comparing that against login data. All serverside: Facebook knows which porns sites you go to, with no cookie involved.
If you had sense, you would be worried about THAT, not bitching about cookies and spewing nonsense about what you think would be somehow better, despite numerous actual programmers pointing out the problems your ideas would cause.