brynndragon: (Default)
benndragon ([personal profile] brynndragon) wrote2009-01-06 11:34 am
Entry tags:

Time to jump ship before it sinks?

via [livejournal.com profile] dragonvpm: LJ slash'n'burn. Nice of our Russian overlords to not mention any of this to us - oh, wait, they didn't leave anyone behind who *could*. . .

ETA: The math in that link is wrong - they cut ~2/3 of just the US tech folks, not 2/3 of the entire US staff, meaning ~12 of 28 jobs were lost not 20 of 28. It's still a pretty bad sign, particularly with nothing coming from LJ itself to confirm or deny any of this to us users. Here's cNet's article.

ETA2: LJ has made a press release that says pretty much nothing (certainly it does nothing to resolve the question of how many were cut). They couldn't even be arsed to send out that bit of palp to users?

[identity profile] dragonvpm.livejournal.com 2009-01-06 05:02 pm (UTC)(link)
I'm not going abandon ship quite yet, but I did go and grab my username over on Blogger (if I was going to bet on who might have a shot a some reliable longevity should LJ go under it would be them).

What I really want to do though is figure out how to archive my old LJ stuff somewhere online so it's not likely to disappear.

[identity profile] nyren.livejournal.com 2009-01-06 06:12 pm (UTC)(link)
People have told me that http://www.ljbook.com/ works well for that. I haven't tried it yet, but plan to very soon now. I just want to change my password to something inane before giving it to a third party website.

[identity profile] benndragon.livejournal.com 2009-01-06 07:07 pm (UTC)(link)
I just want to reiterate, in case anyone misses the subtle subtext of [livejournal.com profile] nyren's comment, that people who use LJbook (or any online archive) should be aware that they are giving full access to not only their own journal but any friends-locked posts of their friends to an unknown third party. Ny's work-around still requires a certain amount of trust (that they haven't set things up to gank other info with the archive dump, for example). You're much better off using an offline archiver, with this caveat.