Others have pointed out many weaknesses of this product already, but one seemingly annoying issue is homophones in the context of verbally communicating your lo

Others have pointed out many weaknesses of this product already, but one seemingly annoying issue is homophones in the context of verbally communicating your location. They use a 40k word dictionary; surely there are tons of homophones in there. And there are surely more homophones outside the dictionary (which would just give an error when queried through their API). When you call some delivery service and ask them to find you at course.serial.flower, they could end up querying one of: - coarse.serial.flower - course.cereal.flower - course.serial.flour - coarse.cereal.flower - coarse.serial.flour - course.cereal.flour - coarse.cereal.flour If these homophones are used in the dictionary, the other person will get an effectively random location on earth. If the homophones are not in the dictionary, they will get no result from the API. In practice, you'll either need to be extra careful about specifying locations this way, or you'll need to provide extra location data like zip/city/etc. as error-correcting code. But at that point, it seems like you're not much better off than you would be with conventional addresses or LAT/LON coordinates for common use cases.