Semperverus

Normalizing this kind of thing is not okay. It doesn’t matter if its in the TOS, it shouldn’t be a technology in the first place.

You don’t seem to be living in reality.

I’m not in favor of big corpo AI in the slightest, and think that all the data centers should be nuked from orbit, but splitting hairs about LLMs being called or not being called AI is the most greasy neckbeard thing you could possibly do and takes energy away from actually resolving the issues. The language is flexible and it really does not matter whether we call them AI or force a distinction, so long as everyone understands what we are talking about.

Stop wasting everyone’s energy on pedantery and go out and actually solve the problem instead.

Unfortunately for you, the English language has shifted to include LLMs under the “AI” umbrella.

I wasn’t saying it was different from OSM, I was suggesting it as an OSM client.

It offers superior user experience that is almost on par with Google Maps but without being Google Maps (and some things it does better, like more detailed instructions).

It does highlight a lot of glaring issues with the OSM data itself though, be prepared for that - OSM lacks tons and tons of individual street addresses, which is very frustrating. I add them when I can but its too much on my own.

I recommend CoMaps on Android, (or Organic Maps, which CoMaps forked from when Organic started enshitifying)

Doesn’t Prusa rebrand OrcaSlicer though? How is that in-house? Why not just support OrcaSlicer and build their configs into it as a first-class citizen?