I really like this idea. I could see a moderation queue, available to DW community administrators. I would see it listing the user that initiated the import, and the LJ username and LJ community that it is to be imported from, with the optional ability to see maybe the top 10 posts if you need more context.
This is the best balance I've heard so far between community importing and not being evil. --Azz On Thu, Apr 9, 2009 at 2:58 PM, Laura <[email protected]> wrote: > This is likely a technical headache but might address some of the use > issues.... > > Allow a user to import THEIR posts from an other-site community. > Regardless of other posts in the comm. Allow import to a personal > journal (may need to handle > Multiple import if it doesn't now - I might want all my u...@lj stuff > plus my communit...@lj stuff in my u...@dw account). > > Allow import to a DW community if the user maintains the community or > the maintainers have aithorized the user for imports (similar to > posting rights). Allow maintainers to permit free imports or > handshake. In handshake I try to import all my posts from community x > @ LJ (or whatever). DW confirms I can (that they're my posts) and then > stops. It tells the maintainers that user a...@dw wants to import user > b...@lj's posts from community x. They can then authorize or deny. If > they authorize, DW notifies me and gets anything needed to perform the > actual import at that point. > > Does that seem like it would solve at least some scenarios without > making big problems? I know it sounds technically complex to me but it > seems like it has at least some of the desired results. > > Sent from my iPhone > > _______________________________________________ > dw-discuss mailing list > [email protected] > http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss > _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
