Cookies bisect into useful state for session management and all the other truly awful uses. Unfortunately it's impossible to avoid "the evil bit" problem and you cannot a priori know it's a useful or useless cookie.
QUIC session state has potential but I believe won't end the dependency. If you don't keep state in the browser side and you want either idempotent or portable state outcomes you have to have a three way rendezvous to restore prior state into a new binding.
Just saw the comment - I think it's easy to delineate between 3rd party and 1st party cookies, though I know that this would make is much harder to use a lot of SaaS products like Google Analytics etc.
Is it possible for us to create a tech ecosystem where those 3rd party cookies can be avoided in general?
Comments
Cookies bisect into useful state for session management and all the other truly awful uses. Unfortunately it's impossible to avoid "the evil bit" problem and you cannot a priori know it's a useful or useless cookie.
QUIC session state has potential but I believe won't end the dependency. If you don't keep state in the browser side and you want either idempotent or portable state outcomes you have to have a three way rendezvous to restore prior state into a new binding.
Tracking is shit but some cookies are purposeful
Just saw the comment - I think it's easy to delineate between 3rd party and 1st party cookies, though I know that this would make is much harder to use a lot of SaaS products like Google Analytics etc.
Is it possible for us to create a tech ecosystem where those 3rd party cookies can be avoided in general?