Difference between revisions of "Community Wishlist"

Revision as of 14:25, 31 March 2009

See also: Possible paid community features.

Communities: General

• http://community.livejournal.com/suggestions/874305.html - Fix community renaming. Not sure if this should go in Comms or out to a Renaming wishlist; I know there's been call to simplify several things about renaming (such as making it possible to create a brand new journal with a purged username directly), but not sure if it's big enough to get its own Wishlist. In any case, this suggestion received enthusiastic support.

• http://community.livejournal.com/suggestions/881015.html -- enable anonymous posting in communities. Some types of comms have a particular need/wish for this, others very much do not want it as it has high abuse potential. One counter-suggestion to just have people create sockpuppets to preserve their anonymity was rejected as leading to namesquatting; even if accounts are deleted, people still have to pay for renames. Other counter-suggestion, to enable masking of a poster's identity, while still associating the post with an account (viewable by the community mods) was regarded more favorably.

• http://community.livejournal.com/suggestions/855613.html - Purge inactive communities from LJ system. General disagreement to purge all, for archival reasons, but perhaps consider not returning them in top 500 for interests. This may perhaps also be relevant to the "Interest search sux" section. :) Zilla 22

• Posting template for paid comms (suggested by azurelunatic): Like the suggestions template, but available to paid comms to force everyone but someone with maintainer status to go through a template, and to be able to create a template. People could still abuse it, of course, but the maintainers could make very clear where everything was supposed to go. Only on posting not on edit (meant to be helpful, and not enforce the rule)
  • On the other hand, templates could also be optional. There are different kinds of templates a community might want--intro template, fiction post template, etc, and they might only want to facilitate using them to make it easy, not force every post to use them --Foxfirefey 06:25, 28 July 2008 (UTC)

• http://community.livejournal.com/suggestions/846378.html - Stop moderated communities from automatically adding to someone's friendslist when they're accepted. Allow people to add the community through the email notification.

• http://community.livejournal.com/suggestions/823731.html - Show a list of the user's pending membership requests.

• http://community.livejournal.com/suggestions/816158.html - Provide the option to, after making a post to a community, re-post that same post to the person's own (primary?) journal.

• http://community.livejournal.com/suggestions/817203.html - Filter community posts by user (so that communities with too many members for the tag space, or too many topics for the tag space, still have a way to show who made which post). Probably should be a search box rather than a drop-down list, especially for communities with 1x10^65536 members.

• http://community.livejournal.com/suggestions/839359.html -- ask whether you want to include it into a custom friends group or not when replying to a community invite.

• Allow people who post entries to a moderation queue to edit or delete the entries while they're in queue.

• Ability to choose from among the community's user pictures when posting. This is a very frequently requested option on LJ.

• Allow people no longer members of a community to access their protected posts on that community http://community.livejournal.com/suggestions/777037.html

• Include a "leave community" link on a deleted community's info page http://community.livejournal.com/suggestions/780007.html

• user-written but maintainer editable "summary" lines, in addition to the subject header, to make searching easier http://community.livejournal.com/suggestions/790175.html?view=11460255#t11460255

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. Zilla 12 in different form

• 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.

Also suggested: http://community.livejournal.com/suggestions/901201.html -- Add a "Manage Communities" quick link to the bottom of the "Pending Membership Requests" page (the page that appears after maintainers approve / reject members) so maintainers can tend to the remaining requests.

• 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/894442.html - controversial; "display proof of age 18+ on profile." Potentially useful for community moderation, but otherwise a potential invasion of privacy; other (legal?) issues? (if a comm is marked 18+, the system will not let someone who isn't 18+ by birthdate join it)

• http://community.livejournal.com/suggestions/871787.html - Moderation Queue Log. Lists things like submission time, submitted by, IP address, unmoderated, title + some content, status, action taken by who? Enthusiastic support by large community maintainers.

• http://community.livejournal.com/suggestions/700658.html - related to previous suggestion; deletion notification for maintainers is planned, in the forms of "notify me when anyone deletes a post from this comm" and "notify me when anyone deletes a comment from this post."

• http://community.livejournal.com/suggestions/814367.html - Track how many times a member posts or comments in a given community (with an opt-in for the maintainer, and possibly also with an autogenerated notice that a given community tracks that information)

• http://community.livejournal.com/suggestions/826739.html -- separate options for "Who can create new tags and add/remove tags from entries?" under Tag Settings in the Community Management Page.

• http://community.livejournal.com/suggestions/904739.html -- create a few more options between moderator and mainainter levels of access; expanded suggestion in comments: community owners/main maintainers could choose what tasks other admins/moderators could perform

• http://community.livejournal.com/suggestions/905967.html -- Add a link to the requesting user's profile page to Community Membership Request emails sent to Community maintainers, so that they can go directly to the information about that user before choosing approval or rejection. (merely a matter of linking the requesting user's username in the email)

• A way to add other maintainers without giving them the ability to remove you from maintainership

• Ability to withdraw a community invite that hasn't been accepted/rejected yet Zilla 502

• When rejecting a membership request, be able to send an explanation that will appear in the rejection notice

• Ability to make limited changes to someone else's entry in the comm: change security level, turn comments on/off, turn screening on/off, add LJ-cut, etc. Zilla 14/Zilla 12/Zilla 11

• Be able to add tags to a moderated entry while approving it

• Maintainers can specify a tag that gets automatically added to all new entries

• A way for maintainers to sticky post- much requested!

• On standard Edit Profile, users with email aliases have a dropdown option to display actual email address, alias, or both. I suggest that community maintainers with aliases also have this option for the community's profile.

• A new class of comm entries: "maintainer-posted" entries that could be edited wiki-style by any maintainer, not just the one who posted it.