[personal profile] swaldman

Title:
Allow Twitter OAuth identification instead of OpenID for commenting

Area:
openID (sort of)

Summary:
Allow Twitter OAuth identification instead of OpenID for commenting

Description:
A lot of my readers these days don't come from LJ or Dreamwidth, may not have an OpenID, or even if they do have one (most likely Google) don't know what an OpenID is. But most of them have a Twitter account. It would be nice if Twitter OAuth could be used as an identity for commenting. Possibly other OAuth providers too.

Poll #16835 Allow Twitter OAuth identification instead of OpenID for commenting
Open to: Registered Users, detailed results viewable to: All, participants: 46


This suggestion:

View Answers

Should be implemented as-is.
30 (65.2%)

Should be implemented with changes. (please comment)
7 (15.2%)

Shouldn't be implemented.
3 (6.5%)

(I have no opinion)
6 (13.0%)

(Other: please comment)
0 (0.0%)

skakri: (Default)
[personal profile] skakri

Title:
OpenGraph implementation

Area:
frontend, accessibility, cross-site data sharing

Summary:
It would be nice if sites, that use OpenGraph metadata, could use our provided data, instead of crawling the page in question and collecting arbitrary data (article image, article title, author, etc.)

Description:
Sites that support OpenGraph Protocol (http://ogp.me/), like Facebook and Google+ would benefit from already provided data; that would help those sites 1) categorize that data (entry title, tags), 2) provide correct information, when posting to FB or G+ (title, image), instead of full page title (username | post, for example).

Example - http://skakri.grab.lv/2360053.html (check source; done: profile username, entry image, entry title, publishing date and used tags). Could be implemented also in profile pages - user.domain.tld/profile

Poll #9490 OpenGraph implementation
Open to: Registered Users, detailed results viewable to: All, participants: 39


This suggestion:

View Answers

Should be implemented as-is.
4 (10.3%)

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

Shouldn't be implemented.
3 (7.7%)

(I have no opinion)
31 (79.5%)

(Other: please comment)
0 (0.0%)

transcendancing: Darren Hayes quote "Life is for leading, for not people pleasing" (Default)
[personal profile] transcendancing

Title:
Crossposting to Dreamdwidth from Posterous

Area:
Crossposting

Summary:
I have what I call my 'grown up' blog over at Posterous (www.posterous.com) and maintain my beloved personal blog here on DW. Posterous auto crosspost to LJ and I desperately want an auto crosspost feature to DW.

Description:
Posterous (www.posterous.com) is a kind of tumbleblog and they have in place mechanisms to do auto-crossposting to other services. They don't yet do this to Dreamwidth and I've suggested it to them on multiple occasions, and I wonder if Dreamwidth approaching them whether it might actually happen. At present it seems to suffer from being at the bottom of the list of their priorities, and I respect that but it's increasingly difficult to make the best use of my blogging and time having to manually do the post/cross posting thing.

I am hoping that because DW is based on the LJ sourcecode that the work needed to have a DW auto cross post would be less work than they perhaps think it will be. I'm not a coder and I can't speak to that, sorry.

Having this ability will improve shareability between platforms, for those of us who do have multiple blog spaces it cuts down the time needed to manually post/link to/update all the spaces.

The drawback is that I'm asking DW about it and it relates to a push from another service to DW which possibly makes it not possible from this end. It may be that I need to push at Posterous and provide them with more context and detail as to how to go about implementing this.

This is a potential alternative actually, could you provide me with some support to liaise with Posterous so that I can make a better case to them about having the auto-crosspost feature if it's not within your purview or capability to directly engage with Posterous about this?

Hoping that I've provided a useful amount of detail for you and that it's a suggestion that is useful in some way.

Many sincere thanks for how approachable and involved you and the entire volunteer team of DW coders are with regard to improvements on the service and engaging with all the things big and little that matter to DW users.

Poll #8833 Crossposting to Dreamdwidth from Posterous
Open to: Registered Users, detailed results viewable to: All, participants: 48


This suggestion:

View Answers

Should be implemented as-is.
9 (18.8%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
39 (81.2%)

(Other: please comment)
0 (0.0%)

cat_77: Picture of Ghost with booze (Default)
[personal profile] cat_77

Title:
Safari Compatability

Area:
entries

Summary:
Allowing scrollable entry boxes compatable with iPad's version of Safari to make it easier to edit.

Description:
The iPad version of Safari does not permit scrolling in the entry boxes (like what I am typing in now), which makes it quite difficult to read through and edit entries that are longer than one "box worth" of information. This holds true for the original entry prior to posting, as well as attempting to edit a pre-existing entry. As there are no scrolling arrows on the iPad keyboard (only the Bluetooth accessory), you cannot simply use those within the entry box to get back up to an earlier part of the entry.

LJ has the same issue, but has an iPad compatable app which you can use instead. Understandably so, it does not crossover to any other journal site so you can only use it for LJ and not DW, which I much prefer to use.

Is there any sort of coding fix to allow this (likely a frames-related issue), or possibly a DW app in the works?

Much appreciative for any information you may be able to provide.

Thanks!

Poll #8379 Safari Compatability
Open to: Registered Users, detailed results viewable to: All, participants: 37


This suggestion:

View Answers

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

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

Shouldn't be implemented.
2 (5.4%)

(I have no opinion)
26 (70.3%)

(Other: please comment)
1 (2.7%)

flo: A lovely, purple-shaded teapot. (Default)
[personal profile] flo

Title:
Revamping the 'Export Journal' tool to allow exporting in larger time intervals

Area:
exporting, interoperability, backups

Summary:
Revamping the 'Export Journal' tool at http://www.dreamwidth.org/export so that you can export entries from your journal on a yearly basis, and also export it all as one giant file. Export options on that page could also use some clarification so that you understand why or why not to tick them.

Description:
Basically, I want to the basic export tool to allow me to export my journal as XML on a yearly basis as well, or even just all at once. Currently, the export tool at http://www.dreamwidth.org/export only allows you to export on a monthly basis, which means lots and lots of repetitive action if you post even occasionally on your journal. As far as I know, people that want to back up their Dreamwidth journals generally resort to something like LJ Archive, which is thorough, but can be inexplicably buggy, and is not at all maintained by Dreamwidth or otherwise affiliated with Dreamwidth. I would much prefer being able to export my journal with an on-site tool that I know will be fixed or improved as necessary, and I would be willing to go without exported comments if the Dreamwidth tool will provide a complete set of all my entries.

It would also be rather nice if the more esoteric options on the tool's page had more explanatory labels. Currently, this is approximately what the "Fields" options look like:

- ID Number
- Event Time (from your clock) *
- Log Time (from system's clock) *
- Subject
- Event *
- Security Level
- Allow Mask *
- Current Mood & Music

Some of these fields (the unstarred ones) are fairly self-explanatory. The rest are somewhat confusing to me-- "Event Time" and "Log Time" seem self-explanatory at first glance, but then you also have "Event", and before I actually looked at an export file, I honestly wasn't sure what all those fields would mean when taken together. "Allow Mask" is also really badly named, and probably should not be an option at all, since that field is basically the bit that is used to determine whether an entry is public or access-only. Not exporting that field just removes part of the distinction made between private and public entries in the export file, which really doesn't serve any purpose since the tool currently exports everything. A fine-grained option to control what is exported would be nice, but it probably should not be at all related to what fields get exported.

Another confusing option on the page is: "Don't translate between encodings". Is this something an end user is supposed to just know? I know what encodings are, and that option does not really tell me exactly what it does. Does ticking the option mean that it will just leave any entries that are not encoded as X (where X is the encoding you selected from the preceding combo box) as they currently are? Is this an option that's more for debugging or troubleshooting export files that don't import elsewhere correctly? Should it even be on the page at all?

As far as using the tool goes...well. There is nothing on the page that indicates that the tool will only export by month, so unless you got to it from the FAQ, you won't even know about that. When I tried putting in just the year to see if I would get an explanatory error, it basically just gave me an empty CSV or XML file named after the year. Putting in the wrong month/year combination also gave me an empty file, which, remember, I won't know about until I actually look within the file. Considering that the tool is supposed to let you export entries, I really think it should let you know when your settings mean that you will not be exporting any entries at all.

In summary, what I want is for the export tool to
a) Allow you to export entries by year
b) Allow you to export all your journal's entries at once
c) Provide understandable and useful options that will not make your export useless or incomplete in ways that you did not mean (e.g. if, for some reason, you do not select "Event", none of your entry text will be added to the export file)

If there is a question of the tool putting strain on the servers, the number of times that free users can export their journals can be restricted (e.g. once a month, once every couple months, etc).

Poll #7709 Revamping the 'Export Journal' tool to allow exporting in larger time intervals
Open to: Registered Users, detailed results viewable to: All, participants: 45


This suggestion:

View Answers

Should be implemented as-is.
20 (44.4%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
16 (35.6%)

(Other: please comment)
0 (0.0%)

robotech_master: (Default)
[personal profile] robotech_master

Title:
Add your site to addthis.com

Area:
posting

Summary:
Could you go to the following website and use it to submit a listing for Dreamwidth to the AddThis link sharing rouser plug-in? There is a listing for LiveJournal, but not one for Dreamwidth – and since I have Dreamwidth set to cross post to LiveJournal, I'd like to be able to post anything I would want to post there here instead.

http://www.addthis.com/services/submit?

Description:
This would mainly involve making sure that Dreamwidth is Oexchange compatible, and submitting the URL to the site descriptor.

Poll #7708 Add your site to addthis.com
Open to: Registered Users, detailed results viewable to: All, participants: 43


This suggestion:

View Answers

Should be implemented as-is.
6 (14.0%)

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

Shouldn't be implemented.
6 (14.0%)

(I have no opinion)
31 (72.1%)

(Other: please comment)
0 (0.0%)

eleanorjane: The one, the only, Harley Quinn. (Default)
[personal profile] eleanorjane

Title:
User tag should allow Twitter as an option

Area:
DW-specific HTML Markup

Summary:
The user DW tag will work with a number of external sites, mostly LJ-based sites, plus AO3. Given the popularity of Twitter we could add Twitter to the list, with a service-appropriate icon.

Description:
A lot of fans use Twitter, and at least some of us would find it pleasing to be able to link to our Twitter accounts the way we do to our AO3/LJ/DJ/IJ accounts, with the matching service icon and so on.

The advantage of this is visual consistency, especially for posts with a laundry list of "here's how to contact me" options. I can't think of any particular drawbacks, other than perhaps a small additional load on the server by adding another icon that has to be served whenever twitter accounts are linked in this way.

Poll #5129 User tag should allow Twitter as an option
Open to: Registered Users, detailed results viewable to: All, participants: 68


This suggestion:

View Answers

Should be implemented as-is.
47 (69.1%)

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

Shouldn't be implemented.
1 (1.5%)

(I have no opinion)
20 (29.4%)

(Other: please comment)
0 (0.0%)

eosrose: (Default)
[personal profile] eosrose

Title:
Crossposting between a community on DW and a personal journal on another LJ-based platform

Area:
crossposting

Summary:
A previous suggestion asked that crossposting be enabled between a personal journal and a community that are both on Dreamwidth. I would ask that we be able to post an entry on a Dreamwidth community and crosspost that entry to the personal journal(s) we've enabled crossposting access to.

Description:
Part of moving house is finding new and better ways of posting entries. Because I can only afford one paid account over on LiveJournal and the ads frustrate me too much to bother with unpaid accounts, I've been posting creative works and personal commentaries to the same journal--but here on Dreamwidth ads are not a problem. I would like to post some entries to a personal journal and some entries to a closed community where appropriate. Doing so at present, however, means I would lose the crossposting functionality that I so love over here at Dreamwidth. I therefore propose that the current crossposting option be enabled even when we are posting to a community rather than to a personal journal. Perhaps this could be a paid feature? This would be something I would certainly buy into!

Potential problem:
-importing from the journal you've been crossposting to may mean importing entries you don't want on your personal journal over here on DW

Additional thoughts:
-enabling crossposting between a DW community and a LJ community that your registered crossposting account has posting privileges for might also be good somewhere down the road, but right now it seems that the ability to crosspost between a DW community and a personal journal on another service would be a lot easier to set into place.

Poll #3687 Crossposting between a community on DW and a personal journal on another LJ-based platform
Open to: Registered Users, detailed results viewable to: All, participants: 27


This suggestion:

View Answers

Should be implemented as-is.
10 (37.0%)

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

Shouldn't be implemented.
3 (11.1%)

(I have no opinion)
14 (51.9%)

(Other: please comment)
0 (0.0%)

thorfinn: <user name="seedy_girl"> and <user name="thorfinn"> (Default)
[personal profile] thorfinn

Title:
Crosspost to Facebook Notes

Area:
crossposting

Summary:
The crossposter sites option should have an option to "push" notes into facebook.com.

Description:
Facebook.com currently has a Notes feature. You can point it at a public RSS feed to import notes, but that fails to re-import edited notes.

I would prefer to "push" notes into facebook via the crossposter, so that edited notes show up correctly etc.

That may or may not be technically possible to do with facebook's note posting. I suspect it would require some reverse engineering of facebook page code etc.

There are complications around posting security - facebook does actually have the concept of custom posting security, and an extra "friends of friends" level.

Also I'm pretty sure there's no way to prevent comments on a note within facebook, so this option may be problematic.

Poll #3653 Crosspost to Facebook Notes
Open to: Registered Users, detailed results viewable to: All, participants: 53


This suggestion:

View Answers

Should be implemented as-is.
14 (26.4%)

Should be implemented with changes. (please comment)
2 (3.8%)

Shouldn't be implemented.
20 (37.7%)

(I have no opinion)
17 (32.1%)

(Other: please comment)
0 (0.0%)

matgb: Artwork of 19th century upper class anarchist, text: MatGB (Default)
[personal profile] matgb

Title:
Allow XFN relationships to be defined in Links List

Area:
Styles

Summary:
Allow for XFN relationships to be defined, so that other sites and services can detect your relationship to an outgoing link in the links list.

Description:
The XHTML Friends Network is used by a number of services, including Google Profile, to know if you are related to an outgoing link. http://gmpg.org/xfn/

Many users put links to personal friends and their profiles on other sites in the links list. Allowing those that wish to define XFN relationships to outgoing links would help interoperability in a user friendly manner.

This could possibly be linked to FOAF, which we already support and has a similar objective?

Poll #3477 Allow XFN relationships to be defined in Links List
Open to: Registered Users, detailed results viewable to: All, participants: 24


This suggestion:

View Answers

Should be implemented as-is.
4 (16.7%)

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

Shouldn't be implemented.
1 (4.2%)

(I have no opinion)
19 (79.2%)

(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%)

jjhunter: Watercolor of daisy with blue dots zooming around it like Bohr model electrons (Default)
[personal profile] jjhunter

Title:
Feed Ghost Comments

Area:
Feeds

Summary:
Ability to read grayed out/'ghosted' comments from original post via corresponding DW feed post.

Description:
One drawback to using feeds on DW to track posters on other sites is the additional energy barrier to reading the whole conversation, i.e. the comments. If 'ghosts' of public comments on the original post could be imported to the corresponding DW feed, one would be much more likely to participate in the conversation, i.e. go post a comment at the original.

By comment 'ghosts,' I mean comments visually/audibly presented as non-interactive and non-native to DW. Visually, this could be indicated by faded, greyscale reproductions of the original comments, moving icons/in-text graphics 'frozen,' etc.

Possible complications: Ethics/privacy issues would probably require permission from original poster. Perhaps link an automatic permission request to creation of DW feed?

Tools in the same family: comment importing (e.g. when importing journals), accepting x-posts from other sites

A parallel possibility: set up a comment counter for each feed post that counts the comments on the original post. This at least raises awareness about conversations one might be missing.

Poll #2558 Feed Ghost Comments
Open to: Registered Users, detailed results viewable to: All, participants: 35


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
2 (5.7%)

Shouldn't be implemented.
24 (68.6%)

(I have no opinion)
6 (17.1%)

(Other: please comment)
1 (2.9%)

jjhunter: Watercolor of daisy with blue dots zooming around it like Bohr model electrons (Default)
[personal profile] jjhunter

Title:
Feed Comment Exporter

Area:
Feeds

Summary:
Ability to export one's comment on a feed directly to the original without leaving DW. Co-develop with 'Feed Ghost Comments'?

Description:
One drawback to using feeds on DW to track posters on sites such as LiveJournal is the activation energy required to go comment on the original post. An option to export (not cross-post) one's comment on the DW feed to the original would increase the overall response rate to that original post.

Possible complications: if it isn't possible to view the comments on the original post through the DW feed, this would give a negative incentive to disregard the /comment/ context into which one is commenting. See suggestion 'Feed Ghost Comments' for possible fix.

Tools in the same family: x-posting (could use variant to export comment & 'post' it under one's username on that other site); comment importing when moving journals.

Poll #2557 Feed Comment Exporter
Open to: Registered Users, detailed results viewable to: All, participants: 30


This suggestion:

View Answers

Should be implemented as-is.
3 (10.0%)

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

Shouldn't be implemented.
19 (63.3%)

(I have no opinion)
8 (26.7%)

(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:
usernames from other sites with different file structures

Area:
user tags, playing well with others

Summary:
Make it possible to add specific external sites with different file structures as recognized entities and make their users linkable with <user name="" site="">

Description:
So not all external social sites are structured site.tld/users/username. Some of those that aren't are even used by Dreamwidth users. Take Ravelry, where that structure is http://ravelry.com/people/username

Obviously, Dreamwidth won't be able to recognize all the possible social media sites out there, but it would be nice to be able to do this at need, and would be nice to do it for reasonably stable, popular sites where Dreamwidth users have profiles of their own, or friends, or both. (Take Ravelry...)

If this happened, there should of course be an interface for whoever gets stuck managing this (probably staff and senior Support) to easily manage it.

Poll #2452 usernames from other sites with different file structures
Open to: Registered Users, detailed results viewable to: All, participants: 61


This suggestion:

View Answers

Should be implemented as-is.
44 (72.1%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
12 (19.7%)

(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:
Recognize AO3 Links

Area:
user tags, playing well with others

Summary:
Add archiveofourown.org as a recognized remote site with its own user-icon.

Description:
On my reading list today, I noticed a number of people (starting, I believe, with helens78) discovering that our offsite user link, without tweaking, works with archiveofourown.org's site structure, even though they're not working off the same root open source project.

Since it works already, why not inquire with them and see what small icon they would prefer for linking to their users? (Their favicon, http://archiveofourown.org/favicon.ico , might work if they don't have a preference otherwise.)

Poll #2451 Recognize AO3 Links
Open to: Registered Users, detailed results viewable to: All, participants: 72


This suggestion:

View Answers

Should be implemented as-is.
50 (69.4%)

Should be implemented with changes. (please comment)
14 (19.4%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
8 (11.1%)

(Other: please comment)
0 (0.0%)

charmian: a snowy owl (Default)
[personal profile] charmian

Title:
Posting Via Metaweblog API

Area:
External Services

Summary:
Dreamwidth does not currently support the MetaWeblog API. If it did, users could easily post to DW using external services, such as Delicious and Posterous.

Description:
The Blog Posting function of Delicious is not compatible with DW (or with LJ, for that matter) and thus users wishing to post digests of their Delicious links must use an external script to be able to post digests to their Dreamwidth journals.

It seems (from what I have learned in conversations with people better versed in these issues than me) that if the MetaWeblog API were implemented on Dreamwidth, people wouldn't have to use such scripts anymore.

Poll #2448 Posting Via Metaweblog API
Open to: Registered Users, detailed results viewable to: All, participants: 53


This suggestion:

View Answers

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

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

Shouldn't be implemented.
5 (9.4%)

(I have no opinion)
12 (22.6%)

(Other: please comment)
0 (0.0%)

acb: (Default)
[personal profile] acb

Title:
Crossposting of non-public items to Facebook

Area:
crossposting

Summary:
A means of posting one's own posts which are not open to the public to Facebook. Since one's Facebook feed is by default open only to one's own FB friends (and they're now adding LJ-style subgroup permissions) it's quite conceivable that one would want to share one's posts with authenticated DW/LJ friends and authenticated FB friends but not the general public.

Description:
One possible implementation would involve users linking their Dreamwidth account with a Facebook account (using Facebook Connect) and adding a tag (say, 'facebook' or 'fb_xpost' or 'xpost:fb') to posts they wish to have crossposted to their Facebook account. When the item is posted, at about the same time that LiveJournal crossposting is being handled, DW would crosspost the item to the user's Facebook.

The point would be to allow the item to be seen by the user's trusted Facebook friends without them having to obtain a Dreamwidth account. There would be two ways to implement this: the easiest would involve posting the post to Facebook's own note facility and keeping it on Facebook, effectively letting go of it. Thus people on Facebook would read/comment on the note, and people on DW would read/comment on the DW post. The facility could have a user-configurable option to put a link to the original at the bottom.

A more complex way would involve integration between Dreamwidth and Facebook's API. A Facebook interface would be effectively a Facebook application (albeit one running as an external Facebook Connect app), and would be able to see a connected user's Facebook UID and check whether they are connected to another user. This could be used to either:
a) have an interface tht runs within Facebook and presents the text of Dreamwidth posts, with comments, if the Facebook user is authorised to see them, or
b) integrating Facebook Connect users into the Dreamwidth user identity system (which allows OpenID users, so there is precedent for external users), and allows them to view posts and comment using their Facebook credentials.

IMHO, a system which integrates Facebook users with DW users in one of these two ways would be better for connecting one's various friend circles together.

Poll #1838 Crossposting of non-public items to Facebook
Open to: Registered Users, detailed results viewable to: All, participants: 42


This suggestion:

View Answers

Should be implemented as-is.
7 (16.7%)

Should be implemented with changes. (please comment)
3 (7.1%)

Shouldn't be implemented.
13 (31.0%)

(I have no opinion)
19 (45.2%)

(Other: please comment)
0 (0.0%)

beet: a beet (Default)
[personal profile] beet

Title:
Importing multi-journal posts into a single community.

Area:
Personal journal and community importing

Summary:
Allow users to import posts from one or more personal journals and/or single-poster LJ communities to a single, unified DW community.

Description:
I was a noob. It's true. And I'd love to use Dreamwidth to clean up my mess.

When I started playing with art at LJ, I posted to my personal journal. At the point I decided I wanted to have more adult themes and that it would be responsible to f-lock them down at some point, I realized that I didn't want my personal journal f-list to be synonymous with the list of people who could see my art. So, (stupidly) I started a separate personal journal for my art. And then, when I realized what a pain in the ass it was to have to constantly log in and out, so I created yet another place for my art--a single-poster community.

I have art and comments across all three places and would really, really love to correct my noob mistakes and be able to import them all into one journal on DW. I imagine I am not the only person with (at least some of) these issues.

I know that there have been discussions on various parts of this issue, but I am not sure where things have gone. I see in the FAQ that there are currently no plans for community importing, even for importing single-poster communities.

For that reason, I want to reiterate how very much I would like to see this kind of functionality added to Dreamwidth. I know that importing communities is a contentious issue. Nevertheless, I hope that you continue to work on finding a way to make this happen.

Poll #1774 Importing multi-journal posts into a single community.
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)
2 (7.7%)

Shouldn't be implemented.
1 (3.8%)

(I have no opinion)
7 (26.9%)

(Other: please comment)
1 (3.8%)

altivo: The Clydesdale Librarian (Default)
[personal profile] altivo

Title:
Blogging photos from Flickr.com

Area:
external/client posting

Summary:
Flickr has no support for posting photos to Dreamwidth, even though they do post successfully to Livejournal. Can we encourage them to add Dreamwidth support?

Description:
Flickr has a feature that allows a user to post a photo from a Flickr photostream to blogs on Blogger, Livejournal, etc. Since they work well with LJ, it seems they ought to be able to work with Dreamwidth, but so far no luck. A query sent to their help staff just gets the response that they "do not support Dreamwidth." Can you perhaps encourage them to do so? Surely it wouldn't be that difficult for them.

Poll #1592 Blogging photos from Flickr.com
Open to: Registered Users, detailed results viewable to: All, participants: 23


This suggestion:

View Answers

Should be implemented as-is.
12 (52.2%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
9 (39.1%)

(Other: please comment)
2 (8.7%)

cimorene: A black-and-white vintage photograph of 1920s singer Helen Kane in profile, with a dubious, side-eye expression (Default)
[personal profile] cimorene

Title:
Make comment count & link for crossposted entries reciprocal

Area:
interoperability, entries

Summary:
Place a link (with comment count) at the bottom of the original DW entry to its crossposted mirror.

Description:
Right now we have the option to include a link back to the original DW entry on crossposted versions of it, displaying the number of comments at the original entry. Any readers of the mirror journal will know if they are missing any discussion at DW, but DW readers don't currently know if they are missing part of the discussion at the mirror location.

I'd like to be able to generate a copy of that notice/comment count that would include the address of the cross-posted entry and a comment count for it, and place it on the original DW version of the entry so that both copies would link to each other.

Drawbacks:

If the same entry is crossposted to more than 1 other site, the number of links could eventually start to become unwieldy.

It would require another step after completed crossposting to modify the original entry on DW with the link.

Poll #1575 Make comment count & link for crossposted entries reciprocal
Open to: Registered Users, detailed results viewable to: All, participants: 46


This suggestion:

View Answers

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

Should be implemented with changes. (please comment)
6 (13.0%)

Shouldn't be implemented.
5 (10.9%)

(I have no opinion)
7 (15.2%)

(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