ladyasul: A picture of the back of a fairy, with their red-and-gold wings spread out. (Default)
[personal profile] ladyasul

Title:
Add ability to link OpenID account to DW account during content imports from other sites

Area:
site: openid, workflow: importer, and maybe site: usability

Summary:
Subsuming your OpenID while importing content created by the OpenID's account (such as associating the OpenID of Username@Livejournal while importing Username's journal contents from Livejournal) seems a very logical thing. Suggest there be an option on the Import Content page, which is easily reachable in the larger DW-sitescheme header, to do that in the course of importing content, or at least a link to the page for associating the OpenID, with a blurb explaining what it's for. To an end user, these two processes look to be rather closely related, so to have them obviously linked seems neatly intuitive.

Description:
I imported an account from LiveJournal a while ago and checked an entry's page, only to finally realize that comments made by that account, while it was on LJ, to its own posts... did not register as belonging to the new account on Dreamwidth, although the entries in the journal correctly said that they belonged to the DW account.

I realize that importing content from a non-DW journal to a DW journal and claiming ownership of that non-DW journal's comments are two separate things, but they feel as though they should go together somehow.

I can see two ways of doing this quite neatly, and in a way that makes things clear to the new user. The first would be to include a note on the Import Content page stating that "importing the comments on a journal's entries does not claim ownership of the journal's own comments, but this tool can take care of that for you: (and a link to the appropriate page for subsuming your OpenID accounts)" or something to that effect.

The other way, which I suspect would be more work, but still end up pleasing many users, would be to combine the two pages, so that you could take care of both tasks at once, if you wanted. There's all sorts of options for what to import, exactly, and you already need to enter your username and password, and specify which site to import from. Taking ownership of that account's comments, especially on its own pages, seems a logical and intuitive part of the process, to me.

If the second idea is gone for, still having a note and link like the first idea, in the Import pages (and it being pointed out that taking ownership of the OpenID account works for all OpenID sites, whereas importing the content only currently works for LiveJournal and InsaneJounral, would be great too) would be very handy, especially as it isn't linked directly in the header navigation, while Import Content is.

Poll #14591 Add ability to link OpenID account to DW account during content imports from other sites
Open to: Registered Users, detailed results viewable to: All, participants: 26


This suggestion:

View Answers

Should be implemented as-is.
16 (61.5%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
9 (34.6%)

(Other: please comment)
1 (3.8%)

bulma: A four star dragon ball png (Default)
[personal profile] bulma

Title:
Import entries from Scribbld.com

Area:
import

Summary:
There is no option to import from scibbld.com

Description:
I have several accounts on Scribbld.com that I would like to import content from, but Dreamwidth doesn't seem to allow for this option (only livejournal and insanejournal). I could go through every entry and repost it to another account on dreamwidth, but that would be a tedious task. LJarchive doesn't work on my mac, and I've tried using it on someone else's PC, but for some reason it isn't functioning on there either because there's some component missing in the operating system or something.

In short, please see if you guys can find a way for us to import content from accounts on scribbld.com to dreamwidth.org. Thanks!

Poll #12202 Import entries from Scribbld.com
Open to: Registered Users, detailed results viewable to: All, participants: 57


This suggestion:

View Answers

Should be implemented as-is.
27 (47.4%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
29 (50.9%)

(Other: please comment)
1 (1.8%)

montuos: cartoon portrait of myself (Default)
[personal profile] montuos

Title:
Importer error pages need buttons for the next step

Area:
Importer

Summary:
If you omit any information when starting the importer, the error page drops the ball on guiding you to the next step of the process.

Description:
When using the importer [https://www.dreamwidth.org/tools/importer], I forgot to click the site I wanted to import from before I filled in my userid and password and then automatically hit enter. The error page that comes up when you do that [https://picasaweb.google.com/lh/photo/6s-ph1Nbgfxy0p3zwIqYi9MTjNZETYmyPJy0liipFm0?feat=directlink] drops the ball on what to do next. It says "Please select a service to import data from." but the options for that are not displayed, and there is no further guidance for what the user should do. Further testing reveals that you get "Please provide a username and password for the service that you selected." if you forget either of those, but again, there is no further guidance for what the user should do.

In a perfect world, the error page should remember all the information already provided, including the password, and repeat the "Choose a service to import from:" or "Username on other service"/"Password on other service" item that was missed, and have a Continue button to proceed forward.

My secondary preference would be to have a button to go back to the missing step. This would be a more versatile fix since you get the exact same error not just from failing to select a site but also when you fail to fill in any of the information. However, I would prefer not to have to go back because although the username is remembered, I have to re-enter my password for the other site.

At the very least, even if no buttons are added to the error page, there should be an instruction to use the browser's Back button. Again, I would prefer not to have to go back because I have to re-enter my password for the other site even when I already did that.

Poll #10446 Importer error pages need buttons for the next step
Open to: Registered Users, detailed results viewable to: All, participants: 47


This suggestion:

View Answers

Should be implemented as-is.
31 (66.0%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
16 (34.0%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Integrate better with LiveJournal's "spoiler" tag

Area:
entries, comments, importing, crossposting

Summary:
LiveJournal has implemented a <lj-spoiler> tag, which should be accounted for when importing and crossposting.

Description:
There's been past discussion (most recently http://dw-suggestions.dreamwidth.org/1303478.html ) about how to best make a spoiler/trigger/not-expanded-by-default tag work for entries and comments on Dreamwidth. LiveJournal has since implemented a method to do just this, and it would be wise to remain compatible with it.

When importing, entries with <lj-spoiler> tags should retain the type of concealment it is, the custom warning text if any, and the text within.

When importing, comments with <lj-spoiler> tags should not lose any data.

When Dreamwidth implements its own version, things tagged with <lj-spoiler> should be backwards compatible - if already posted, they should be treated accordingly.

New crossposted entries containing the <lj-spoiler> tag should be passed on to LiveJournal without mangling the tag; when our version happens, it should convert to LiveJournal syntax when crossposting to LiveJournal, just as usernames are.

New entries containing the <lj-spoiler> tag should be displayed sensibly on Dreamwidth, either consistent with a regular <cut> tag (if that's quick and easy to set up before implementing it properly) or properly.

Whatever method we use should remain accessible. If implemented with scripts for inline expansion, non-script viewing should retain any custom warning text and the fact that this was concealed, and give sufficient time and space for people to decide to stop reading (this should accommodate very fast readers who skim and can absorb the gist of whole sentences/paragraphs in seconds before their executive function has caught up, as well as screen reader users who may need time to tell their screen reader to stop reading). It should also not suck for mobile device/small screen users.

One possible method would be to automatically add "spoiler space" as was done manually on email lists of old: for example, typing <mask text="OMG!">WTF!!</mask> (or however it's decided to do locally) might result in:

*** MASKED CONTENT: OMG! ***

*
*
*
*
*

WTF!!

*
*
*
*
*

*** END MASK ***

Poll #9954 Integrate better with LiveJournal's "spoiler" tag
Open to: Registered Users, detailed results viewable to: All, participants: 73


This suggestion:

View Answers

Should be implemented as-is.
52 (71.2%)

Should be implemented with changes. (please comment)
4 (5.5%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
16 (21.9%)

(Other: please comment)
1 (1.4%)

cesy: "Cesy" - An old-fashioned quill and ink (Default)
[personal profile] cesy

Title:
Option to show "originally posted as" on imported entries and comments

Area:
entries, comments, importing

Summary:
Expose "originally posted as" on imported entries and comments, as an option that can be added to styles if desired.

Description:
Some users would like to be able to see where a comment or entry has been imported from, if they are importing from several locations or different names, or wish to display the history in full on Dreamwidth. Other users would prefer to keep the current display. I propose that the importer is updated to preserve the username and site/OpenID name at the time of import, so that this information is available to style designers, who can then create styles with it displayed, or add it to their styles as an option for those who want to show it on their journals. For previously imported entries where the original import site has not been saved, this would display something like "Originally posted as: information not available".

Poll #9857 Option to show "originally posted as" on imported entries and comments
Open to: Registered Users, detailed results viewable to: All, participants: 63


This suggestion:

View Answers

Should be implemented as-is.
22 (34.9%)

Should be implemented with changes. (please comment)
10 (15.9%)

Shouldn't be implemented.
7 (11.1%)

(I have no opinion)
24 (38.1%)

(Other: please comment)
0 (0.0%)

fiddlingfrog: (Default)
[personal profile] fiddlingfrog

Title:
Send inbox notification to new OpenID accounts upon comment or entry importation

Area:
inbox, importer

Summary:
When the importer imports a comment, it should leave a notification in the inbox of the associated OpenID account stating "A comment you left at {original site} has been imported to {Dreamwidth journal/community name}."
When the importer imports an entry from a community import, it should leave a notification in the inbox of the associated OpenID account stating "An entry you wrote in {original community} has been imported to {Dreamwidth community name}.

Description:
Currently OpenID accounts have very little ability to find comments, and soon entries, that have been imported to Dreamwidth. The Recent Comments page only goes back 10 comments, and deleting one of those comments doesn't let another one slide in at the back of the list. Currently the search by poster function [http://foo.dreamwidth.org/?poster=] doesn't work for OpenID accounts, not by using the displayed name {bar.livejournal.com} nor by using the internal name {ext_###}. Unfortunately, it's too database heavy to try and search for all comments and entries an account made anywhere that isn't their journal, so my idea is to give the user a place to start looking themselves.

When the importer imports a journal or community, it should leave a notice in the Dreamwidth inbox of the OpenID account that's been created (or added to) stating what action just happened. It only needs to leave one notification per import.

Under this idea, a user from LiveJournal would log into Dreamwidth for the first time using their OpenID credentials and find an inbox with several notices already waiting for them, like this:

"Comment imported to {Journal A}"
- A comment you left in {Imported journal's original address} has been imported to {Journal A}
"Entry imported to {Community B}"
"Comment imported to {Community B}"
"Comment imported to {Journal C}"

Edit: It's one message per import, not one message per comment/entry.  If you count the community and comment import as a single job, it's up to two message per import.
For example, say somebody decides to import [livejournal.com profile] gardening to DW. In my OpenID account's inbox I'd get one notification saying that an entry or entries I posted there had been imported to DW. I'd get another notification saying that comments I had left there had been imported to DW. And that's it.

Upsides: OpenID users feel more in control of imported content.
Downsides: Will probably slow down the importer.

Poll #9001 Send inbox notification to new OpenID accounts upon comment or entry importation
Open to: Registered Users, detailed results viewable to: All, participants: 59


This suggestion:

View Answers

Should be implemented as-is.
18 (30.5%)

Should be implemented with changes. (please comment)
11 (18.6%)

Shouldn't be implemented.
5 (8.5%)

(I have no opinion)
25 (42.4%)

(Other: please comment)
0 (0.0%)

tetoest: (Default)
[personal profile] tetoest

Title:
Imported Writer's Block Posts

Area:
Importer

Summary:
Replace the link on imported writer's block posts from Livejournal with the text of the actual question.

Description:
I've noticed that posts I've imported from Livejournal containing Writer's Block questions do not display correctly. This is probably because the question is not included in the text of the post but instead rendered as "lj-template qotd" enabling associated links to other answers.

When this is imported the code isn't recognised and displays as an error and leaves the post without the question it is answering. I don't pretend to know how the importer works and, for the six posts that I have, I can edit it manually.

I was curious though if it would it be possible to have the importer pull the data and then replace lj link with the plain text of the question instead.

Poll #8901 Imported Writer's Block Posts
Open to: Registered Users, detailed results viewable to: All, participants: 71


This suggestion:

View Answers

Should be implemented as-is.
19 (26.8%)

Should be implemented with changes. (please comment)
1 (1.4%)

Shouldn't be implemented.
6 (8.5%)

(I have no opinion)
38 (53.5%)

(Other: please comment)
7 (9.9%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Import content from an authenticated Twitter account

Area:
importing, Twitter

Summary:
Import the day's tweets from a twitter account under the user's control. This would eliminate the need to share one's Dreamwidth password with an external service, and might be able to have settings tailored to take better advantage of Dreamwidth's features.

Description:
Some people like to import the day's tweets from their Twitter accounts to Dreamwidth. (For archival purposes, so friends who don't do Twitter can read it, for people who use Twitter to collect interesting links, et cetera.) Some people don't care to see Twitter imports showing up on their reading lists.

Having a Dreamwidth-side importer is likely to be useful to both of these parties: people who do import can do so more easily and using more of Dreamwidth's features; having a Twitter-importer that supports tags means more people's imports will be tagged consistently and will therefore let paid users set up their default reading filters more accurately to exclude those tags; if the Twitter-importer consistently wraps the imported entry in <div class="LoudTwitter">, it will remain compatible with most existing make-Twitter-imports-disappear style hacks.


Must authenticate to Twitter properly (I believe Twitter now requires OAuth). While one technically can scrape up an unlocked account, authenticating to the Twitter account means that the user has control over that account, and therefore should have authorization to repost to Dreamwidth. Authentication also means locked accounts are visible.

Must collect all tweets daily, whether from a locked or unlocked account. (The Twitter account being locked should not prevent from public posting, because some people are merely locked to keep out the Twitter spambots.)

Should be able to set a security for all imported-from-Twitter entries that is distinct from the minimum security; some people prefer to post their Twitter imports to a custom security group even if their minimum is public. (Locked twitter account and locked entries would maintain security for people who need it.) For UI, the set-minimum-security setting in the 'Manage' area should link back and forth to the Twitter-imported-entries security setting, in case someone found one but wanted the other.

What should happen if someone switches from public on Twitter to locked on Twitter? Is this something the service should look out for and send a notification about? Probably a notification paired with a "Match the security setting on Twitter (if there are multiple, go with the most restrictive)" setting for entry security (as well as the usual selections) would solve that problem.

Should reproduce the tweet as seen on Twitter as faithfully as possible, including http:// links working clickably, @links working correctly, and #hashtags linking to a Twitter search for the hashtag. (Known incompatibility: mentioning IRC channels on Twitter turns them into hashtags, even though you might prefer to have the IRC channels link usefully.) (It would be nice to optionally include in-reply-to, location, and other doodads, but even though retrieving them through the API may be easy, would they be really wanted in an import?)

Should collect retweets via the most modern method, as using the old method makes the end cut off if it's long.

Options for:
timestamps or no timestamps; timestamp format.
linkback to original tweet, or no link back.

Should be able to set tags to be applied to every imported entry (suggest "twitter"). (This will help with paid users' filtering, but since exclude-a-tag is at this point per-user, as long as the one user keeps consistent tagging, it shouldn't matter whether the tag is 'twitter' or 'chickens shifting in the night'.)

Would be nice to have an option that would try to use any hashtags in the import as tags on the entry (but would fail back to only existing tags if it went over the number of allowable tags, and would send a message that tagging on this automatically posted entry did not work properly, and maybe send a list of the tags that could not be created).

Should be able to set userpic (if they have a userpic called "twitter", maybe have it pre-selected for them?)

Should be able to customize the subject, with variables to insert the date and/or number of tweets if you want to, in your exact preferred configuration.

Should be able to cut tweets, either all of them entirely, or after some small reasonable number. My service does 5; LJ's does 10. Either of these are reasonable.

Should be able to customize the cut text.

What time options should there be for posting? Twittinesis posts sometime in the middle of their night. LiveJournal's posts at noon. My script host posts five minutes before midnight. Would there be a way to allow customization of posting time that does not affect site performance? It seems as though allowing a post to be set at an exact time would possibly set up situations where too many people would try for the same thing and bog things down. Though a reasonable effort should be made to a) have the things post at the same time for the same person, and b) get the tweets of a particular span, most popular likely to be the whole day's twittery.

Should the time on the entry correspond to the last time in the included tweets (and/or the time the user wants the thing to run), or to the actual time it's sent? (If the time it should have been posted and the time it was posted differ, what happens if the journal owner posts in between then? Maybe try again with the actual time?)

Should have the option to use the 'do not show on reading pages' option, in case someone wants that.

Should be robust enough to try again if Twitter failwhales for any reason while attempting to fetch.

Should be able to choose whether to import all tweets, or only tweets that lack an in-reply-to. (without in-reply-to is good for not having half-a-conversation, but bad if what you wanted to do was archive it all for your own use). There's some debate about whether the without-@ should be tweets that don't start with an @-name, or tweets that have an in-reply-to -- various clients handle things differently, and sometimes break in-reply-to when it should be there, or one was starting a conversation.

Might want to set up more than one import (paid feature?), from either multiple accounts (some people have lots) or multiple imports for the same account (one public, cut and without @replies, one private, uncut, with @replies, for example)

Should expand as many as possible shortened URLs (including t.co links), to prevent the failure of a shortening site from making your old links useless. (There are, however, some people who use shorteners on purpose? What about them?)

Since it's an archival under the control of the person who wrote the tweets (the ones that aren't retweets), rather than a fully operational client, I'm not sure how much of this stuff applies, but it's potentially useful: http://dev.twitter.com/pages/display_guidelines

While it would be nice for people to be able to run a Twitter-importer like an importer from other journal sites, and slurp up all the data for past days, there are limits on the Twitter API for how much you can extract from the site: the REST API lets you pull up to approximately 3200 items, the other APIs top out at 800. (So if someone SOMEHOW MANAGES to tweet over 800 times in one day, they'll probably not have all their tweets ship. However, I'm darned chatty on Twitter, and I don't believe I've ever gone over 200.)

Mood, location, music, adult content -- can these be left alone, or should there be settings for them?

Should there be the ability to override the default crosspost settings for this type of entry?

Comments/comment screening?

Poll #6506 Import content from an authenticated Twitter account
Open to: Registered Users, detailed results viewable to: All, participants: 64


This suggestion:

View Answers

Should be implemented as-is.
28 (43.8%)

Should be implemented with changes. (please comment)
9 (14.1%)

Shouldn't be implemented.
4 (6.2%)

(I have no opinion)
23 (35.9%)

(Other: please comment)
0 (0.0%)

[personal profile] samueljames

Title:
Importing Individual Entries From Other Journalling Sites Using URLs

Area:
Importing

Summary:
The idea would be that in the import function you would have the ability to choose specific entries to import.

Description:
The only site I import from is LiveJournal. The reason for my suggestion is that I keep only my fanfic on Dreamwidth. If I do an import I then need to manually delete lots of non-fic entries. I'm not technically minded so I don't have any idea of whether this would be doable and if it were whether it would get enough use to warrant the change.

I was thinking something along the lines of the import function that they have on Archive Of Our Own. I don't often use it because it doesn't format everything exactly the way I want but am thinking that it could work between Dreamwidth and other journalling systems as the entries look alike in terms of title, icons, tags and the actual entry text itself.

On their system you can list several URLs at once but I would be happy with one at a time. In an ideal world the import function would have the option to import all journal content or import by URL and the user would be able to put the URL from their posted entry in LiveJournal, InsaneJournal etc into Dreamwidth and just have that specific entry appear on their Dreamwidth Journal.

Poll #6503 Importing Individual Entries From Other Journalling Sites Using URLs
Open to: Registered Users, detailed results viewable to: All, participants: 53


This suggestion:

View Answers

Should be implemented as-is.
24 (45.3%)

Should be implemented with changes. (please comment)
5 (9.4%)

Shouldn't be implemented.
3 (5.7%)

(I have no opinion)
21 (39.6%)

(Other: please comment)
0 (0.0%)

teapotgirl: (Default)
[personal profile] teapotgirl

Title:
Another journal site for the Importer

Area:
importer

Summary:
Would it be possible to add Blurty to the sites we can import entries from since it's also based on the Livejournal code?

Description:
Even though Blurty was not the first place to go during the big Livejournal exodus, a lot of people still set up journals there.

Poll #4418 Another journal site for the Importer
Open to: Registered Users, detailed results viewable to: All, participants: 33


This suggestion:

View Answers

Should be implemented as-is.
8 (24.2%)

Should be implemented with changes. (please comment)
1 (3.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
23 (69.7%)

(Other: please comment)
1 (3.0%)

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
[Suggestion submitted by OpenID user, reposted by moi.]

Summary:

Add ability to import Vox journals by the end of September 2010.

Description:

Since Vox is shutting down at the end of September 2010, is it possible for you all to add the ability to import a Vox journal in such a short time?

Suggested by:

ext_83128

Poll #4323 Add ability to import Vox?
Open to: Registered Users, detailed results viewable to: All, participants: 57


This suggestion:

View Answers

Should be implemented as-is
34 (59.6%)

Should be implemented with changes (please comment)
1 (1.8%)

Shouldn't be implemented
1 (1.8%)

(I have no opinion)
20 (35.1%)

(Other: please comment)
1 (1.8%)

eosrose: (Default)
[personal profile] eosrose

Title:
Importing to a community

Area:
importer, communities

Summary:
In many cases individuals create personal communities closed to posting from visitors in order to house their creative works (or for similar reasons). These individuals should also be able to import their works.

Description:
The idea of importing whole communities with open membership sounds quite daunting for the very reasons mentioned in the FAQ--the admin does not always own the content of that community. And, unfortunately, I can't see how DW could possibly code things in such a way as to allow communities with posting access limited solely to the owner/admin to be an exception to the general rule at this time. So while I look forward to the day when communities can be imported by admins in the same way as personal journals, that is not what I am trying to propose here.

What interests me is the potential for an admin to import content from a personal journal hosted on another LJ-based service (or even from one hosted on DW). This, I think, would be most useful after the suggestion that content be imported according to tag be put into place, though I can see a potential for usefulness before that, too.

There is potential for abuse here, make no mistake, but admins always have the power to cause trouble when it comes to the communities they control.

The goal of this suggestion is to make life easier for people who want to start keep personal communities, but haven't yet. This particular feature probably wouldn't help those who already have personal communities and it wouldn't help maintainers of open communities.

An alternative might be to allow personal journals on DW to be converted to communities without deleting entries. Once the journal becomes a community, importing no longer becomes possible, which might help with some of the potential for abuse. (Though this idea wouldn't do me much good, since I already created my community and I think reverse conversion is impossible for good reason. ;_;)

Poll #3688 Importing to a community
Open to: Registered Users, detailed results viewable to: All, participants: 32


This suggestion:

View Answers

Should be implemented as-is.
17 (53.1%)

Should be implemented with changes. (please comment)
1 (3.1%)

Shouldn't be implemented.
1 (3.1%)

(I have no opinion)
13 (40.6%)

(Other: please comment)
0 (0.0%)

glymr: (Default)
[personal profile] glymr

Title:
Please make imported entries act like crossposted entries

Area:
Importing, crossposting

Summary:
When editing imported entries on Dreamwidth, the edits should also be applied to the original post (similar to crossposted entries).

Description:
Occasionally I will edit old entries, to modify tags or fix errors, etc. I was extremely pleased to find that when I edit a crossposted post on DW, its counterpart on LJ is also edited (this made me decide to buy a paid account at DW, in fact). However, if I edit any of my many *imported* entries, the original post it was imported from at LJ is not modified.

It would make a lot of sense to treat imported entries like crossposted entries, and might make people feel more comfortable about coming over to DW, because they know they will have a true mirror of their archive without having to edit two different posts if they need to make a change to one of their older posts.

Poll #3027 Pleas make imported entries act like crossposted entries
Open to: Registered Users, detailed results viewable to: All, participants: 63


This suggestion:

View Answers

Should be implemented as-is.
33 (52.4%)

Should be implemented with changes. (please comment)
17 (27.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
13 (20.6%)

(Other: please comment)
0 (0.0%)

martzin: (Default)
[personal profile] martzin

Title:
Prevent OpenID relationships from cluttering profile pages

Area:
profile page

Summary:
On profile pages, relationships with DreamWidth accounts should stand out from those with OpenID accounts.

Description:
OpenID accounts that are given access tend to drown out actual DreamWidth accounts on the profile pages of people who used the import tool.

I suggest displaying DreamWidth accounts first, then OpenID accounts grouped by site, using the compact style — <user site="www.site.com" name="username" /> — for known sites.

Poll #2871 Prevent OpenID relationships from cluttering profile pages
Open to: Registered Users, detailed results viewable to: All, participants: 66


This suggestion:

View Answers

Should be implemented as-is.
15 (22.7%)

Should be implemented with changes. (please comment)
40 (60.6%)

Shouldn't be implemented.
4 (6.1%)

(I have no opinion)
7 (10.6%)

(Other: please comment)
0 (0.0%)

melannen: Commander Valentine of Alpha Squad Seven, a red-haired female Nick Fury in space, smoking contemplatively (Default)
[personal profile] melannen

Title:
Import with wipe

Area:
Importer

Summary:
I would like to move my content from LJ to DW without completely breaking existing links; I'd like the importer to have the option to automatically replace the text of lj entries with a link to the DW import.

Description:
Basically, what it says in the summary: I don't want to leave my content on LJ (partly for housekeeping - I don't like to have multiple copies scattered around the webs; partly due to trust issues) but I want old links to the LJ posts to still point to the post content. I could do this manually, going through after the DW import and replacing the content with a link one entry at a time, but having an option for the importer do it automatically would be *so* much easier. And it seems like something it would be able to do.

The one caveat is you would have to make it *very* difficult to do this accidentally. Letting people do it accidentally would be bad.

Poll #2422 Import with wipe
Open to: Registered Users, detailed results viewable to: All, participants: 58


This suggestion:

View Answers

Should be implemented as-is.
39 (67.2%)

Should be implemented with changes. (please comment)
17 (29.3%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
2 (3.4%)

(Other: please comment)
0 (0.0%)

zellieh: kitten looking shocked, openmouthed, text: WTF? (What the fuck?) (Default)
[personal profile] zellieh

Title:
When importing, update/change internal links

Area:
Importing, links

Summary:
When I imported my LJ entries to DW, a lot of my LJ entries were cross-linked to other entries in my LJ , so it would be great if the Importer could update those links to the new DW URLs when it imports those entries.

Description:
As I import entries from my LJ (or other journalling service), any internal cross-links from one of my journal entries to another of my journal entries should be updated as well.

So, if my LJ post 'zellieh.lj.com/123' (which becomes something like 'zellieh.dreamwidth.org/123') contains a link in it to another of my posts, 'zellieh.lj.com/100', then that link should be updated it's new Dreamwidth URL, 'zellieh.dreamwidth.org/100'.

NOTE: I am only suggesting this initially for links that go from one of my journal entries to another of my own entries, not for any links to other people's journals.

I am not a technical person, but I'm assuming that at some point in the import process, there's a record of the old LJ URLs and the new DW URLs for each entry; I'm hoping that that's the information that could be used to update the internal links.

Pros: This would save a lot of time when moving from another journal site to Dreamwidth, because you wouldn't have to go back in and hand re-code a lot of older links on older posts. (Something I still haven't done, because I am dreading the work involved.)

Cons: It would likely complicate and slow down the initial importing process, and you would likely have to wait until you had all the information available at the end of the import before you could update all the links. Perhaps it might be better as a separate option, or next step after the import is complete?

Poll #2420 When importing, update/change internal links
Open to: Registered Users, detailed results viewable to: All, participants: 44


This suggestion:

View Answers

Should be implemented as-is.
17 (38.6%)

Should be implemented with changes. (please comment)
19 (43.2%)

Shouldn't be implemented.
2 (4.5%)

(I have no opinion)
4 (9.1%)

(Other: please comment)
2 (4.5%)

crystalpyramid: crystal pyramid suspended in dimensional abnormality (Default)
[personal profile] crystalpyramid

Title:
imported entries should appear on friends pages

Area:
entry importing from offsite

Summary:
When I import a recent entry from LJ to DW, it should appear on my DW friends' reading pages just like an entry I posted normally. Or make it customizable somewhere in my our their settings. Right now I have to repost anything I've imported if I want it to show up on their reading pages.

Description:
Right now, when I import recent entries from offsite (LJ) to DW, my friends on DW say that those entries do not appear on their reading pages. I've been working around that by reposting the entries on DW with basically the same text again, but that's kind of awkward and unattractive. Also, the fact that imported entries don't show up is counterintuitive, and it took me a while to realize that was what was going on, since clearly the entries were visible in DW as well. It might cause more trouble for someone who's less familiar with possible modes of failure.

It would be better if, when I import a recent entry from LJ to DW, it appeared on my DW friends' reading pages just like an entry I posted normally. It's possible that, for people reading entries from multiple sites on DW, this could lead to duplicate entries, but I imagine that there is already a workaround for this, since it also comes up with crossposting. I can't think of any other obvious drawbacks, but if it seems like they might exist, you could always make it an option in the import menu &mdash; a checkbox with "make these entries visible on my friends' reading pages", perhaps unchecked by default.

Poll #2388 imported entries should appear on friends pages
Open to: Registered Users, detailed results viewable to: All, participants: 44


This suggestion:

View Answers

Should be implemented as-is.
2 (4.5%)

Should be implemented with changes. (please comment)
11 (25.0%)

Shouldn't be implemented.
27 (61.4%)

(I have no opinion)
4 (9.1%)

(Other: please comment)
0 (0.0%)

eos_rose: (Default)
[personal profile] eos_rose

Title:
Maintaining entries imported into Dreamwidth

Area:
importing, crossposting

Summary:
If you find that you need to edit an entry that you've imported from another service and you want to maintain both old and new journals, presently you'll need to edit the entry twice: once on Dreamwidth, once at the old service. Wouldn't it be great if the two entries were connected like crossposted entries?

Description:
I, like many, still maintain a heavy presence over at livejournal. I want to import older entries here, but I'm in the process of revamping older entries and don't want to have to do so more than once. Changing an imported entry on Dreamwidth does not change the entry on the original service. Re-importing entries (so far as I am aware) only adds new comments and entries, but does not notice edits. This can make editing imported entries very tedious.

If possible, I propose that imported entries somehow be treated like crossposted entries, provided that the journal imported from is on a user's crossposting list. I'm not a coder, so I can't say what is possible and what is not or how problematic this could be. It would make life a lot easier, however.

Poll #2333 Maintaining entries imported into Dreamwidth
Open to: Registered Users, detailed results viewable to: All, participants: 32


This suggestion:

View Answers

Should be implemented as-is.
19 (59.4%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
4 (12.5%)

(I have no opinion)
8 (25.0%)

(Other: please comment)
1 (3.1%)

ex_xo956: (Default)
[personal profile] ex_xo956

Title:
Importing Dreamwidth journals into Dreamwidth journals

Area:
Import Content, Entries

Summary:
It would be uberly, superly awesome if you could import a DW journal into another DW journal. For example, I created ABC as a public journal and XYZ as a private friends only journal and eventually, I decide I'd like to import ABC into XYZ so I can have all my entries in one place.

Description:
I'm really surprised no one has suggested this yet and so now I'm wondering if it's one of those things that just can't be done and I'm the village idiot standing around waiting for everyone to breathe water. :P Or worse, it's some kind of cyber-faux-pas to request such a thing...

One drawback to this thing that I am suggesting is that, if someone combines their journals but leaves the original one still standing, it takes up superfluous server space. It could be implemented such that, if you combine DW journals, the one being imported is automatically queued for deletion...but there could be a reason someone would want to combine and leave the original standing. I don't know.

The reason I came up with this at all is because I'm consolidating ALL of my online journals into one journal and I would like to add my DW journals to this one.

OOO! I just thought of something else actually...MOVING entries from one DW journal to another. So it would be a totally different feature from the Import Content because would be A.) importing entries and B.) deleting the entries from the place they were imported. That could get really tricky though - if there were any glitches at all, entries could be lost forever...

Well, I think I'm done brainstorming this one. :P I'll go ahead and turn this over to the people who know what they're talking about and I'll wait to see if I've invented the wheel or if I'm suggesting we all start breathing water. ;)

Poll #1925 Importing Dreamwidth journals into Dreamwidth journals
Open to: Registered Users, detailed results viewable to: All, participants: 43


This suggestion:

View Answers

Should be implemented as-is.
16 (37.2%)

Should be implemented with changes. (please comment)
21 (48.8%)

Shouldn't be implemented.
4 (9.3%)

(I have no opinion)
2 (4.7%)

(Other: please comment)
0 (0.0%)

hatman: HatMan, my alter ego and face on the 'net (Default)
[personal profile] hatman

Title:
More options when importing - add tags, set security, set icon

Area:
Importer

Summary:
When importing entries, have the options to add a new tag, apply an access filter, and choose a default userpic to/for the batch.

Description:
Mostly for those importing entries from multiple journals.

1. Have an option when importing to add a new tag to the entries being imported (in addition to any tags that may exist in the original entries).

This would help journal owners and readers keep track of what came from where.

It would also allow essentially the reading of the original journal. Anyone who wanted to review the original journal or catch up on it (and might not be on the offsite access list) could just click the tag to pull those entries out, sorted by date.

2. Additionally, have the option to import to an access filter. That is, apply an access filter to an entire batch of imported entries. Or, more generally, set a new minimum security level for the batch.

This would be used when importing a private journal or one with a specialized access list.

It would also allow the journal to be imported as a private archive, even if the journal being imported has a higher offiste security level.

3. Have the option to pick a different default userpic for a batch of imported entries (to be applied as a one-shot deal by the importer). Useful for when you don't want to import all userpics from the original journal but don't want the DW default userpic applied to the imported entries.

Downsides:

Higher resource demands on the importer.

Not sure what, if any, coding issues would be involved.

As cool as more flexibility/options/bells&whistles can be, increasing options can lead to increased chance of confusion and errors.

Poll #1814 More options when importing - add tags, set security, set icon
Open to: Registered Users, detailed results viewable to: All, participants: 26


This suggestion:

View Answers

Should be implemented as-is.
15 (57.7%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (42.3%)

(Other: please comment)
0 (0.0%)

Profile

Dreamwidth Suggestions

April 2017

S M T W T F S
      1
23456 7 8
9 101112131415
16171819202122
23242526272829
30      

Style Credit

Expand Cut Tags

No cut tags

Syndicate

RSS Atom