From LJ Suggestions
Everything from 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 suggestions that have already been mined for useful suggestions:
- None yet.
- November '08 - ursamajor - in progress
- October '08 - principia_coh - in progress
- September '08 - Magycmyste - in progress
- Community Wishlist
- Syndication Wishlist
- Watching Wishlist
- Trusting Wishlist
- Friending Wishlist
- OpenID Wishlist
- Intersite Wishlist
- Interface Wishlist
- Multimedia Wishlist
- Posting Wishlist
- Commenting Wishlist
- Data Management Wishlist
- Themes Wishlist
- Support Wishlist
- Installation Wishlist
- Client Wishlist
Contents
Memories
- http://community.livejournal.com/suggestions/348380.html -- Option at time of entry creation to instantly make entry a memory.
This would be fairly easy to implement if actually wanted.
- http://community.livejournal.com/suggestions/349056.html -- Export memories by category (needs work to avoid huge hit).
- http://community.livejournal.com/suggestions/380025.html -- Indicate in archive view (or other places too?) if entry has been added as a memory (by me) (maybe public memory by others too).
- 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/887768.html - mark PMs as read after they've been replied to in the Inbox
- 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?
http://community.livejournal.com/suggestions/890016.html - refresh message count in headers when deleting messages in inbox (only on the page where the messages were deleted from, not cross-tab or cross-window)
http://community.livejournal.com/suggestions/890470.html - need a better process for spam removal - fewer clicks, able to remove in bulk.
http://community.livejournal.com/suggestions/890784.html = allow unformatted links in the inbox to be clickable.
Styles
- http://community.livejournal.com/suggestions/356270.html -- Error pages (bad dates, etc) for journals are served in the journal style, not site scheme. Related to some general points made in http://community.livejournal.com/suggestions/889338.html - "when there are error pages, make them useful ones" so people can move forward logically, instead of going back in confusion. Error pages being served in "journal style" often means basic black text on white with no links whatsoever.
- http://community.livejournal.com/suggestions/892064.html - return error when custom CSS is too long. Makes sense, ja?
- http://community.livejournal.com/suggestions/893189.html - add free text areas to all styles. In general, I think the aim is for styles to have as many of these features occur across all styles?
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.
- http://community.livejournal.com/suggestions/356886.html -- Show stats on userpics use (most frequently used) (shinier would be most frequently used over time).
Accounts
- http://community.livejournal.com/suggestions/882451.html -- add Twitter profile to profile page. Counter-suggestion to just make free-form fields for entering that sort of info available. (We actually want to revise that entirely, to an extent -- see zilla 23.)
- http://community.livejournal.com/suggestions/373322.html -- multiple login manager tool, DW-side.
Account Creation
- http://community.livejournal.com/suggestions/362229.html -- Confirm username before creating account (I might implement by displaying the username and email address before creating rather than asking for confirmation of account name).
Account Deletion
- http://community.livejournal.com/suggestions/365315.html -- Optional message from deleting user to display on deleted journal (until purged).
Communities: Community Maintenance/Moderation
- http://community.livejournal.com/suggestions/883325.html -- Let community maintainers create a boilerplate message unique to their community that will display when someone tries to join their community.
- http://community.livejournal.com/suggestions/881865.html -- Expand number of comments viewable in 'Latest Received' area to ease handling of comments in very active communities. Specific number given was 500, broken down in pages of 50.
- http://community.livejournal.com/suggestions/376934.html -- Screen entry until fixed by original poster.
- http://community.livejournal.com/suggestions/891068.html - "Pending Membership Requests" modification request: be able to bulk approve, reject, and reject+ban from the same page with one click.
- http://community.livejournal.com/suggestions/892471.html - Add "notes" section for maints/mods. Could be achieved several ways - additional fields on /manage/banusers.bml (for each displayed user, show: user, date/time of banning; in comms, show who did banning and allow notes field for); allow private posts to comm which would only be visible to maints/mods?
- http://community.livejournal.com/suggestions/896930.html - community userpic selection. this one confuses me, and users are confused and mongoosey about it.
External Services
Moods
- http://community.livejournal.com/suggestions/380573.html -- Moods can show intensity via color modification (probably not suitable for all mood themes)
- http://community.livejournal.com/suggestions/384894.html -- paid mood themes
Site Schemes
- http://community.livejournal.com/suggestions/864581.html -- add "find:" search to Lynx, omg why was this not done back in 2003?
Support
- http://community.livejournal.com/suggestions/882211.html -- enable sorting of Support requests by ones that have no response yet. Counter-suggestions include letting a volunteer tag a request as one they don't want to look at again (e.g., if it's one they know has been answered adequately).
- http://community.livejournal.com/suggestions/882065.html -- enable sorting of Support requests by ones you haven't touched. Also, enable sorting of green support requests by ones you have or haven't touched.
- http://community.livejournal.com/suggestions/362810.html -- link to FAQs about certain error messages with those error messages
Suggestions
- http://community.livejournal.com/suggestions/892296.html - Ability to preview (and then edit) a suggestion during the submissions process. Enthusiastically supported.
Statistics
- http://community.livejournal.com/suggestions/377309.html -- Extended site statistics.
Search
- http://community.livejournal.com/suggestions/419057.html -- Search for users with PGP keys
Et cetera
- http://community.livejournal.com/suggestions/386309.html -- redirect www.usersub.example.com to usersub.example.com so fewer people need to be fish-slapped.
- http://community.livejournal.com/suggestions/879620.html?thread=13611524#t13611524 -- friendbot preventative measure proposed by commenter: force completion of captcha for each additional friend an account adds after a certain number of friends are added in a certain amount of time.