Mark Smith (marksmith) wrote in lj_dev,
Mark Smith
marksmith
lj_dev

Comment Limiting

A new feature has been proposed, but the concensus around the office is that we want the concensus of the community before we actually implement it. We're thinking UI here--placement, look, feel, making it intuitive for the user.

The feature is the ability to set a time limit on comments. For example, you can specify in your userinfo that you want all of your posts to only allow comments for a week. Perhaps you don't like getting comment emails and you don't want to lose any comments, so you only check your most recent posts and are sure to never get comments way back in your journal. Perhaps you've got a community full of "24 hour proposals" and you don't want comments trickling in days after things have been decided. (Heh.)

Anyway, it seems like we're going to make this a per-user property, not a per-entry property. We want to give users the ability to disable it on a particular entry, though. For example, you could say "limit comments to 48 hours from post time" and then on a particular entry you have the options:

Disable comments entirely
Enable comments per timeframe option
Enable comments ignoring timeframe (unlimited comment times)

We've considered allowing this to be on a post by post basis, too, but the UI is throwing us for a loop. There are already a lot of optional post settings--overloading disallow comments to be three items and then making a time entry field (if we go that route) seems to make things far too big and cluttered.

UI people, what do you think? Should this be a userprop or a logprop, and either way, how should it be represented so as not to confuse people?
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 47 comments
Previous
← Ctrl ← Alt
Next
Ctrl → Alt →
Previous
← Ctrl ← Alt
Next
Ctrl → Alt →