Difference between revisions of "Posting Wishlist"
From Dreamwidth Notes
Vassilissa (Talk | contribs) |
Vassilissa (Talk | contribs) |
||
Line 64: | Line 64: | ||
* allow the user to turn off autocomplete in the tags field http://community.livejournal.com/suggestions/787356.html | * allow the user to turn off autocomplete in the tags field http://community.livejournal.com/suggestions/787356.html | ||
+ | |||
+ | * http://community.livejournal.com/suggestions/788037.html When auto-saving a post on the server (in case the browser crashes, etc.) DW to save all the post parameters, not just the text of the post |
Revision as of 14:08, 31 March 2009
- http://community.livejournal.com/suggestions/884432.html - Give Rich Text Mode a ‘remove LJ-cut’ button, as the current editor makes it nearly impossible to move LJ-cuts without completely messing up an entry.
- http://community.livejournal.com/suggestions/883830.html - Let poll creators make questions that allow a creator-defined number of options to be selected, instead of the current limit-to-one-or-don’t-limit-at-all options. This would ideally include the ability to require a maximum number of answers, a minimum number of answers, or a fixed number of answers (e.g., no more than three, at least three, exactly three).
- http://community.livejournal.com/suggestions/911599.html - This is a request to add a customizable field to the Mood/Music/Location area of the post. Usage example - Number of Words in NaNoWriMo: 17,596.
- http://community.livejournal.com/suggestions/880379.html -- adding link to a page of the LJ-specific/LJ-accepted HTML to the static header and footer. Useful counter-suggestions in comments include making a unified FAQ with this information that is linked solely on the Post an Entry page, with a mouseover tag indicating why it's of import.
- http://community.livejournal.com/suggestions/902330.html - add basic HTML "cheatsheet" to the HTML Editor page, whether clickable-to or visible on the page. Original suggestion was shredded to bits by people fearful of the HTML Editor turning into the ever-broken RTE.
- http://community.livejournal.com/suggestions/904345.html - add a "now" button/link in the entry editor to update the time listed in the time slot. Supported by people who take longer to compose entries and want the entry time to reflect the time of posting rather than "the time I loaded the 'Update Journal' page."
- http://community.livejournal.com/suggestions/848793.html - Users should have the ability to Recommend and maybe also Pan, posts and comments. "Panning" nearly universally derided, but perhaps some mileage in a Digg/[this is good]-style "I like this post"? Google Reader also has a "cool" recommendations aggregator: http://www.google.com/reader/shared/user/15650323335570657892/label/cool
- http://community.livejournal.com/suggestions/849937.html - Posts which already have a cut tag should not be completely hidden if they are marked as having adult concepts or content; instead, they should be rendered as normal, with the warning page appearing between the cut and the full post. Some concern about potential abuse, but definite agreement that the adult warning pages are inelegant.
- http://community.livejournal.com/suggestions/855934.html - I would like the time the entry was updated to be when the entry actually posts rather than when I first open the post page. General consensus that a button to "update to current time" would be better: see http://community.livejournal.com/suggestions/904345.html
- It would be really nice if this could be a user-set preference, so that users could have either at-posting or at-loading without one or the other having to click an extra button every time. branchandroot
- Maybe a checkbox, which remembers the last set value? Afuna 01:33, 13 February 2009 (UTC)
- Perhaps the way to do it that would be cleanest from a user perspective would be to set it up to automatically be assigned a timestamp of the time at which it was actually posted, according to the user's chosen time zone, rather than LJ's behavior of reading from the computer clock. I don't think people will want to lose the option to specify a different date/time, so for them we could have a "change timestamp" button on the Post Entry and Edit Entry forms. The form could just not have date and time fields until someone clicks that button - similar to the way "date out of order" currently works. Maura 20:48, 21 February 2009 (UTC)
- http://community.livejournal.com/suggestions/851162.html - Simply expand the 'Current Music' field into separate 'Artist' and 'Track' (and perhaps 'Album') fields so that users can gather and integrate the differential values in their LiveJournaling. General response: meh. :)
- http://community.livejournal.com/suggestions/840636.html - Make Browse button for userpics appear for the full comment page (?mode=reply) the same way it does for quick reply.
- http://community.livejournal.com/suggestions/843045.html - Add quote button to quick reply.
- http://community.livejournal.com/suggestions/820859.html - Add one-click preview for quickreply
- http://community.livejournal.com/suggestions/821199.html - Add rich text editor for comments (consensus seems to be that font size and font color should not be among the rich-text-editing options, though)
- http://community.livejournal.com/suggestions/819871.html - Autosave when editing as well as when posting an entry (instead of only when posting)
- http://community.livejournal.com/suggestions/823239.html - Offer per-user custom spellcheck dictionaries
- Add a word counter that tracks how many word have been written in a post - and possibly also a character counter for tags and subject line. It would be useful to see if you'll hit a particular word/character limit.
- Post Revisions similar to Wordpress - http://support.wordpress.com/posts/post-revisions/. Backup the last x revisions, whether auto-saved or otherwise, of a post and have the ability to compare and revert to an earlier version. I would add that I would like to see the first version of a post to be saved as a backup option for comparing and reverting.
-
http://community.livejournal.com/suggestions/814051.html - Let journal owners see what filter a post of theirs is on - it was implemented so that journal owners could see that a post was filtered rather than just normally locked, but not to show what filter the post is using.
- Hasn't this already been done? branchandroot
- Yes, posts now display different icons for Custom than for FO, and list the custom groups. Maura
- http://community.livejournal.com/suggestions/832501.html -- Download raw results of polls; there are privacy issues involved here, but the overall sentiment was that users wanted to be able to manipulate the data based on other factors, like respondent age, etc. Zilla 28
- http://community.livejournal.com/suggestions/831270.html -- Allow inserting narrative or descriptive text between poll questions, e.g. for sub-headings or text common to several consecutive questions.
- http://community.livejournal.com/suggestions/896058.html -- HTML Editor as default entry editor for new users, rather than the Rich Text Editor.
- http://community.livejournal.com/suggestions/896355.html -- Add the poster's chosen timezone to the timestamp on entries
- http://community.livejournal.com/suggestions/913700.html -- Allow a) change of type of question, and b) editing within the Poll Creator
- Don't require a "date out of order" post to be kept off Friends page. There should still be an option for keeping a post off Friends pages, but why should it be required when backdating?
- When Dreamwidth gets photohosting, make how photos post to your journal (centered, text cleared or not, etc.) an end user option
- http://community.livejournal.com/suggestions/780235.html Allow adding a poll to an already created post
- insert a message warning users that they're about to post to a community (opt-out) http://community.livejournal.com/suggestions/780556.html
- allow the user to turn off autocomplete in the tags field http://community.livejournal.com/suggestions/787356.html
- http://community.livejournal.com/suggestions/788037.html When auto-saving a post on the server (in case the browser crashes, etc.) DW to save all the post parameters, not just the text of the post