search

Charcoal-SE / SmokeDetector

Headless chatbot that detects spam and posts links to it in chatrooms for quick deletion.
https://metasmoke.erwaysoftware.com
Apache License 2.0
474 stars 182 forks source link

When manually reporting a post that has already been recently reported with a custom reason, add that reason to the original report as a comment #3712

Open gparyani opened 4 years ago

gparyani commented 4 years ago

When manually reporting a post, there is an option to provide a custom reason why the post is being reported along with the report (#1965). Since #2398 was implemented, using this feature will also post a comment on the metasmoke page for the report with the same reason text, attributed to the reporter.

If I report a post using this feature and it's already been recently reported, the reason text will go into the void, on the other hand.

Can we please make it so that if someone supplies a custom reason on a manual report regarding a post that has already been recently reported, the reason they supply becomes another comment on the existing report?

makyen commented 4 years ago

While this certainly could be implemented, the chat response from SD should indicate to the user that the !!/report didn't actually create a report. They should then be able to manually add the comment to the existing post.

gparyani commented 4 years ago

@makyen It does indicate so, with a link to the existing report. But it might confuse some users into thinking that their reason was placed on said earlier report. Making the comment automatic would be much nicer.

stale[bot] commented 4 years ago

This issue has been closed because it has had no recent activity. If this is still important, please add another comment and find someone with write permissions to reopen the issue. Thank you for your contributions.

makyen commented 4 years ago

As far as I know this was resolved a month, or so, ago.

gparyani commented 4 years ago

@makyen This was never resolved. I just tested this and my reason wasn't added. If you're referring to the above PR resolving this, that's still open and not been merged yet.