Difference between revisions of "Community Wishlist"

From Dreamwidth Notes
Jump to: navigation, search
(→‎Communities: General)
(→‎Communities: General)
Line 32: Line 32:
 
* 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
 
* 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
  
−
* <strong>Community Importation</strong>: the ability to import content from communities on Livejournal 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 journals, 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.  
+
* <strong>Community Importation</strong>: the ability to import content from communities on Livejournal 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?
 
: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 journals 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. (<dwuser>tea</dwuser>)
+
: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. (<dwuser>tea</dwuser>)
  
 
== Communities: Community Maintenance/Moderation ==  
 
== Communities: Community Maintenance/Moderation ==  

Revision as of 03:25, 16 April 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.
  • 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/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.
  • 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.
  • Community Importation: the ability to import content from communities on Livejournal 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. ([info]tea)

Communities: Community Maintenance/Moderation

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/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! 
- Isn't this covered by the ability to make it a future-dated entry? ~Cesy
  • 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.
Retrieved from "http://wiki.dreamwidth.net/wiki/index.php?title=Community_Wishlist&oldid=4058"