Uuuh, TIL that @lib_reviews officially welcomes and endorses "AI" slop.

As it relies on #LinkedData, is there maybe another project sharing schemas for location reviews I could go to instead?

#libreviews #FOSS

@nik @lib_reviews

Hey Nik - I use various AI coding agents to maintain the project, which has been a great help. However, there are absolutely no plans to use AI to generate _content_ or to allow "slop reviews" on the site; that would defeat the purpose.

That said, judging by your posts on the subject, I'm guessing that's enough for you to turn your back on it, which is fair enough. But I felt it important to clarify the distinction, anyway. :)

@eloquence @lib_reviews

I don't want to use or operate any software that welcomes contributions stolen from others. It's a great decision that you place your work in the public domain, but it is disgraceful to disrespect the licensing choices of others and deny them credits they asked for in return for their work.

@nik @lib_reviews

I understand. I disagree that training ML/AI systems constitutes theft (copyright infringement to _obtain_ training data is a different story), or that their outputs automatically constitute derivative works.

Anyway, if you're looking for alternatives, mangrove.reviews has come a long way and has a nice OSM integration:

https://mangrove.reviews/search?sub=geo%3A40.7416028,-73.9902269%3Fq%3DVeggie%20Grill%26u%3D30&q=veggie%20grill

Mangrove Reviews -

Try out writing reviews in the public domain, using a cryptographically generated account that puts you in control of your privacy.

@eloquence @lib_reviews

That looks very interesting for a variety of reasons.

I value your openness towards promoting other projects when users are critical of your own. Thanks!