I downvoted because the reply has nothing to do with the argument.
If I know for a fact that you're cheating on your wife, and someone else asks how I know that, then a third person chirping about your sketchy business dealings is entirely irrelevant to the question, no matter how much suspicion it might otherwise raise.
The thing I hate about rust is that compiling a small app immediately creates 100gb of junk, and that junk doesn't live in the responsible project's folder, and that junk doesn't get cleaned up by anything.
I noticed yesterday that they've managed to make editing the text field on their search page lag and flip/reorder characters entered during the edit: editing “foot pedal” into “foot pedal keyboard” became “foot pedal oardkeyb”
This is the problem with using vector search for everything: there is no “verbatim” when the corpus and the search are both converted to a vector, and not necessarily using exactly the same transform.
I know that's the common story, but I have never seen any actual court cases confirming that theory; certainly the recoverable damages from such copying such an error would be minuscule.
The problem is that factual details aren't copyrightable in the first place, so no amount of licensing will prevent organizations with enough money to pay a lawyer from understanding this and using the data as they see fit. And on the flip side, those organizations can pay those same lawyers to write scary boilerplate to make it seem like their map data is “proprietary” and therefore “protected by copyright” even though it isn't.
If I know for a fact that you're cheating on your wife, and someone else asks how I know that, then a third person chirping about your sketchy business dealings is entirely irrelevant to the question, no matter how much suspicion it might otherwise raise.