Difference between revisions of "Uncategorized Wishlist"

From Dreamwidth Notes
Jump to: navigation, search
 
Line 96: Line 96:
  
 
* http://community.livejournal.com/suggestions/917740.html - make deleted entries show a proper 404 for Google caching purposes (assumes 404 page has been made suitably friendly)
 
* http://community.livejournal.com/suggestions/917740.html - make deleted entries show a proper 404 for Google caching purposes (assumes 404 page has been made suitably friendly)
 
* http://community.livejournal.com/suggestions/919035.html - when requesting to join a moderated community, have subscribing to the community as an option at that time
 
  
 
* http://community.livejournal.com/suggestions/919199.html - clarify error messages when posts are bounced from the moderation queue of a community
 
* http://community.livejournal.com/suggestions/919199.html - clarify error messages when posts are bounced from the moderation queue of a community
Line 110: Line 108:
  
 
* http://community.livejournal.com/suggestions/922774.html - allow creation of public tags without having to create an entry
 
* http://community.livejournal.com/suggestions/922774.html - allow creation of public tags without having to create an entry
 
* http://community.livejournal.com/suggestions/924381.html - different subject lines for different types of moderated submission notification
 
  
 
* http://community.livejournal.com/suggestions/926065.html - trash can for the inbox to rescue accidentally deleted messages
 
* http://community.livejournal.com/suggestions/926065.html - trash can for the inbox to rescue accidentally deleted messages
Line 138: Line 134:
  
 
* http://community.livejournal.com/suggestions/938202.html - option to view all entries that have no tags
 
* http://community.livejournal.com/suggestions/938202.html - option to view all entries that have no tags
 
* http://community.livejournal.com/suggestions/938284.html - easy way for comm maintainers to view when members' journals were last updated
 
  
 
* http://community.livejournal.com/suggestions/938950.html - hide long URLs so they don't break reading pages, or fix the styles so they don't break
 
* http://community.livejournal.com/suggestions/938950.html - hide long URLs so they don't break reading pages, or fix the styles so they don't break
Line 148: Line 142:
  
 
* http://community.livejournal.com/suggestions/938685.html - be able to request an email summary of post-by-email commands
 
* http://community.livejournal.com/suggestions/938685.html - be able to request an email summary of post-by-email commands
 
* http://community.livejournal.com/suggestions/941710.html - be able to view raw HTML of entries in a moderation queue
 
  
 
* http://community.livejournal.com/suggestions/940952.html - ability to search by site & user from the home page when not logged in
 
* http://community.livejournal.com/suggestions/940952.html - ability to search by site & user from the home page when not logged in
  
 
* http://community.livejournal.com/suggestions/942055.html - support OAuth, which allows you to give access securely to other services without giving them your password
 
* http://community.livejournal.com/suggestions/942055.html - support OAuth, which allows you to give access securely to other services without giving them your password
 
* http://community.livejournal.com/suggestions/942399.html - moderated posting in communities for specific users
 
  
 
* http://community.livejournal.com/suggestions/943853.html - Links on Recent Comments page to parent comments and threads
 
* http://community.livejournal.com/suggestions/943853.html - Links on Recent Comments page to parent comments and threads
  
 
* http://community.livejournal.com/suggestions/943919.html - Include FAQ numbers in reference FAQ drop-down in support
 
* http://community.livejournal.com/suggestions/943919.html - Include FAQ numbers in reference FAQ drop-down in support
 
* http://community.livejournal.com/suggestions/945021.html - Allow deleting the email address associated with a community
 
 
* http://community.livejournal.com/suggestions/945449.html - Various suggestions for compulsory tags or default tags or moderating untagged entries
 
  
 
* http://community.livejournal.com/suggestions/946172.html - More possible moods, option to add your own
 
* http://community.livejournal.com/suggestions/946172.html - More possible moods, option to add your own
Line 174: Line 160:
  
 
* http://community.livejournal.com/suggestions/950336.html - add account creation date to FOAF page, for research bots
 
* http://community.livejournal.com/suggestions/950336.html - add account creation date to FOAF page, for research bots
 
* http://community.livejournal.com/suggestions/950533.html - view last x active entries in a community
 
  
 
* http://community.livejournal.com/suggestions/950942.html - form for requesting syn address edits, so people don't miss out key info
 
* http://community.livejournal.com/suggestions/950942.html - form for requesting syn address edits, so people don't miss out key info
 
* http://community.livejournal.com/suggestions/951212.html - modify membership request emails to have more useful info for moderators
 
  
 
* http://community.livejournal.com/suggestions/951459.html?thread=15338147#t15338147 - add an onbeforeunload handler so partially-written posts are not lost so easily
 
* http://community.livejournal.com/suggestions/951459.html?thread=15338147#t15338147 - add an onbeforeunload handler so partially-written posts are not lost so easily

Latest revision as of 10:58, 21 August 2009

  • http://community.livejournal.com/suggestions/886403.html - The 'send this user a message' feature should also show the IP address, to discourage abuse by trolls. As refined in comments, should behave the same as the IP-address-logging options associated with one’s journal settings (i.e., the message sender would receive a notification that their IP address is being logged before they hit send), and should be able to be set in the same way one can control comments on one's journal.
  • http://community.livejournal.com/suggestions/886081.html - Create a toggleable view option that is imageless for faster and/or more private work/school/public-location reading of LJ/DW. Would strip all userpics, posted images, layout customization, et al, leaving a text-only version of site that could then be easily switched off at the user's discretion, and would not affect their journal's default style/view settings.
Sounds like making the "mobile" sitescheme/etc. easily toggled would satisfy this one. We plan to create it anyway. Rickybuchanan 10:59, 2 February 2009 (UTC)

Some of these are probably categorizable, but I'm not sure where. --Ursamajor 05:15, 10 January 2009 (UTC)

  • http://community.livejournal.com/suggestions/893954.html - Image placeholders. Applies across friends page and entries. Dre (need to find her userpage) points out that on-demand size detection is impractical especially for low-bandwidth readers (and would force images to go through DW's bandwidth for said detection, costing even more money), so the existing implementation of image placeholders is as good as it can be for now; still, upgrading the existing console command for customizing the placeholder size threshold to being in the settings would be lovely.
Major accessibility implications for putting captchas anywhere. Just Say No. Rickybuchanan 10:59, 2 February 2009 (UTC)
different version of the same idea as a greasemonkey script ljwho
  • 'go to next post' and 'go to previous post' when browsing a journal should go to the next / previous post visible to the user. They should not, as on LJ, fail if that post is not visible to you.
  • Expanding on that, it should not be possible to see that there is a post that is not visible to you (or, at best, not without guessing the right URL - make these longer?) via next/previous post or the calendar or...
I believe these last two have already been implemented on LiveJournal. -- Pne 14:41, 9 February 2009 (UTC)
  • An API call that says 'give me all posts and comments visible to me in this (these?) journal since x'. This will greatly help the introduction of offline readers and facilitate continuing discussions.
  • Journal Entry Security update - ability to select specific entries and update the security of those entries only, as opposed to the entire journal, rather than having to mark each one individually. (LJSec sort of already does this, I think).
  • Tag by Access Filter: create a rule where use of a particular access filter automatically tags an entry with a pre-selected tag. For example, if I were doing nano and had decided to create an access filter for it, every time I posted to the Nano access filter, the entry would automagically get a 'National Novel Writing Month' tag.
  • Paid (or Premium Paid) feature: fully encrypted (https) sessions.

I'm really not sure what category to put these in. - Magycmyste

  • http://community.livejournal.com/suggestions/876453.html - list pending schools by country - not sure if adding schools is a feature that we're going to use in Dreamwidth, or if this has been covered, but if so, the suggestion is to have a list of schools pending approval, so someone else from the same school can see that it's pending and doesn't try to add it twice.
  • http://community.livejournal.com/suggestions/914513.html - sort entries by icon keyword, a feature where we can go back and see all the entries that we wrote when using a specific icon. For this suggestion to be useful, it would need to be able to get entries by icon keyword, and be able to tell which keywords there's no longer an icon for, as well as probably grouping keywords by icon (say I've used the icon on this comment 50 times under the St. John's Wort keyword, but 100 times under the sanity keyword; I'd want to know that it was 150 uses total and how many times per keyword).
  • http://community.livejournal.com/suggestions/920595.html - if a screened comment (e.g. from a non-friend) is unscreened then edited, editing it should make it screened again. Similarly, in moderated communities, editing a post that has been approved should have optional safeguards.