| // ==UserScript== | |
| // @name Wykop Emojis 3-bajtowe | |
| // @namespace https://gist.github.com/patrolez/ | |
| // @version 0.4.12 | |
| // @downloadURL https://gist.github.com/patrolez/b10d4500451eefdd47504fba987cd8b5/raw/wykop_3bajtowe_emoji.user.js | |
| // @updateURL https://gist.github.com/patrolez/b10d4500451eefdd47504fba987cd8b5/raw/wykop_3bajtowe_emoji.user.js | |
| // @description Emojis subset limited to 3-bytes Unicode. It works in misconfigured MySQL databases with wrong `utf8` charset. <https://stackoverflow.com/a/50264108/12755962> | |
| // @match https://www.wykop.pl/* | |
| // @match https://wykop.pl/* | |
| // @icon https://www.google.com/s2/favicons?domain=wykop.pl |
| All filenames and hashes: | |
| Windows: | |
| Filename: flashplayer32_a_install.exe | |
| MD5 hash: 6331a3bfe47233560a72da2855616285 | |
| Filename: flashplayer32pp_a_install.exe | |
| MD5 hash: 4b3f96b3138ff834f8673efde9bb771f |
I've even seen implementations that compare objects using
JSON.stringify.
I would expect a memoizer and most hash code/table implementations to treat { foo: "bar", baz: "quux" } and { baz: "quux", foo: "bar" } as equivalent, but many implementations use JSON.stringify, which doesn't guarantee this:
$ node
> JSON.stringify({ foo: "bar", baz: "quux" })
'{"foo":"bar","baz":"quux"}'
> JSON.stringify({ baz: "quux", foo: "bar" })
'{"baz":"quux","foo":"bar"}'