Short version. Livejournal has today fired about half of its US based staff, including several people that I'd say are key, if not crucial to the operation. This means that while SUP/LJ Inc have the right ideas about where to take the site, they're running out of money (and paid over the odds anyway) and can't afford to do it.
I suspect that LJ itself will continue, as it has ongoing revenue, but the improvements that it needs to turn itself into the successful site it could've been will now be significantly slowed, which puts the long term health of the site in danger. Not got time to do a full post, but here are some links: ( ... )
I promised a 'how to' on backing up your journal and exporting it to other platforms, in order to write that I first need to do it myself fully and properly, so that'll happen later on (hopefully tonight, depends if I can get it all to work). In the meantime, some of the comments/posts linked abouve are from rahaeli
, who used
to be an LJ staffer but left to concentrate on her writing career (I got the impression she was asked to defend the indefensible once too often)—she's a good fiction writer FWIW. Last year, she announced that with a small number of others she'd be working on a fork
of the Open Source Livejournal code (to be called Dreamwidth) to update it, make it compatible with modern servers and run a platform that'd be more community friendly in the way LJ "used to be". Many of the proposals she put forward were ones that echoed what I was looking for—crucially a separation between your 'reading' list and the people you trust to read your friends locked posts, as well as complete interoperability with other sites on the same codebase.
That latter is interesting—if she/they (we?) can get it going, then different people could run Dreamwidth installations and you could still add people, let them read your secure entries, etc from your friends page, without much if any extra effort on your part. That could mean that anyone
could pay for a server and run their own site. Drawback is that you'd need your own webserver, renting one of them is a minimum of £50 per month, much more for something decent.
But if enough people were to chip in, it'd be more than possible. In fact, it'd be more than viable, it'd possibly be a very good plan. There are a bunch of you reading this that know a lot more about the backend side of this sort of thing than me—we'd need to work to set it up, and then install updates, etc. Almost certainly viable with enough people, so, well...