Release 86 has just gone live!
New Features / Improvements:
- Community owners can now make use of the Google Analytics feature for their community. (Previously, this feature was only accessible for personal journals.) Note that only the owner of a community can activate this feature; maintainers are not able to define or view the Google Analytics
( Read more... )
While editting this account earlier today, I was randomly redirected to another account that was not my own, straight into the profile editting field. I've also had reports from other people that they've had the same thing happen to them, only with inboxes and various other things. People keep private information in there, some of which shouldn't be made public to random site surfers.
Did you even test this before you released it?
Reply
"Privacy not working? Time to sling dirt with PROOF!"
Reply
Reply
Alternately, set up a Dreamwidth account (let me know if you need an account code) and import your entire journal there as a back-up. Please note: Whenever LJ fucks up, there's usually a large influx of new users and/or people updating their back-ups so it might take a while to import your entire journal.
(Unfortunately, neither of these options would import content posted outside your journals, such as comments left in other journals or posts made to communities. The only thing I can further recommend is to try to convince everyone you RP with to create DW accounts and import all of their stuff as well.)
Reply
I'd love an account code, thanks. Truly appreciate it.
Reply
Reply
Reply
As for importing, as others have said, they have a built in importer. They are having issues just like LJlogin and the like (see this post for more info) but they have have a work-around and are actively working on a fully functioning solution.
Reply
This? Is absolutely disgusting and a poor reflection on your company as a whole. If certain people learn about this, I could see them not even wanting to bother with you anymore.
Reply
Reply
Reply
Reply
Reply
Reply
Granted, for something this serious, I would have much rather the ops rolled back the last release. Especially since, when a similar but much less pervasive security breach happened a few years ago on LiveJournal, the ops were very quick to roll back the code release that triggered it, within fifteen minutes or so of their discovery of it. The radio silence now on this issue, which has gone on for well over a day is, quite frankly, very disturbing to me. ^^;;
Reply
Reply
Leave a comment