"Later he applied his extravagant principle to the other numbers. In place of seven thousand thirteen, he would say (for example) Maximo Perez; in place of seven thousand fourteen, The Train; other numbers were Luis Melian Lafinur, Olimar, Brimstone, Clubs, The Whale, Gas, The Cauldron, Napoleon, Agustin de Vedia. In lieu of five hundred, he would say nine. Each word had a particular sign, a species of mark; the last were very complicated.... I attempted to explain that this rhapsody of unconnected terms was precisely the contrary of a system of enumeration. I said that to say three hundred and sixty-five was to say three hundreds, six tens, five units: an analysis which does not exist in such numbers as The Negro Timoteo or The Flesh Blanket. Funes did not understand me, or did not wish to understand me."
If it's 3 non-repeating unordered words, the minimum vocabulary will need to be 256*3 = 768. Realistically you'll need an order of magnitude larger. That's a pretty large vocabulary.
Write a Grease-monkey (or equivalent) script, that reads your query variable, applies the value to the top bar, and then add that parameter to all links on the page.
Optional: Then write a bookmarklet, that displays a color-picker, and reloads the tab with the changed querystring variable.
(HN web server admin might get some "scary" log file entries though, regarding an "unusual" additional QS variable)
I'm still working diligently on counting the grains of sand on the beach closest to me, and hopefully we can pool all of our work together for a final count. As soon as that's done I'll start trying to name all the stars. Colors? I'm tired already.
Ha, I thought of doing that but decided it would be too hard, so i picked the much easier challenger of naming the numbers between 0-0.01. I'll be finished in no time.
Though it did cross my mind to split the range in to 2 parts and then recursively bin each part in two; if I allow repeating names ... Perhaps then ones chances would be greater than zero.
CSS Color Module 4, which introduced support for the DCI-P3 color space, also introduced support for the even larger ProPhoto RGB and Rec.2020 color spaces (as well as the similarly-sized Adobe RGB). These were already supported in media that could be embedded in web pages.
Hey, I independently came up with a similar solution (https://notryan.com/colors) and it renders to HTML.
But ugh... I applaud your simplicity. I used `unzip` instead of zcat, but I guess .zip files normally use GZIP internally. And, I didn't know you could use `sort` for a specific field! So I ended up using a full SQL engine... Learn something new everyday :)
I propose that names be considered more like probability distributions. For example the name “red” has a probability distribution that probably peaks in the neighbourhood of #FF0000 but includes a large range of colors; the distribution of the name “crimson” likely has a much narrower distribution. Under this interpretation, and given enough data, one could feasibly extract “the” name for any given colour using a maximum likelihood estimation (what name is most likely to generate the observed colour).
And to collect data on this, one could for example ask many random users to choose the range of colours they believe correspond to a given name (“select all red colours”) and merge the results into the distribution. (There are many, many other ways to carry out such a survey; this is but one example).
Obviously, you won’t get to 16M names this way, but you could definitely learn quite a lot about where the “boundaries” are between colours from this kind of exercise!
"can't tell apart" isn't a transitive relation. That is, just because I can't tell A from B and I can't tell B from C doesn't mean I can't tell A from C.
Hah, I love it! There's a lot to dislike about HN and the culture here, but questions like these that sort of make me go "Well obviously not, because ... erm" are quite common and always interesting.
Sure. At a minimum, it seems some folks find it entertaining to do so. That is a point. But naming them for the conventional purpose of indexing into cognitive clusters doesn't work, obviously.
The entire website is obviously a silly joke. Even if the colours were distinguishable you wouldn't go about naming them in this fashion but in some more systematic fashion
I thought the entire thing was an excuse to have yet another node dependency.
const namedColors = require('namedColors');
const chalk = require('chalk');
console.log(chalk.hex(nameColors['Hacker News Orange'])(
lol, you just downloaded a 200meg dep for named colors
));
Depending on how it's produced it's not even _a_ colour, it's three colours, or two colours, then the same two with a bit of blue. Perhaps my eyes lack a normal number of blue receptors, and a substantial amount of blue still wouldn't alter the perceived colour.
-- Funes the Memorious, Borges
Screaming Grey: #AAAAAA
It's Still Basically Black: #000001
Nice: #696969 (lol)
These would make for some great candidates: https://colors.lol/ ;)
Yours should be called Yabba Dabba Doo.
Or perhaps Fred Flintstone.
That managed to uncover all of the Father Ted fans on the team.
Stubbed Toe: #FFFFFF
I'm struggling to figure out if this is a serious attempt, though.
Deleted Comment
Although the 65 one needs to be better named "Fake Hacker News Orange" or "Hacker Fake News Orange".
Edit: I think my new favorite is "#403403 Forbidden Brown"
Optional: Then write a bookmarklet, that displays a color-picker, and reloads the tab with the changed querystring variable.
(HN web server admin might get some "scary" log file entries though, regarding an "unusual" additional QS variable)
Though it did cross my mind to split the range in to 2 parts and then recursively bin each part in two; if I allow repeating names ... Perhaps then ones chances would be greater than zero.
;oP
They need to have a way to sort by votes, or have a "Best of" or whatever. I was curious (and they provide the data! Thanks!)...so naturally-
Edit: sorry..."Focus Group Blue"...im dyingBut ugh... I applaud your simplicity. I used `unzip` instead of zcat, but I guess .zip files normally use GZIP internally. And, I didn't know you could use `sort` for a specific field! So I ended up using a full SQL engine... Learn something new everyday :)
There are zero people in the world who can tell #FF4500 from #FF4501, so aren't they effectively the same color?
And to collect data on this, one could for example ask many random users to choose the range of colours they believe correspond to a given name (“select all red colours”) and merge the results into the distribution. (There are many, many other ways to carry out such a survey; this is but one example).
Obviously, you won’t get to 16M names this way, but you could definitely learn quite a lot about where the “boundaries” are between colours from this kind of exercise!
Particularly, what you're describing is this: http://imgs.xkcd.com/blag/satfaces_map_1024.png :-)
Deleted Comment
If there is at least one person who cannot tell two colors apart, they should have different names.
And conversely, there are infinitely more colors than that particular digital representation can express.
Or maybe lockdown is really getting to their head.
https://en.wikipedia.org/wiki/Eric_A._Meyer#Personal_life