qgil wrote on 2014-05-05 19:24:00 (UTC)

https://secure.phabricator.com/T4909 is basically implemented upstream. Users can remove their own comments via UI. Admins can remove anybody's comments. There is a command-line tool for admins with server access that can destroy items completely.

One point open is whether users should have any limit to delete their own posts, in order to avoid frustrated users to remove all their contributions. See https://secure.phabricator.com/T4909#20 and following discussion.

qgil wrote on 2014-05-10 22:05:16 (UTC)

Assigning to Andre, who needs to decide whether this task can be closed (since the features described in the title and description are implemented in Phabricator upstream), whether a new task should be created for the feature of Rate limit or restrict access to comment removal, and whether it should be a blocker for Day 1 or not.

aklapper wrote on 2014-06-03 15:43:34 (UTC)

Summarizing the upstream ticket activity: Admins can use the "Remove" action in the UI to remove/hide comments, see https://secure.phabricator.com/T4909#19 .
That was the main intention here for Day 1 and I'm closing this task as resolved.

Rate Limiting is additional functionality not provided by our current tools either. Though nice to have, we have managed to survive without so far; it is no regression that should block day 1.

Nemo_bis wrote on 2014-06-15 10:44:16 (UTC)

Rate Limiting is additional functionality not provided by our current tools either. Though nice to have, we have managed to survive without so far;

That's not correct. Absence of such features made us add restrictions we didn't like (editbugs no longer for everyone). But that's T146.

aklapper wrote on 2014-06-16 10:46:21 (UTC)

Bugzilla never had rate limiting. Bugzilla has/had restrictions which stop average users from doing harm by changing fields, but average users can still do harm by mass-commenting without editbugs.

importing issue status