On Feb 11, 2009, at 2:27 PM, Shelly wrote: > Lynne Baer wrote: >> Like taking the existing "freeze this thread" tech, just applying it >> to a top-level post? (No clue if it would be Just This Easy for devs; >> I suspect it's a bit more complex than that. ;) ) >> >> I would love this, at the very least for entries in personal journals >> and the original posters of an entry to a community, simply >> because if >> you go back after-the-fact and disable comments to a post, that means >> they're not even available for *viewing* and education. I'm a bit >> less >> certain about it being a maint/mod power - I can see pros and cons to >> allowing this, but it's better than having to take the draconian >> measure of deleting the post just to stop commenting nonsense?
> Why shouldn't it be a mod power? If I can already delete posts (and > since that's my only option, that's what I do), then surely freezing > some of them is better? FYI, we do plan to allow community maintainers to do a number of useful things to posts, including adding lj-cuts, setting a more- restrictive security level (although not less-restrictive), setting a more-restrictive adult-content level (again, not *less* restrictive), allowing community maintainers to disable comments on an entry, etc. "Don't allow any new comments to this post" is something I'd like to have in future -- not a priority for beta launch, just because we're getting overloaded on what's blocking beta launch, but in the future. If we do implement it, I don't see any reason why we shouldn't also allow maintainers to set it on individual community posts. --D -- Denise Paolucci [email protected] Dreamwidth Studios: Open Source, open expression, open operations. Coming soon! _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
