There are a lot of smart people working on code for DW. I assume (and Mark pretty much said) that if they find a non-slimy way to do it, they can write code to whatever way they decide, once they're past the initial push of getting DW up and running and have a bit of time to work on non-immediate needs. The problem is coming up with a non-slimy way to handle it, which is what the whole brainstorming process is for. I think this is a non-slimy way of handling things, so I'm throwing it out as part of the brainstorming.
Beatrice Otter > I think what Denise has been saying is that all of this is theoretically > possible, except at the moment there's no way to associate a post with an > OpenID, nor is there a way to screen a post, so both of these would have > to > be invented first. > > On Thu, Apr 9, 2009 at 6:24 PM, <[email protected]> wrote: > >> How about this: Mod imports community. Posts are set up as coming from >> OpenID names (can't post new posts, but still have control of old ones). >> BUT all posts are screened as a default. Messages automatically get >> sent >> to the people who originally posted those posts, saying "X community got >> imported to DW" with a list of posts they've made in that community, >> with >> the option to either unscreen or delete each post on DW, the option to >> set >> up a DW account so they could post to the community now it's moved, and >> the option to associate the OpenID account with an existing DW account. >> It would probably take a large, complicated code thingy to do, but it >> would deal with all of the objections raised so far if I understand them >> correctly. People still would have ultimate control over their own >> content, but it would still be moved as a whole. Obviously, it wouldn't >> answer for all situations (forex, if it's a specifically reference >> community and the idea of losing a lot of posts from people who don't >> want >> to switch or have become inactive and disappeared), but it should work >> for >> most communities without being too hinky in the way that it deals with >> peoples' content. >> >> (I was originally going to suggest just a notification that the posts to >> x >> community have been moved with a link to deleting them, but moving >> without >> asking first is hinky enough even if you screen it in the new place so >> no >> one can read it but the original poster.) >> >> Beatrice Otter >> _______________________________________________ >> 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
