HNHacker News
TopNewBestAskShowJobs

thelittlenag

337 karma · joined September 2, 2016

Engineer.
submissionscomments
thelittlenag··on What’s going on with WhatFreeWords?
The goal here is to be more clever than just encoding to a list of random words. We want to encode to a good choice of words.

Partly, that means choosing words that are short, aurally clear, unambiguous, in common usage, etc.

It also means we need words that together form a sentence. Initially that means choosing a good sentence structure. Our is [1-Adjective 2-Noun 3-Verb 4-Adjective 5-Noun (6-Adjective) (7-Noun)]. Next, we have to choose words that are most often the part of speech for the dictionary they need to live in, since we'll never re-use a word.

Getting this dictionary together and having it good is a huge task. Of course we have a naive dictionary, but that's barely suitable for testing purposes.

I may choose to make the "docs" I've written available today in their rough state. That will explain things slightly more.

thelittlenag··on What’s going on with WhatFreeWords?
We're working on the implementation (as time permits). Once we have that it will be published and accessible from search.qalocate.com.

The cert is "wrong" because I redirect back to qalocate.com and that cert only covers the base domain. We have another for all the sub domains but that isn't used by our main site.

My hope is that we'll have something in the next few weeks but its only me (fulltime) and another guy (spare free time), so things move slowly.

Btw, thank you so much for watching the video! I hope it was useful.

thelittlenag··on What’s going on with WhatFreeWords?
I think that w3w is over optimized and suffers from a large number of failure modes that interact poorly with a typical human's memory.

For example, it is really easy to mis-remember and accidentally pluralize or re-order words. Our memories just don't maintain that kind of precision. Yet w3w will happily accept your mis-pluralized word, or re-ordered words, and spit out a location, with no indication that maybe you made a mistake.

w3w forces you to remember and use exactly the 3 words they gave and nothing else, without risking a garbage-in-garbage-out scenario.

In fairness, they do try to put similar words very far from each other, but unfortunately this only mitigates the risk and doesn't eliminate it.

Our design is resilient to these issues in human memory with the geohashphrase. If you re-order words in the phrase, pluralize (or singularize) a word, or even go so far as to change part-of-speech (e.g. noun a verb) then you'll still get back the same geohash.

Btw we hope to offer 4-base-word phrases for well populated locations. Those phrases should be easy enough to use in everday situations. Outside of that you can get complete coverage with a 5-base word phrase.

thelittlenag··on What’s going on with WhatFreeWords?
Yes! The geohashphrase will be free to use and open source. Right now we're working on an implementation and docs and once we have that we'll release all that under a permissive license.

Right now the problem is that we don't have anything more than a description of our idea to release...

thelittlenag··on What’s going on with WhatFreeWords?
I don't think you could easily do that with 3 words. They already have a dictionary 40000 deep and then end up repeating words, just to get to get enough combinations.

With the GeohashPhrase we intentionally telescope exactly like you've described. This is because all we do is encode a geohash, and it already has this property.

thelittlenag··on What’s going on with WhatFreeWords?
(disclosure: i work for qalocate.com)

I think that OLC and W3W have many flaws. If you want to read a critique OLC I suggest you read this: https://www.qalocate.com/whats-wrong-with-open-location-code...

At QA Locate we've been working on a similar solution that we call GeohashPhrase. Rather than encoding a location as 3 random words, or the alphanumeric code of OLC, we instead just encode a geohash as a sentence.

Encoding/decoding is relatively trivial, and can be done offline, but I've yet to write up docs I'm comfortable with other people reading.

There are some light docs you can reference here: https://www.qalocate.com/resources/

We have a video on the tech here: https://www.youtube.com/watch?v=nlscJ8MOPjM

I'm working on some better preliminary docs, but working code takes priority ;-)

Btw, the GeohashPhrase will be open source and free to use.

thelittlenag··on What’s going on with WhatFreeWords?
(disclosure: i work for qalocate.com)

At QA Locate we've been working on a solution to this that we call GeohashPhrase. It encodes a geohash as a sentence.

There are some light docs you can reference here: https://www.qalocate.com/resources/

And we have a video on the tech here: https://www.youtube.com/watch?v=nlscJ8MOPjM

I'm working on some better preliminary docs, but working code takes priority ;-)

Btw, the GeohashPhrase will be open source and free to use.

thelittlenag··on Open Location Code: An Open Source Standard for Addresses
A five word phrase is roughly a 5m x 5m region, so 1m wouldn't be enough to move into the next block.

But in general yes, locations that are "close by" will share the same set of words.

The mapping itself is extremely simple. A geohash is encoded as string of alphanumeric characters where each character is in base-32. This means each character encodes 5-bits of coordinate information. To get to a 5m x 5m region you need 45-bits worth or 9 geohash characters.

To map this 9 character geohash to a phrase is simple - we simply use the binary representation of the characters as a numeric index into a fixed dictionary of words. The first character is mapped to a word in a dictionary containing 32 entries. After that we map characters in pairs to dictionaries of 1024 words; 2 geohash characters being 5-bits we get a 10-bit index.

So two geohashes that share the same prefix will also share the same words, modulo our grouping scheme.

thelittlenag··on Open Location Code: An Open Source Standard for Addresses
Doing this saves you about two bits worth of information while usually greatly increasing complexity.

To see why consider how geohashes work. As you add letters you telescope in to a more precise region. The land/water distinction is less information than even what is encoded by the very first character of your 9 or 10 character geohash.

thelittlenag··on Open Location Code: An Open Source Standard for Addresses
Alternative to DNS you say? Like a Location Name System!?!

Well, we're building it! I cannot supply much info right now other than the whitepaper at https://www.qalocate.com/resources/ but I'm really hopeful that we'll have a beta out in the next few months.

thelittlenag··on Open Location Code: An Open Source Standard for Addresses
Unfortunately we're conflated addresses with coordinates, but fundamentally addresses are not geo-coordinates. Addresses are really just an ancient (500+ years!) short-hand for giving a person a set of rough directions to a "place", with the person supplying that last mile of figuring from context exactly where they are going. It is impressive how far we've taken this technology, but it is really starting to falter as the information age has matured.

From my perspective any solution, like this one, that tries to solve the problem of addresses through the lens of coordinates is doomed to failure. The reason is that there are just too many use cases that raw coordinates cannot supply context for.

For example when I ask for directions to a restaurant, the context of who I am and what my relation to the restaurant is matters quite a lot. A set of coordinates handed out uniformly to all who ask does nothing for my particular use case. Plumbers, health inspectors, and delivery drivers don't use the same entrance, or parking, as ride share or pedestrians.

I think it would be more productive to move to a system that is capable of capturing and relaying these kinds of relations, or at least taking as them as input. Better geo-coordinates miss the forest for the trees.

thelittlenag··on Open Location Code: An Open Source Standard for Addresses
Yet another alternative is GeohashPhrase (https://www.qalocate.com/resources/) which is a simple and direct mapping of word tuples to geohashes.

The word tuples are intentionally structured so they can form a phrase. The exact phrase is left up to the person, with the only constraint being that that phrase use all the base words.

And because of how word choice is made (words that map different parts of the geohash come from disjoint dictionaries) the phrase mapping is invariant under changes in recalled word ordering, word use (noun to verb, or adjective to noun), and more.

Some advantages of the GeohashPhrase:

1) Will be open source and free (Once we finalize the dictionaries and write some real docs.).

2) Designed for offline usage.

3) Designed to be friendly to humans. Phrases and words are MUCH more friendly than alphanumeric digits.

4) Multi-language. The encoding scheme works for most languages.

5) Resilient to errors in human memory, which tends to re-order words, change pluralization, etc.

6) Easy to read, write, share, etc.

7) Directly decodes to a geohash.

8) Works with any map.

-----------------------------------------

Here is a comparison side by side of each option:

Lat/Lon : -6.7184 , 129.5080

GeohashPhrase (Raw): salute tell small student muddy

GeohashPhrase ("Encoded"): The small muddy student told me of a salute.

XADDRESS: 7150 Magical Pearl - Maluku, Indonesia

WHAT3WORDS: percolator.surmount.retooled

GEOHASH: qyu1g0by7

MAPCODE: VQ6.1MFD

OPENLOCATIONCODE: 6Q5F 7GJ5+J6

-----------------------------

(Disclosure: I work for QALocate.)

thelittlenag··on The lat/lon floating point delusion
HAHAHAHA! Having not met Joe I don't actually know, but I presume that is a legit picture.
thelittlenag··on The lat/lon floating point delusion
What would future proofing even look like?

For me I think we need to move away from thinking first/primarily in terms of coordinates. Yes, I know that sounds silly but hear me out.

Say someone is going out to meet a friend at a restaurant they haven't been to before, or perhaps they don't exactly recall the directions they took the last time -- how do they find directions? The first thing they most definitely do not do is say "hey maps app, tell me how to get to -37.80467681 144.9659498".

There is a level of indirection we go through via the names of businesses, places, etc. So we ask, "tell me how to get to I Love Istanbul". And we hop through a number of steps mapping that unstructured name to some coordinate.

But what if instead we used structured names instead of unstructured "names"? Then those names could map to a coordinate, or a street address, or well anything. What's more we could attach metadata to the name.

This is what DNS does. Humans know the names. They are structured according to some simple to follow rules. And computers take care of mapping those names to IPs, as well as other metadata.

Why not do exactly the same, but with locations? Re-use the same system but map to a coordinate? Or a region? Or whatever you need for your use case.

If you did this you'd now have an L-NS instead of a D-NS. That's exactly the insight we've had at the startup I'm working at.

[1] https://www.qalocate.com/resources/

thelittlenag··on The lat/lon floating point delusion
These kinds of issues are what we've solved at QALocate.

There are a number of different issues here, which I think are only partly explored through the article.

Let's take as given that you need to direct a person some place. In the article, they are directing someone to a restaurant. But this gets complicate fast. Is this person a patron rather than, say, a deliver driver there to pick up an order, or a plumber there to fix and appliance, or an inspector there to observe the kitchens, or ...?

By using a lat/long, or any geo-coordinate, we lose the human-value of context. Each of the folks I list above has a very different place they potentially need to navigate to. And even if their destination is the same, the routes they took may NOT have been. Where they park, or were dropped by ride share, and which doors they use are also influenced by their role.

Using a geo-coordinate to drops the rich meaning that humans in all their roles require. A better solution is to use a real identity and then, when and where coordinates are needed, derive them based on the persons role, whether it be patron, plumber, or paramedic. As roles change, or as the structure itself changes, then directions change to meet them. I find this a much richer solution than just blindly telling my maps app to direct me to some GPS location.

Another issue hinted at but not deeply explored is that often what we want to specify is a region or volume, not a coordinate. Things in the real world consume volume. Coordinates are idealized points and do not. This may seem a trite observation, yet, the majority of our tools think in terms of points. With the rise of autonomous vehicles, especially drone delivery, we need to move towards representations of regions and/or volumes, depending on needs. I'm not convinced that geopolys are quite right for this task and instead we need something that is comfortable with the fuzzy and complicated boundaries humans have to deal with.

[1] http://www.qalocate.com

thelittlenag··on Why Bother with What Three Words?
You should check out our LNS system. You find the docs at http://qalocate.bamsaas.com/whitepapers
thelittlenag··on Why Bother with What Three Words?
Our startup offers a geohash phrase that is hierarchical in nature. You can find the docs at: qalocate.bamsaas.com/whitepapers
thelittlenag··on Why Bother with What Three Words?
You should check out what we're working on at qalocate.bamsaas.com/whitepapers/. Even an improvement on W3W is still going to be rather limited and only address part of the problem. We're trying to provide solutions for the entire space.
thelittlenag··on Why Bother with What Three Words?
The startup I'm working with offers a much better solution. We call it a geohash phrase. Instead of three random words, where plurals and order matter, instead we map geohashs to 5-word tuples that easily form a phrase. Moreover, the words will only ever appear in one slot of the tuple, and pluralization and word order don't matter.

You can find more at our website: qalocate.com

thelittlenag··on Open Location Code
I'm involved with a startup that I believe has a wonderful solution to this and other related problems. Our website: http://qalocate.com/

Our platform: http://qalocate.bamsaas.com/wp-content/uploads/2018/12/QA-Lo...

The biggest issue with solutions like this isn't that they aren't clever, or even that they aren't better than say a geohash or lat/lon, but that they have the wrong target. Computers don't really care since its just as easy to parse a geohash, a lat/lon, or an open location code. The tricky bit is when humans get involved.

Its humans that have way more limitations when it comes to using complex systems. And frankly, humans still use addresses because the system co-evolved with us and our needs. Addresses solve the problem well enough, and have "outs" for when they don't work. For a bit more in-depth discussion on this see: http://qalocate.bamsaas.com/2018/04/04/addresses-are-complic...

So if we want to replace addresses, then we really have to think outside the box. Fortunately, the web has done a lot of the heavy pushing by introducing all kinds of new, useful, and exploitable semantics that we can apply in other domains.

Humans are pretty good at using names for things. When computers were first networked, we soon replaced IP addresses with names. Thus was DNS born. We then combined that with another id, and soon we had email.

We believe that a similar system can be used for locations. No one really cares about the exact geohash or lat/lon of a location, or the niftyness of your coordinate system. Instead, what we need are memorable names. So why not just use names?

That's what LNS (http://qalocate.bamsaas.com/wp-content/uploads/2018/12/QA-Lo...) is. It works very similarly to DNS and allows one to link arbitrary names to exact coordinate locations, structures, or even regions.

For example, I can have "thelittlenag.frontdoor" if I want to point someone to the exact coordinate of my front door. If I want drone deliveries, then maybe I tell Amazon to use "thelittlenag.deliverydrone". The lawn guy can use "thelittlenag.propertyboundaries" to figure where my property lines start and end. And "thelittlenag.house" and "thelittlenag.gardenshed" can logically reference as entities(!) the two structures we have on our property.

PM me if you have any questions.

thelittlenag··on Open Location Code
This is a general problem with solutions in the space. Part of the niceness of say geohashes is that they telescope down.

The startup I'm involved with has developed what we call a geohash phrase. The core idea is to map English (or whatever language) words to the characters of a geohash. We usually map a word two-characters at a time, giving us 10-bits of precision for each additional word. So your location might be something like: "The big dog walks near the red house."

What is nice is that the phrase telescopes. So you can be vague when you want and only provide say the first three words of your location.

thelittlenag··on Open Location Code
The startup I'm involved with has a solution that solves this problem.

Edit: Sorry about the terseness. I decided about half-way through to write a top-level comment that delved more deeply.

In short, our solution is this: http://qalocate.bamsaas.com/wp-content/uploads/2018/12/QA-Lo...

The AliLocator is flexible enough that whole structures can be sub-divided by any arbitrary criteria, with floor as potentially one of many. Since the AliLocator itself would be a bit awkward to use, you'd just want to create an LNS entry that then pointed to it.

thelittlenag··on Ask HN: What are the best MOOCs you've taken?
Absolutely, this was one of the better courses I've taken. My only wish would be to have the course expand and include models from says physics or chemistry, just so that students could get a feel for how both quantitative and qualitative models can both be useful.
thelittlenag··on Finding Pwned Passwords with 1Password
That is true, but the price structures are different. Stock prices, and other equities, are already priced with everyone knowing that you have permanent ownership. Software isn't priced that way. If it were then I would expect prices to be much higher.
thelittlenag··on Ask HN: What are the best resources to properly learn Scala?
I know this question is mostly about resources in dead tree format, but don't forget there are sometimes local events and meetup groups that can help you learn Scala (and other languages too!).

For example...

If you live in Dallas/Fort Worth and would like to learn Scala then you should know that the local Scala Enthusiasts group is hosting a Scala Essentials workshop on April 7th, 2017. This will be an all-day, hands-on event for Scala beginners. We will start with a language intro and finish up coding a REST server. More details can be found here: https://www.scala-enthusiasts.com/scala-essentials-workshop-...

thelittlenag··on Thinking at the Margin: It's Revolutionary
Economics as a discipline can certainly be positive and scientific. Developing a model to predict the elasticity of demand, collecting the data, testing the model, and independently replicating the results is certainly science, with all the pitfalls of doing science well.

Answering whether one should raise/lower the price of some product P to maximize profit for company C is a normative question.

BTW, calling economics a social science doesn't mean that economics gets to shun scientific methods, nor is economics any less a science than physics. Being a social science just means that the discipline will apply scientific methods to develop models of, collect data about, or directly experiment on human subjects. (Physicists, and normal humans alike, don't view individual particles as human and feel no qualms about performing whatever experiments they might feel like, no matter how high energy.)

Humans tend to be understandably nervous about being test subjects and this has limited the pace-of and extent-of progress that economists have been able to make. The extent to which economics relies on inaccurate models ("rational consumers, competition, efficiency" as you say), is the extent to which personal morals, governments, and societies inhibit progress.

One thing I find very cool about economics is that it can put bounds on how much these barriers to our scientific understanding cost and benefit us. There is a cost to having a better model than "rational consumers" and we can know how much that is. But whether or not one ought to pay that cost is outside the realm of economics.

Overall, I think your claim is more rightly applied not to Economics the discipline but to Economists the practitioners.

thelittlenag··on Thinking at the Margin: It's Revolutionary
Logical positivism is a school of philosophy. It certainly impacted the view of what constituted scientific analysis in the realm of economics. I'm more talking about the development of economics as a science, rather than a branch of politics or philosophy.
thelittlenag··on Thinking at the Margin: It's Revolutionary
This is actually one of the first things that my econ classes covered: normative vs positive statements.

Proper and correct economic analysis explicitly concerns itself with positive statements. These are statements that are factual and/or scientific. In this case, it would be things like estimating the maximum life times earnings of the average athlete. You can gather the data, develop a model, and crunch the numbers to test the model.

The flip side are normative statements: i.e. how things ought to be, what values should be upheld, etc. At that point you are more properly concerned with philosophy, specifically morality, than purely economics. You can certainly use economic data, economic terms, economic models, etc in making your case, but ultimately you are arguing for a normative statement (e.g. what is a "just" or "fair" allocation?).

That's not to say that economists don't make normative statements, they do and all too often. But that's usually politics.

← PreviousPage 4 of 4