Ripeness guide - additional type information

[wbazant]

We can use LLMs to provide ripeness guides. Then a person interested in the location can compare what's on the tree with what they see, and decide when it's ready:

See Sveder#2 and Sveder#1

[Sveder]

From slack conversation, to be able to push this feature what we need:

1. Move the data to backend
2. Take translations into account
3. Add a "report mistake" button
4. UI fixes - breaks for locations with multiple fruit (for example: https://issue-1128.falling-fruit-web.pages.dev/locations/591687/38.2764386,-111.2409159,13z) - move it into each fruits dropdown.
5. Tests and make sure there is no html injection possible.
6. Ethan comment: "I do notice that it tends to be less useful/relevant when applied to generic taxa (e.g. compare Pyrus, which mostly talks about Pyrus communis, and Pyrus calleryana), so probably best to generally limit to (sub)specific taxa."

To discuss:

1. Add a flag to only show confirmed texts
2. How to handle reported mistakes and where to send the notification.

[ezwelty]

@Sveder Cool! And I think it can/should be incremental – we can always launch with a few species, fruit only, English only, and "email us" reporting, then build further to more species, more plant parts (flowers, sap, etc), more languages, and a more flexible reporting mechanism (currently location-linked only, but could be extended to types). I remain available to help loading the data to the backend (which remains more my domain).

[jordanstreiff]

I think that it's important - both from a legal and ethical perspective - that we let users know when they're reading AI generated content. Disclaimer maybe? A little info icon above or below? Something like "This text was generated with Claude Sonnet 5, but proofed by a human." or... "This text was partially or in full generated by an LLM, use caution and do your own research as well."

Personally I like the idea, beyond just reporting mistakes, of crowdsourcing descriptions (wiki style?), just like we crowdsource food locations.

[wbazant]

@Sveder I've made an epic #1145, with lots of stuff out of scope here. To finish this feature, can we address four things?

1. Fetch the data, don't bundle
   Bundling the data with the code will increase startup time too much. I just realised we don't need to store it in the database, since we have the public directory and for example fetch languages like that. Add a file there, and add a new module under src/components/connect to add a fetch + store into Redux when a user visits their first location page. Only do it when the language is English. Compare to src/components/connect/ConnectTypes.js.

2. Display under accordion
   Show the new content like we show wikipedia links, not on the location page. We can work on making it more visible soon afterwards - see the epic.

3. Reduce content to only species level types
   Ethan noticed that entries for e.g. pear genus Pyrus try to cover all of pears and aren't so accurate or helpful to a forager.

4. Display along with context for what we're showing
   I like your UI with a vertical bar to mark a paragraph. Extend it with an info, explainer, or header, that has the word AI in it - Jordan is right that when we show AI generated text it should be labelled as such. It could include a link to an email, explanation that we're trying out a new thing, etc. or it could just be three words long like 'AI description (beta)'.