Comment by NeckBeardPrince
Comment by NeckBeardPrince 3 days ago
What would be a valid reason to allow this? That just seems mind-numbingly stupid.
Comment by NeckBeardPrince 3 days ago
What would be a valid reason to allow this? That just seems mind-numbingly stupid.
Markdown is pretty tricky for new users to figure out, so quite often, users will just paste big snippets of code without formatting them, which is nearly unreadable. I'll usually edit these posts to add ```backticks``` around any code.
This is particularly useful when editing the top-level comment of a popular issue to specify the current status. Or when a peer opened a placeholder issue and you fill it up. Etc.
If you actually use GitHub as a social network of sorts, there are many reasons to do edit comments. All the edits are visible anyway. You're on Git-Hub, you can already edit everything you have write access to.
That also means that some users will be pressured to censor illegal speech no? If you live under e.g. a regime that disallows or discourages criticism, now suddenly the onus is on you to do something about those comments because you have the ability to. If you couldn't edit the comments it's not your fault.
Either way I think it's a pretty stupid feature the way it's implemented; it should show the edit more clearly or indicate that the comment has been written by multiple people (like StackOverflow does), especially if edits change more than e.g. 10% of the original comment.
I maintain the formatter for Dart, so a lot of my job involves maintaining the issue tracker for the formatter.
I use this feature all the time. Users get Markdown wrong, give titles to issues that don't make any sense, have typos, etc. Being able to edit issues helps me keep the issue tracker easier to understand and navigate for maintainers and users.
Every feature can be used. That doesn't mean every feature should not exist. The fact that the edit history is still visible means it's next to impossible to abuse the feature. It works fine.