SERVICE does not seem to be LiveJournal-based.
#Dreamwidth import livejournal password#
The username and password you gave us for SERVICE was rejected, so we couldn't download any information.We apologize for the problem and hope things can be resolved. We were unable to transfer your journal OTHERNAME from SERVICE to your account USERNAME on Dreamwidth. These email templates will be sent out when we manage or fail to transfer a journal.Ĭould not transfer your journal from SERVICE to your account USERNAME on Dreamwidth That way, the OpenID identity holder can verify that their words haven't been edited offline.Įither way, it would be very very nice if there were a place where an OpenID identity could go and see all their OpenID comments that have been imported and take ownership of them under a specific linked DW account.] If someone is importing their journal from downloaded backup file, import all comments as OpenID comments screened, frozen, visible only to the journal owner and the OpenID identity that made the comment, and unable to be unscreened/unfrozen by the journal owner him/herself, only the OpenID identity. If someone is importing their journal directly from another site, by giving us their username and password for that site, import all comments as OpenID comments with the same screening/visibility level that the original comment had. That the OpenID owner of the comments could find them and possibly To make this work better, imported comments should be listed somewhere Original comment poster could elect to own and unprivatescreenĪfter this point, the journal owner could screen/unscreen the comment at will. Unscreened on the original, someone OpenID-authenticated as the This would be doneĪccording to the screening settings on the original post: if Handle privately-posted imported comments. Supposing also that the comment screening mechanism were modified to This would allow a maximum amount of the user's Posted, and comments belonging to the user were imported and postedĪccording to their current screening setting in proper threads with Supposing comments belonging to others were imported and privately Options: "import tags, tag prefix, tag suffix" "import comments"? "import friend groups, tag prefix, tag suffix" "import all as *security*".exor674 I think one of the things we'd need to add for the import feature is a external-logid logprop, so if somebody tries to import twice you won't get twice of the entries - AND the systen can know "oh DW entry 1 was originally -exor674-5827377212221211".I need to find a proper "insert comment and metadata in the same instant" command, as I don't want a possible instant where someone can see a comment that is supposed to be screened.I think this is wanted, import them as OpenID?.Probably need to scrub a few more things.Need to fail cleaner if this is missing (like on DJ).Get it compiling after some changes merged in from test tool.
0 kommentar(er)
