Comment by dannyfritz07
Comment by dannyfritz07 3 days ago
Allowing the maintainer to prepend a comment to the top seems more sensible to me to be honest. Would make API use harder potentially, but it would avoid weird abuse like this.
Comment by dannyfritz07 3 days ago
Allowing the maintainer to prepend a comment to the top seems more sensible to me to be honest. Would make API use harder potentially, but it would avoid weird abuse like this.
reporting abusive edits requires moderation/arbitration. the rules can instead be changed to sidestep the issue, while maintaining the value of the feature.
Report to whom? Github, who allows the behavior and therefore doesn’t see anything wrong with it, or the repo admins who have proven they they couldn’t give a rat’s ass about the very thing you’re reporting? The well is already poisoned, there is no reason to think that they’d suddenly change their stance and cooperate.
In this case at least, github (most probably) banned this account, presumably after reports. There are also other stories for github banning accounts for pr trolling kind of behaviours. So not sure if everything is perfect, but at least there are cases such things work.
> designing it around adversarial use would be a loss for everyone
hmm... isn't this more of a 'personal viewpoint'? why are you stating this like a fact?
moreover, how would it "adding Edited by ~" constitute as a "loss for everyone" ?
I agree on adding "report abuse" button, but if no one notices that edit, how would anyone know what to report in the first place?
github is meant for collaboration, designing it around adversarial use would be a loss for everyone. Adding a function to report absusive edits rather than an entire post would be a better choice imo.