naughty_or_ice: (Default)
[personal profile] naughty_or_ice

Title:
Icon Downloads

Area:
icons

Summary:
Ability to download all current icons on your journal (active or inactive).

Description:
I know that I'm not the only one that sometimes looks at their long list of icons after some kind of computer failure, and wants to back them up on the new machine. Or maybe they were linked by a url and you forgot to save them. Maybe you stopped having a paid account, but want to be able to reupload them with ease after you get a chance to pay for the account again (Submitting another suggestion on this topic as well).

I think it would be very helpful if there were some option that would let you batch save the image files currently on your account, preferably with the keyword or description as the name. Compression has improved and should allow users to download a backup of their icons in a zip file they can unpack on their computer.

In addition and/or alternatively, perhaps there is some way to make a metadata file that would take less room than the icons, but contain the information about them and their keywords and descriptions, or a file that can be added to the zip folder that contains this information to make the re-upload of icons easier.

Poll #18020 Icon Downloads
Open to: Registered Users, detailed results viewable to: All, participants: 41


This suggestion:

View Answers

Should be implemented as-is.
29 (70.7%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (26.8%)

(Other: please comment)
0 (0.0%)

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

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

Title:
Full Export Tool

Area:
exporting, interoperability, backups

Summary:
Create an interface/client with an easy way of setting up and later downloading a full backup of one's journal. This would be in a file format of one's choice, with entries, comments, icons, memories, and all.

Description:
Currently, one can back up one's journal through a scattering of mostly-legacy interfaces in different places. There are tools that were never exactly designed to work with Dreamwidth, such as LJ Archive. (While some of them work even most of the time, there are times that they do not, and I suspect Dreamwidth developers may not necessarily prioritize jumping in to third-party client code developed for another site, assuming the code is even open and available to be jumped into.)

There already exists a bug requesting a PDF export of one's journal: http://bugs.dwscoalition.org/show_bug.cgi?id=32

This would broaden the scope of the ability to export, so one could choose between, say, .pdf, HTML, plain text, rich text, comma separated values, tab separated values, and perhaps other formats (WordPress-friendly?) as developers see the need.

One could go to a page similar to the current import journal page, and select the date range (as for the existing spec for .pdf, whole journal or month by month), elements and file type that one wished to back up, and queue a download request. The system would queue the download request, and prepare it in a timely fashion, as other load allowed so as to keep things readable in other journals on the same cluster. (Paid users might be given priority in the queue, if there was a queue worth mentioning.) Similar to the importer, the page would show progress of the export file preparation when revisited, and offer a low-impact refresh option, because you just know that people are going to want to sit there and beam at the progress the first couple times they download. Once the files were prepared, in reasonable-sized chunks for downloading if it were a particularly large journal *cough*azurelunatic*cough*, a notification would be sent with a link to the download page, so the user would not have to sit on the page refreshing if they did not want to. There might also be a password challenge before downloading, to diminish the possibility that someone's theoretical nosy little brother could copy one's whole journal to a USB drive in an unguarded minute alone with the computer.


In addition to the web interface, there should also be an API that allows (at minimum) the same choices as the web interface, complete with full documentation. Perhaps there could even be official clients for a range of different platforms.

Poll #4293 Full Export Tool
Open to: Registered Users, detailed results viewable to: All, participants: 64


This suggestion:

View Answers

Should be implemented as-is.
53 (82.8%)

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
1 (1.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 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%)

zvi: self-portrait: short, fat, black dyke in bunny slippers (Default)
[personal profile] zvi

Title:
OPML file should special case feeds accounts

Area:
third party site integration

Summary:
The current OPML file includes the DW RSS address (http://example_feed.dreamwidth.org/data/rss) for feed accounts. This is ridiculous. It should give you the RSS feed that DW subscribes to, instead. (http://examplersswebsite.com/example.rss)

Description:
An OPML file is a bit like an address book, it lets you take the subscriptions from one feed reader (in this case, the reading page) and put it into a different feed reader. As if you have one of those 7 ring binder planners, only you got one in black plastic and now you have the opportunity to buy one in blue plastic, so you want to move your addresses with you into the new container.

The way the OPML file works now, if you have a feed account on your reading page, it pulls the DW url, instead of the originating site's feed. So, in your new feed reader, you'll always be reading at a serious delay, because your waiting first for DW to contact the originating site and download an update, and then for your feed reader to contact DW and get the update that DW has gotten. [personal profile] rho corrects me that the DW rss URL is just a redirect to the originating site, so the delay is not very long.

There's no real benefit to DW in remaining the middleman in this transaction, and it's better for end users if they butt out.

Poll #1381 OPML file should special case feeds accounts
Open to: Registered Users, detailed results viewable to: All, participants: 28


This suggestion:

View Answers

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

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

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (21.4%)

(Other: please comment)
0 (0.0%)

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

Title:
Get notified of your own posts

Area:
notifications, entries

Summary:
Option to get email notifications of your own posts, or your posts with a certain tag, in the same way as you can track other people.

Description:
You can get notified of someone else's posts by going to http://www.dreamwidth.org/manage/subscriptions/user?journal=exampleusername. However, doing that for your own name redirects to http://www.dreamwidth.org/manage/settings/?cat=notifications. I'd like to be able to get email copies of my own entries, like I can with my own comments. (This would probably be a paid feature for the same reasons.)

Poll #1197 Get notified of your own posts
Open to: Registered Users, detailed results viewable to: All, participants: 33


This suggestion:

View Answers

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

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

Shouldn't be implemented.
1 (3.0%)

(I have no opinion)
24 (72.7%)

(Other: please comment)
0 (0.0%)

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

Title:
Export memories

Area:
memories

Summary:
I know there is a plan to overhaul memories eventually. However, in the meantime, it would be useful to be able to backup exisiting memories.

Description:
I imagine a feature to be able to export all your memories into some kind of useful format, either a CSV that you can download, or even into a private links post in your journal. The idea is so that all your existing memories can be saved in some way before memories are overhauled.

Poll #984 Export memories
Open to: Registered Users, detailed results viewable to: All, participants: 34


This suggestion:

View Answers

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

Should be implemented with changes.
9 (26.5%)

Shouldn't be implemented.
1 (2.9%)

(I have no opinion)
5 (14.7%)

(Other: please comment)
1 (2.9%)

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