Live data from Hacker News

Why Bother with What Three Words?

shkspr.mobi

101–110 of 336 posts

Re: Why Bother with What Three Words?

#101

All you need is https://what3emojis.com

> If you are unhappy with the emoji you are assigned you can reserve custom emoji markers for your triangle for only a low, lifetime price of $24.99.* Custom emoji can be any length (except three), up to the VARCHAR limit set in our MySQL database.

Awesome.

Re: Why Bother with What Three Words?

#102
post #80

W3W suffers horribly from "call for price". You won't catch Google or Amazon making you call and talk to a human being (on GMT time no less) before figuring out if you can afford their service. I'm preparing my own version, truly open source (though with a premium component), with the following improvements over W3W: •Length-optimized. If one character sufficiently describes your location, you don't need to tack on e…

You have to call Google for Analytics pricing when you outgrow the free tier. And no, we could not afford it.

But at least they tell you that it starts at $150K/year so you know right off the bat if it's even in your ballpark. A lot of SaaS products completely hide thier pricing entirely. I have zero interest in sitting through some sales-bro's phone pitch before I know if I'm even in the right pricing bracket. Nothing like sitting through an hour long preso only to find out afterwards something is 10x what you were looking to spend.

Re: Why Bother with What Three Words?

#103
post #55

Earlier quoted context omitted.

"you could infer that 1234 W Something Rd is nearby 1238 W Something Rd." Don't overestimate that. There are nasty exceptions where the street disappears and continues elsewhere without a significant gap in house numbers, especially in cities with a long history.

Don't throw the baby out with the bathwater here. Being able to naively navigate city -> street -> number is incredibly useful, and that it is occasionally broken doesn't make it an undesirable feature.

It's more than occasionally broken, there's billions of people living in spots where it doesn't work.

Re: Why Bother with What Three Words?

#104
post #80

Earlier quoted context omitted.

You have to call Google for Analytics pricing when you outgrow the free tier. And no, we could not afford it.

But at least they tell you that it starts at $150K/year so you know right off the bat if it's even in your ballpark. A lot of SaaS products completely hide thier pricing entirely. I have zero interest in sitting through some sales-bro's phone pitch before I know if I'm even in the right pricing bracket. Nothing like sitting through an hour long preso only to find out afterwards something is 10x what you were looking…

Do they now? They certainly didn't at the time a few years ago.

I at the time found some prices online searching around but nothing from them.

We were very hopeful we'd get some sort of discount because we're in educational tech, so our income per user is very low, but nope. Free to $100k overnight is insane. We’ve got a guy whose full time job now is basically developing analytics tools for us and it’s a cheaper solution.

Re: Why Bother with What Three Words?

#105
post #29
post #13

Does anyone have a list of patents What3Words has? Regardless, this service solves a problem that does not exist whatsoever. My guess is they will go out of business in a few years.

It does exist in developing nations, where street names change very quickly and are not very reliable (and the rusty government can't keep up with the quick development). First hand experience, Vietnam - I currently live in a street that wasn't there a year ago and isn't in Google Maps. If you put it into Google, it will send you to another place, 200 meters away. (They are getting better fast, compared to Apple Maps…

That's what Plus Codes appear to be aimed at. And it's open source. https://plus.codes/

Re: Why Bother with What Three Words?

#106

Earlier quoted context omitted.

So your solution won't result in "coordinates" easily memorized by humans or easily translated to the very vast majority of map implementations?

Not sure how you got that from what I typed. The fact is the 4 coordinates (two numeric, two with the stupid "N/S/E/W" corresponding with traditional), decimal points, and reverse order from an X,Y coordinate system, are hardly easy to memorize. They're next to impossible to memorize. What part of pencil and paper didn't come across?

Because, from what you've described, it sounds like your system will look like base64-encoded coordinates. Ie 39.022874, 21.913384 will be IJASDO, which isn't as easy to memorize as W3W.

Re: Why Bother with What Three Words?

#107

I inherited a property management system where previous developers used what3words for storing location of homes (since reverse geocoding based on address is not reliable in some countries we support). However, after an internal review we realised that a lot of our UK properties have locations in Asia or the US... It turned out that typos in what3words often result in a valid location on the other side of the world.…

I imagine that a single digit typo in latitude could also result in a valid location on the other side of the world

This is true, but the structure of the number itself carries a connotation to the reader to pay extra attention to their accuracy.

We expect numbers to be number-like where every little digit is important. We expect words to be word-like where plurals and sometimes even synonyms mean the same or similar things.

Re: Why Bother with What Three Words?

#108
post #90

Earlier quoted context omitted.

Ummm. That's what latitude and longitude are. Angles. Or equivalently, radians. And what's magic about one meter? Latitude and longitude can be arbitrarily precise. But whatever. You want 40 million? Well, 360 degrees / 40 million ~ 10^-5. That's easily handled by "43.63872, -116.24135".

Yes, it seemed you were arguing those two numbers could easily be encoded using existing words. If you want to make gibberish word like objects it's probably possible.

But what's the point of that?

If they were always the same two (or three) words, fine.

But if there are multiple such encoding systems, any set of three words (foo.bar.baz) is ambiguous. Because it depends on the system being used.

So sure, someone might remember "foo.bar.baz". But "foo.bar.baz" in W3W might be in SF. But in Hanoi by some other system.

And then we get to the need to pay W3W to generate those codes. That's crazy bullshit.

Re: Why Bother with What Three Words?

#109
post #90

Earlier quoted context omitted.

Ummm. That's what latitude and longitude are. Angles. Or equivalently, radians. And what's magic about one meter? Latitude and longitude can be arbitrarily precise. But whatever. You want 40 million? Well, 360 degrees / 40 million ~ 10^-5. That's easily handled by "43.63872, -116.24135".

Yes, it seemed you were arguing those two numbers could easily be encoded using existing words. If you want to make gibberish word like objects it's probably possible.

Words in one language are very often ~gibberish words in other languages. And worse, because of false homonyms. And people with heavy accents.

Re: Why Bother with What Three Words?

#110

Earlier quoted context omitted.

Yes, it seemed you were arguing those two numbers could easily be encoded using existing words. If you want to make gibberish word like objects it's probably possible.

But what's the point of that? If they were always the same two (or three) words, fine. But if there are multiple such encoding systems, any set of three words (foo.bar.baz) is ambiguous. Because it depends on the system being used. So sure, someone might remember "foo.bar.baz". But "foo.bar.baz" in W3W might be in SF. But in Hanoi by some other system. And then we get to the need to pay W3W to generate those codes. T…

Yes, W3W is stupid, but each address is a pointer to lots o bits.
Post reply on HN