> but it got watered down which was a real shame. I'm not sure why. I think (and this might just be an old wive's tale) it was related to the browser connectio

> but it got watered down which was a real shame. I'm not sure why. I think (and this might just be an old wive's tale) it was related to the browser connection limits being per domain, and so subdomains + looser cookie origins was a band aid for it.