Difference between revisions of "From LJ Suggestions"

From Dreamwidth Notes
Jump to: navigation, search
(Site Schemes)
Line 25: Line 25:
 
* [[Installation Wishlist]]
 
* [[Installation Wishlist]]
 
* [[Client Wishlist]]
 
* [[Client Wishlist]]
 +
* [[DWTalk Wishlist]]
  
 
== Memories ==
 
== Memories ==

Revision as of 20:21, 10 January 2009

Everything from [info]suggestions that doesn't totally suck. (IE: anything non-obsolete, non-reactionary, and not related to details of LiveJournal.com's business plan and not LiveJournal-the-service).

(Built over time, la la la, categorize however y'all find appropriate...)

Months from [info]suggestions that have already been mined for useful suggestions:

  • None yet.
  • November '08 - ursamajor - DONE.
  • October '08 - principia_coh - in progress
  • September '08 - Magycmyste - in progress
  • August '08 - ursamajor ([info]ursamajor) - in progress.

Memories

This would be fairly easy to implement if actually wanted.

  • http://community.livejournal.com/suggestions/891542.html - Revamp Memories - "should feel like a cross between delicious and inbox management;" specifically, put categories/keywords on the left and memorified links on the right. Better ability to bulk edit/rename/move between memories cats. Better ability to see/find uncategorized memories. Add the ability to add a note to a memory, a la delicious?

Service-specific markup

  • http://community.livejournal.com/suggestions/350836.html -- List of pre-defined people and/or entities that could be linked to in a way similar to another local-service user, except this would be defined per-journal by the user, for example, <lj cast="mymom">. Link would go to sub-page belonging to user, the space defined for "mymom", where the user could provide all the relevant explanation of the person and/or entity "mymom".

Inbox/ESN/Notifications

  • http://community.livejournal.com/suggestions/889605.html - 1. Don't allow blank PMs to be sent. 2. LJ form completion behavior - should be internally consistent, yes (PM form behavior mirrors Tag form behavior, for example - but should also be consistent with external standard form behavior?

Userpics

  • http://community.livejournal.com/suggestions/881651.html -- Make anchor tags on the 'allpics' page so that when someone clicks on an icon associated with a post or comment for more information it takes you to that specific icon rather than putting you at the top of a page that may have almost 200 icons on it.

Moods

Site Schemes

  • http://community.livejournal.com/suggestions/888650.html - 1. Figure out better way to differentiate between screened and unscreened comments in Lynx. 2. Adjust alt text sensibly for screen/unscreen button - it says "screen" for both "to screen" and "to unscreen;" combined with the above problem, it's hard to know whether you're screening or unscreening a given comment!
  • http://community.livejournal.com/suggestions/888876.html - Text links in lieu of image buttons? Similar issue as above - alt text not changing appropriately when situation changes ((un)screen, (un)freeze). Also, "is Lynx meant to be for mobile browsers? For visually impaired readers?" Make as clean and compact, codewise, as possible.

Error Pages

http://community.livejournal.com/suggestions/889338.html - On the journal pages of purged accounts, link to "rename accounts page." Part of a larger point - non-sitescheme 404s such as journal pages are utterly useless right now. Should we force 404s into sitescheme with contextually appropriate links? For example, going to the profile page of a purged journal is in sitescheme; going to the journal or friends page of a purged journal is not. For ease of use, this needs to be addressed.

http://community.livejournal.com/suggestions/889458.html - On the pages of unregistered usernames, a link to "join DW;" also, links to "create a journal with this name" and "create a community with this name."

Suggestions

  • I don't think there actually is a suggestion in for this yet, but given recent Suggestions deletion drama, users should not be able to delete their top-level Suggestions posts. They should be able to disable receiving notifications from it, yes, but if a suggestion is posted and discussion occurs, even if it is entirely against the proposed suggestion, it is useful to have discussion pointing out all these issues archived to show people "this is why this suggestion is not such a good idea for DW," etc.

Statistics

Search

External Services

Et cetera

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.