OpenUserJS
Consider Ability to Edit Comments/Discussions
This doesn't really have a home issue and should be referenced with this issue number. It is however referenced randomly in other tickets.
My thoughts are for a very strict edit...
- Discussion may only be renamed by the originator and perhaps a given time frame.
- New comments can be edited without notification of being "last edited"
- If a newer comment is added to a discussion, then prior edits should indicate that they were "last edited" with a last accessed perhaps with the same type of Base16 date hash like our other models for the
id. - Optionally if we get as, forgive the candidness but it's accurate, "anal" as GH use a sha1sum for the content as well.
- If the originator gets removed for spam reasons, or other, the entire discussion should be removed... or the next reply author becomes the owner... this is a choice... personally I'd rather see the entire thread disappear. One of the most common private notices I gave on USO was to not to respond to spammers. To keep things on a positive note it is best just to remove all comments under that discussion assuming the originator was at fault. Obviously if a reply is spam just the spam should be addressed.
- If a reply is removed, it might be nice to see a brief message say "comment deleted" but this is optional.
- Issue discussions could be controlled much like the Open/Close where the owner of a script page has control to open/close and originator has close privi's... e.g. change open/close for remove... if removed issues should say that it has been removed... or we can add all of this to flagging a comment and handle it internally...
These are a few of my thoughts. Obviously it has some thought into it already but this is what would be handy imo.
In general these steps will promote healthy commenting along with healthy reediting. All of these will, in one form or another, assist in administrative decision regarding spam messages.
See also:
- https://openuserjs.org/discuss/%5BFeature_request%5D_Ability_to_edit_comments
For the purpose of this discussion, "deleted" means the user who posted a comment deleted their own comment. It is no longer stored and doesn't appear in the Graveyard. "Removed" means that the comment was removed by moderation and it will appear in the Graveyard.
1-3 agree 4. Not necessary. 5. Remove the whole discussion if the first comment is removed. 6. If a comment is mod removed, show nothing. If the comment is deleted, show a message that it was deleted in its place. 7. Not exactly sure if I understand, but I would rather stick to the same moderation logic we use everywhere for issue discussions. If it's spam, users flag it and mods removed it.
I'd like to add: 8. You can delete your own discussion if there are no comments by others.
I'm going to assign this to myself because I'll be handling the backend, but I have no experience with bootstrap so I'd welcome help with the UI.
That's fine for 7... was an optional choice that I threw out as a bone.
I can help with bootstrap but I think @Zren is more tenured in this area... it's basically just looking up the "Documentation" link in the README.md and see what is available in the toolkit. Even in one my .user.js scripts I am just currently buttonizing on the bottom instead of a full fledged toolbar... which I'm not sure if the current bootstrap has one.
I don't feel right editing someone's comment. If we have a problem with something we just remove it (and the notice of removal will be visible).
Okee doke... striking out. I will add that to the privacy soon e.g. if someone posts their email address, for example, moderation and above should just remove whatever is present to avoid spam bots that harvest this information.
Know this is a wee bit late _(re)_addition but 9) should exist at least in part for splits... I just needed to do one manually and it was rather lengthy but very doable e.g. if we need to remap a comment to another discussion.
