LJ, Y U NO FIX CODE?
Oct. 27th, 2011 07:00 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Just as a heads up, LJ's new code push included some truly impressive bugs, the most notable being that people are finding themselves logged in to other people's accounts. With complete access to locked and private entries, comments, everything.
At this stage it has been a known issue for almost a day (I think -- timezones are hard!) and has yet to be fixed, or even addressed publicly by LJ.
I try not to over-react to LJ fails, but that's ... kind of epic. Even if it's a rare problem, it's still ... epic. Would it be silly to delete one's journal until the problem is fixed? I knew a few people who have done so, and I have to admit that I'm leaning that way.
no subject
Date: 2011-10-27 01:43 pm (UTC)As for deleting your journal, I would do this if I weren't afraid that the glitches might end up permanently deleting said journal. Even if it were a mistake on their behalf, I would still worry that they wouldn't be able to reverse it. I think the risk of hacking is better than the risk of losing it all. Or at least, until an import actually works for once =3
no subject
Date: 2011-10-27 01:56 pm (UTC)no subject
Date: 2011-10-27 03:50 pm (UTC)I suggest checking login sessions for IPs that aren't yours, for a start.
24 hours without mentioning that, oh yeah, the new release has a few issues, is definitely not cool. (Wonder if this has cropped up on the Russian side? I haven't seen comments in Russian at lj-releases but I can't imagine they're not wondering what's going on too. Have SUP been more on the ball about notifying their Russian userbase?)
no subject
Date: 2011-10-28 09:20 pm (UTC)