As I have understood Dreamwidth's goals, the intent is that sites using the dreamwidth codebase will be interoperable to a greater degree than is currently possible with sites using the livejournal codebase. Some of the concepts discussed have been things like ... if you subscribe to a dreamwidth clone account, having the comments at dreamwidth automatically be reposted to the clone (or, perhaps, having no comments at Dreamwidth at all, and having the comment links go to the clone site), supporting authenticated RSS feeds so that a dreamwidth user is alerted to a locked post on a different site, attaching imported comments to OpenIDs of the person who made the comment, and allowing the openid holder to erase/edit comments as a normal dreamwidth user would have permission to do.
As these goals are achieved, the difference between service providers should be less important, reducing the livejournal codebase 'fenced garden' effect. --zvi On Mon, Feb 2, 2009 at 12:28 PM, Jae Gecko <[email protected]> wrote: > Lije Carpenter wrote: > > I know and see plenty of people who are multilingual or even > > non-English unilingual who use the parent LiveJournal site. There's > > not much English necessary for using the base functions of any > > journaling site. I can see where a lack of ability to read the FAQs > > (et al) would be problematic, though. Perhaps a workable solution > > would be for multilingual volunteers to offer their help in having a > > support wiki that translates the FAQs (et al) for users who are > > primary speakers of languages other than English? > I actually don't have strong opinions about what the solution should be, > and I believe Denise when she says that the current livejournal model > doesn't work and shouldn't be duplicated. I just wanted to have > registered a concern early on about any solution that involves entirely > separate sites for different languages. If it is in fact done that way, > integration really does need to be entirely seamless--i.e., people like > me need to be able to add people on a dreamwidth clone to our Trust and > Watch lists, for example, and they need to be able to add me to theirs. > > I understand that there won't be any solution for a while, and that's > fine. But when one does start to be tackled, I'm hoping that the > dreamwidth team will keep these things in mind. > > -- > Jae/[email protected]/www.jaegecko.com/therealjae.livejournal.com > "If you must put me in a box, make sure it's a big box > with lots of windows and a door to walk through > and a nice high chimney" -- Dan Bern, "Jerusalem" > > _______________________________________________ > 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
