| Why not leave the existing LJ comm as an "archive"?

Because over the past few years there have been multiple actions taken by the 
current management of LiveJournal that has led to a fundamental level of 
distrust from the user base. Many users, particularly those in the 
fandom-oriented communities, would prefer not to leave their material to the 
tender mercies of LJ. Also, see Mikey's earlier missive about how this would 
serve to tear some existing comms apart bit by bit.

To be fair to LiveJournal, it is a private business, and as such it has the 
right (and many would argue, no small legal responsibility) to draw a line in 
the sand when it comes to what type of content it will allow to be 
stored/published using its service. Regardless of one's opinion as to where 
that line ought to be drawn, the way in which the various policy changes 
related to this ever-shifting line have been implemented has been abrupt, 
arbitrary, and opaque. Dreamwidth will no doubt face some of the same 
questions, but it is believed that they will do a much better and more 
transparent job of governance.

A lot of folks are looking to Dreamwidth as the safe place to escape to from 
LJ, preferably in a smooth transition now rather than in a panic after the next 
policy shift that leaves a number of LJ users being treated like criminals 
whether they've done anything wrong or not.

| No import necessary. No messy dealing with who owns the rights to what 
content. If new members join and want to look at old LJ posts, they can sign up 
| for "archive access" via OpenID.

That's easier said than done for a lot of communities. If you're talking about, 
say, a community devoted to posting daily pictures of baby llamas, that's one 
thing. If you're talking about a community that maintains an archive of recipes 
and wants to use Dreamwidth's improved searching and tagging functions to 
better manage its existing content, then a split community doesn't serve that 
need.


Thanks,

Alexis Carpenter
principia at Dreamwidth
principia_coh at LiveJournal

_______________________________________________
dw-discuss mailing list
[email protected]
http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss

Reply via email to