From Dreamwidth Notes
Revision as of 17:12, 10 December 2010 by Xtina
See also: Possible paid community features.
- 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 is 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. Another 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 the 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. :) Bugzilla #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 membership communities from automatically adding to someone's reading page 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 a 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 journal.
- http://community.livejournal.com/suggestions/839359.html -- Ask whether you want to include a community into a custom reading group when replying to a community invite.
- Allow people who post entries to a moderation queue to edit or delete the entries while they're still in the queue.
- Ability to choose from among the community's user pictures when posting. This is a very frequently requested option on LJ.
- http://community.livejournal.com/suggestions/777037.html -- Allow people who are no longer members of a community to access their own protected posts on that community.
- http://community.livejournal.com/suggestions/780007.html -- Include a "leave community" link on a deleted community's info page.
- http://community.livejournal.com/suggestions/790175.html#t11460255 -- User-written but maintainer-editable "summary" lines, in addition to the subject header, to make searching easier.
- Community Importation: the ability to import content from Livejournal communities to Dreamwidth. Main issues: copyright of individual posters vs. desire to import content from existing communities. Possible solution: allow users to import all of their own posts from a Livejournal community into a Dreamwidth community. This would put the burden of effort on the people who wanted to import communities, rather than on DW for making certain every post imported is by someone who allows it. Only current Dreamwidth members could import posts, so the issue with OpenID accounts not being able to post would be non-existent.
- Technical feasibility: The importer would need to sort through posts made to a community for those made my the user requesting import. How to determine which posts were made by that user? Can the current importer be expanded to include this functionality?
- Other considerations: Access to locked content on the comms by Dreamwidth, storing the username and password for an extended period of time, giving moderators a veto to make sure accidental/trolling importations don't happen. (tea)
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 it's fixed by the original poster. Basically, Bugzilla #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 maintainers/moderators. This 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. List 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 the 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 maintainer 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. (This is 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.
- 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. Bugzilla #14/#12.
- 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!
- Isn't this covered by the ability to make it a future-dated entry? ~Cesy - I don't think you can future-date (or DOOO) at all on comms. --Pau Amma
- On the Edit Profile page, 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.
- http://community.livejournal.com/suggestions/791975.html#t11501735 -- Ban all users linked to the same email address.
- http://community.livejournal.com/suggestions/879445.html -- Show "preapprove poster" checkbox for community maintainers only. There seems to be mixed feelings about this, but the general consensus is that it should be consistent, and that moderators should not have a power on one page, and not have it on another.
- http://community.livejournal.com/suggestions/945021.html -- Allow removing the email address for a community journal (that is, remove it from the account settings, not just hide it on the profile).
Extra bits from Uncategorized
- http://community.livejournal.com/suggestions/951212.html -- Modify membership request emails to have more useful info for moderators.
- http://community.livejournal.com/suggestions/945449.html -- Various suggestions for compulsory tags or default tags or moderating untagged entries.
- http://community.livejournal.com/suggestions/942399.html -- Moderated posting in communities for specific users.
- http://community.livejournal.com/suggestions/941710.html -- Be able to view raw HTML of entries in a moderation queue.
- http://community.livejournal.com/suggestions/938284.html -- Easy way for maintainers to view when members' journals were last updated.
- http://community.livejournal.com/suggestions/924381.html -- Different subject lines for different types of moderated submission notification.
- http://community.livejournal.com/suggestions/919035.html -- When requesting to join a moderated community, have subscribing to the community as an option.