I often get reports with just “Breaks Community Rules” and no additional context. This is because Voyager automatically sets the mandatory report reason as “Breaks Community Rules” without actually adding a reason. However, it’s often not clear why a post would break those rules and which rule would be broken.
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.
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.