Re: Firefox 22 and third-party cookies

Thrawn wrote:And if only 1% of browsers support them, then no site can rely on them and they are basically dead.
[...]
workaround: once a site sets a first-party cookie, it is allowed to set third-party cookies. [...]strengthens the argument that this won't work. [...]sites that want to collaborate will just have to use more redirects, that's all.

Not having a clue about how it works - security and set and get and that type of thing, - and not directly related to your own service coding, but DOM storage looks to be the way servers are going to get a step ahead of the game without being allowed to set little cookies; I subscribe to a US mail forwarding service and for a year now the site breaks without

dom.storage.enabled

toggled "on". Perhaps that's a flag of what coders are resorting to in the home of the WWW empire now that cookies is a scare word?
Many more Safari browsers with crippled cookies would've been lobbing on to mail services (because people with a lot of money but not much nous want mail services to kiss feet on top of send and get reliably), and you usually find that mail services code is a good indicator of where the web is moving to accommodate the noisy but dumb anxious of this world.
Good luck with your own workarounds

EDIT: close quotes