If the API provided rules as an array rather than a single big chunk of text then frontends could present a list to users when reporting.
Voyager
The official lemmy community for Voyager, an open source, mobile-first client for lemmy.
Rules
- Be nice.
- lemmy.world instance policy
Sponsor development! 👇
💙
Yes that would be the best solution imo. However, that would require changes to Lemmy (which usually take a while). Did you see the proposals in the linked issue?
Yeah. The problem with using a regex is the formatting of the rules would need to be very consistent. There'd be no way to make it reliable.
The proposed text would not render as markdown and would be invisible when viewing it normally, it would be added in addition to the existing text. It would be used to store the rule list for clients specifically wanting a list until such a feature is added to Lemmy itself.
Ideally voyager would display the sidebar and a field to enter the reason for the report for the user.
That could also work. It's certainly a lot simpler than my proposal in the GitHub issue.
Maybe even a note saying that vague reports may be ignored.
I do my best to investigate what the problem might be, but at some point I need to dismiss the report without actioning anything
I don't think that's a good idea. There often is a very good reason for the report. I usually sent a DM asking the reporter to elaborate further.
Fair enough, I do investigate more for the communities I'm actively moderating, but a lot of the reports are intended for the community moderators, and it's not really my place to follow up on it.
Another common one is "spam". We get a lot of legitimate reports for spam which I take action on. Sometimes a regular comment is reported for "spam", and if it doesn't look like spam to me then I will end up dismissing it.