Similarly, I once needed some new robust tyres for my folding bike, so I googled 'marathon plus 20 inch'.<p>Google helpfully informs me that<p>marathon + (20 inches) = 1.00001204 marathon
Google refuses to search for hash-like strings that aren't well-known across the web.[0] That's why this search gives no actual results. (It certainly will in the future as this submission gets reposted, breaking the googlewhack)<p>[0] <a href="https://news.ycombinator.com/item?id=31638976" rel="nofollow">https://news.ycombinator.com/item?id=31638976</a><p>(I think Bing also blocks hashes but has an exemption for UUIDs; right now it gives me results for random UUIDs but not random MD5s)<p>Bing and Yandex are both capable of locating OP's Minecraft account in online databases:<p><a href="https://web.archive.org/web/0/https://www.google.com/search?q=%220e2b835d-4d9a-4b8b-b009-988741022e8c%22" rel="nofollow">https://web.archive.org/web/0/https://www.google.com/search?...</a><p><a href="https://web.archive.org/web/0/https://www.bing.com/search?q=%220e2b835d-4d9a-4b8b-b009-988741022e8c%22" rel="nofollow">https://web.archive.org/web/0/https://www.bing.com/search?q=...</a><p><a href="https://web.archive.org/web/0/https://yandex.com/search/?text=%220e2b835d-4d9a-4b8b-b009-988741022e8c%22" rel="nofollow">https://web.archive.org/web/0/https://yandex.com/search/?tex...</a><p>PS: example of an uncommon hash that Yandex finds but not the other two: the MD5 of 'Hacker News' (f3e4...), which actually occurs on the web on one site (<a href="http://archive.ph/oLgUe" rel="nofollow">http://archive.ph/oLgUe</a> <a href="http://archive.today/lkyNN" rel="nofollow">http://archive.today/lkyNN</a> <a href="http://archive.ph/v3TY5" rel="nofollow">http://archive.ph/v3TY5</a>)
That's pretty funny. I work for a company that puts 5 alphanumeric characters on physical devices to track and identify them. We are always putting those 5 characters into various google sheets. And every so often one had an E in the middle of all numbers and google would convert by default to something like "1.10E+34" so we had to make SCIENTIFIC_NUMBER_REGEX = Regex("\\d+e\\d+") and stop making codes with E's in the middle.
I'm amazed that google does that (I didn't know) and even shows the steps! But it still is lacking.<p>The "solution" here is just a simplification, not something I would call a "solution" (like for an actual equation). But as it isn't an equation, that could be fine. Another weird thing is that it won't simply eliminate the first term with 0x=0. Why?
That's interesting, because on the other end, lately I had some cases where Google did not even recognize very elementary operations and would not give me the result. That never happened before.