There are multiple reports out that LiveJournal's latest code push has created a bug wherein users can, at random, view and edit other users' entries.
dw_maintenance has information as to its possible cause.
boundbooks has the actual quote from the first post about this, which was on…Journal Fen.
eruthros has links to actual bug reports. People have started reporting that they're no longer getting the bug as of my writing this, but unless LJ says something officially, there'll be no way to know whether it's actually stopped.
As
boundbooks says,
I'm probably going to discontinue crossposting of everything but translations to my LJ. In the meantime,
dw_codesharing has lots of Dreamwidth invite codes.
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
So, what's all the hub-bub about? Well, as you may have noticed as a Livejournal user, the hover menu on a user's ID has changed significantly and certain browser add-ons like LJ Login no longer work. What you might not know is that there is now a random, but rampant privacy breech on the site. Several users are able to see the f-locked and the private entries of other users/communities even if they are not friended by or they are banned from that particular user/community. Not only that, but several users have been taken to another user's entries when they try edit their own. The same mix-up in redirects goes for the redirect to edit profiles, edit journal information/settings, managing userpics, and even checking your message inbox. To put it simply: certain users have complete access to another user's account.There's been no comment from LJ either way;
Whether or not people will exploit this fact remains to be seen and the Livejournal staff has yet to comment on the issue.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
As
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I'm really not sure what more can be said in response to a massive privacy breech on LJ as a result of a change not reported to users, while Dreamwidth has reported what is likely that LJ code-change to DW users in a timely manner, in order to explain a minor bug on Dreamwidth.
I'm probably going to discontinue crossposting of everything but translations to my LJ. In the meantime,
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)