09-27-2012, 10:47 PM
Earlier today I changed the time on my computer to 2016. I was messing around with an application and wanted to see what it'd do if I went installed it in the future, then tried to use it in the 'past' by setting my time back.
Well, during that time I also logged into TLF, used Google, all that stuff. Needless to say when I changed my time back.. my login wouldn't work. NO matter what I did I couldn't get it to log in. Google rejected me and thought my computer was being hacked.
Finally I realized what might be causing these issues, I cleared my cache, restarted Chrome, then did a victory dance.
So, the moral of this story (speaking of m0ral, I miss that guy) is, don't play with your time if you don't want funny things to happen with your session cookies and certificates and junk.
Well, during that time I also logged into TLF, used Google, all that stuff. Needless to say when I changed my time back.. my login wouldn't work. NO matter what I did I couldn't get it to log in. Google rejected me and thought my computer was being hacked.
Finally I realized what might be causing these issues, I cleared my cache, restarted Chrome, then did a victory dance.
So, the moral of this story (speaking of m0ral, I miss that guy) is, don't play with your time if you don't want funny things to happen with your session cookies and certificates and junk.