On Thu, Apr 9, 2009 at 6:34 PM, Emily Ravenwood <[email protected]> wrote:
> I don't think piecemeal importing is the answer. I know that I, for > one, would look at such a requirement and throw up my hands and never > even try it. Ditto. > At the same time, I would be pretty infuriated if I found that an > entry I had posted to a comm had been reposted somewhere I could not > assert any control over it. Control of one's own content is a pretty > bedrock feature of LJ and all it's offspring. So I also don't think > that the current stop on comm imports is in any way unreasonable. That is a good point I had not considered until reading this thread, but still, it doesn't change the fact that not being able to import the comms I mod over = no migration. > And, given what I said first about the turn-off factor of any major > hassle being involved for the users, it seems to me the best way to > address the problem is indeed at the back end, by figuring out some > way for non-native (that is OpenID) users to assert control over > imported entries. (Lost track of who said this first, but +1.) That does sound ideal! Not that I can comment on the technological end of it, but yes, that would solve the whole problem it seems like, if it could be made to work. I also wonder if it would be possible to somehow notify each poster to a comm that the comm is being imported? A way for them to know and then go alter/delete if they so choose? Again I'm sure that stumbles over the OpenID issue, but still, would be nice. I'm not into taking control away from a poster, but again (and somehow I do not get the feeling that anyone but Lije is truly understanding the seriousness this issue poses to communities) without being able to port a comm over in toto, the community will NOT follow. At least not the ones I am active in. ::::KBS / Mikey
_______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
