ARGH ARGH ARGH!

[branchandroot]

OMG, LJ YOU UTTER FUCKERS!

Not ONLY do they fuck up the latest release so it allows random people access to random other people's journals and HAVEN'T ROLLED THE RELEASE BACK, but NOW LJ-SEC CAN'T LOG IN. Because those remote log-in pathways that just changed?

AFFECT THE ONLY APPLICATION THAT CAN DO BULK DELETION OF LJ ENTRIES.

RAGE.

*breathing heavily* I can only hope that the lj-sec developer is a kind soul and releases an update soon. Because this is absolutely it, I'm not leaving my content on that service for another second than I have to. Nothing but public links to other sites!

ETA: It has been suggested by a party who wishes to remain unnamed, but who has some cause to know, that the reason a release like this will not be rolled back despite security failure is most usually that this release fixes some /other/ security bug that was being actively exploited. Additional recommendation: try logging out of LJ and not logging back in until it's fixed. This would kill one possible cause of the mad account access swapping. If it's another cause, apparently we're fucked until LJ's worker bees can scramble a fix. *sighs*

Comments

[ldybastet]

...

-_-

I take two days off the Interwebs to paint the walls at my new workplace... and LJ breaks them? My poor Interwebs! Godammit. Grrr. God what a horrible bunch of fuckups. *sigh*

[seagull2eagle]

And I love the fact that we hear the information from *Dreamwidth* and not LJ. That just sucks. LJ, what a piece of... ~..~

[annotated_em]

Wait, there was an application that let you do bulk deletes? Damn.

I'm slowly working my way through the archive of my journal, but it's so dispiriting.

(Ye gods, I was a twerp.)

[mitsuhachi]

Yeeeeaaaahhhh....I've gotta admit, there's a lot of shiny people over on LJ. But damn am I glad I cut and run way back when. O.O That sounds like a MONUMENTAL fuckup. I kind of wish there were somewhere over there to offer DW/AO3 invite codes.

[synecdochic]

Additional recommendation: try logging out of LJ (ideally restarting your browser) and logging back in. This would fix one possible cause of the mad account access swapping. If it's another cause, apparently we're fucked until LJ's worker bees can scramble a fix.

actually, in *most* cases the problem could be (and please note that I have no idea what the problem is or whether it's something other than the Varnish misconfigs they mention in http://lj-maintenance.livejournal.com/131843.html and claim to have fixed), logging out of LJ entirely, expiring all sessions, and staying logged out until the problem is no longer being reported, would most likely do it. If it's cache/Varnish problems the way they say, that would prevent you from loading a page logged in and thus having your logged-in account cached for someone else to see; if it's something more serious like a fucked up master cookie->login session table or something, it would prevent your master cookie or login session from existing (and thus from being confused with someone else's).

[foxinthestars]

Not being knowledgeable about programming at all, my initial reaction was "that can even happen!?" After reading the comments here I put up a quick post offering my DW invites to my LJ friends, logged out and restarted my browser...