3 ms·
same here....I'm assuming that it is still working correctly but may be wrong.
by lgleason 14y ago
same here....I'm assuming that it is still working correctly but may be wrong.
- kristjan 14y agoOpening google.com/+ shows the cookie is still intact. There's also a ping every 30 seconds to https://developers.google.com/events/register/waitlist/status/googleio2013_general/ https://developers.google.com/events/register/waitlist/statu... that returns {"status":"waiting"}. Trying that URL from a remote console returns {"status":"reregister"}, so the Sign In header appears spurious.