eloquence
Add a “Report review” functionality
When viewing the following reviews, I noticed that there was no “Report review” functionality to report errors or, in my opinion, abusive use of a review. For example:
- https://lib.reviews/review/da8a8577-6325-428f-bcb2-bfcd9688b6d5 - The language label is “IT” for Italian, but the language of the review is German.
- https://lib.reviews/review/9c02c06c-fdeb-4112-adf0-a670b1dcddea - The old restaurant has closed and a new one has moved in.
- https://lib.reviews/review/2994f8f3-c1f2-4cef-a1f6-8a49207c6797 - In my opinion, this is not a review of the restaurant and should be considered by the team.
I like the general idea of flagging a review for moderator attention and putting those reports in a queue (maybe sending an email too - if only account holders can report, it shouldn't be too noisy). The site is so slow-moving typically that I don't think it's super-urgent yet, but it may become necessary once we promote a "Request an account" feature.
For the first review you mention, I saved a copy in German which should resolve the language label issue. I think the real fix to reduce this specific category of mistake is to let users set the content language explicitly (discussed in #349) instead of coupling it to the currently active UI language. But I also think we can potentially give moderators some leeway in fixing incorrect review metadata, wiki-style.
For the second case, I don't think we have a good way to represent "this URL used to point to this thing, but it points to that other thing now". The best I can think of is unlink the OSM URL (since that describes the current restaurant) and manage the metadata ourselves. We should probably also have a general "closed" or "unavailable" setting for the subject itself. What do you think?
For the third case, I'm a bit more torn. The labor abuse is cited to what looks like a reliable source, and labor rights issues are a legitimate lens through which people may want to review things. I could imagine a review team that entirely focuses on such matters and tries to find businesses it considers ethical.
The abusive case to me would be one where a user just pursues a personal vendetta, or bombs many review subjects as part of some crusade against <evil thing of the moment>. But this specific case feels more borderline to me.
Regarding point 1: Okay, thank you.
Regarding point 3: I lost sight of the bigger picture and focused solely on the meals itself. From that other perspective, it's a good review.
Regarding point 2: The root cause of the error lies with OSM, as the data was overwritten instead of using the Key:disused:* for the closed business and creating a new one. To begin with, a one-time query of the data from OSM at the time of writing the review would suffice to prevent such errors. Is this possible? A marker/message "This place is closed." is not urgent but very welcome.