It's because LJ has fubared something in the latest release they rolled out yesterday. There was a post about it on one of the official Dreamwidth comms - I'll see if I can find it.
It's not just DW it's fubared - it's broken all sorts of third party login clients, and there's a lot of ranting on the lj-release comm over on LJ. Not to mention the whole massive security breach it resulted in, which LJ have now dismissed as being 'minor'. After the rollout, a lot of people, when they went to check their inbox or edit entries, were shown the cache (LJ says 'cache' and therefore wouldn't have been able to edit anything) of the last person to use the page. Which meant, of course, they could see messages in the inbox and locked entries they weren't supposed to have access to.
LJ said this only lasted 3 minutes, but the reports that rolled in from users suggest it was/is more widespread.
(no subject)
Date: 2011-10-27 09:17 pm (UTC)It's not just DW it's fubared - it's broken all sorts of third party login clients, and there's a lot of ranting on the lj-release comm over on LJ. Not to mention the whole massive security breach it resulted in, which LJ have now dismissed as being 'minor'. After the rollout, a lot of people, when they went to check their inbox or edit entries, were shown the cache (LJ says 'cache' and therefore wouldn't have been able to edit anything) of the last person to use the page. Which meant, of course, they could see messages in the inbox and locked entries they weren't supposed to have access to.
LJ said this only lasted 3 minutes, but the reports that rolled in from users suggest it was/is more widespread.