You can't google 9999999..99999999999999999999999
11–20 of 84 posts
Re: You can't google 9999999..99999999999999999999999
#1211..22 would be to search for all integers between 11 and 22.
The effect is that the search is too broad. The problem is more likely to be that the range search is a mapreduce that performs a search for each item in the range.
You can imagine why that's a bad idea, and some aggressive timeouts are probably what stop it from going too far.
Plus the numbers in the range of the OP search are likely to fall in the ranges of sensitive numbers, credit cards being the most sensitive... which are likely to be explicitly blocked.
Re: You can't google 9999999..99999999999999999999999
#13Our systems have detected unusual traffic from your computer network. Please try your request again later.
Re: You can't google 9999999..99999999999999999999999
#14Re: You can't google 9999999..99999999999999999999999
#15Re: You can't google 9999999..99999999999999999999999
#16Bing to the rescue: http://www.bing.com/search?q=9999999..9999999999999999999999... Pretty similar URL format eh?
Re: You can't google 9999999..99999999999999999999999
#17Neither 1111111..11111111111111111111111 11111111..1111111111111111111111 111111..111111 // minimum case or any other integer combination. 6 digits is the minimum amount that spawn the bizarre error.
100000..100000 Neither
Re: You can't google 9999999..99999999999999999999999
#18Re: You can't google 9999999..99999999999999999999999
#19On a faintly related note, I once was calculating partitions, using a relatively inefficient method (memoization: if f(n,k) is the number of distinct ways to express n as the unordered sum of integers no greater than k, then f(n,k) = f(n-k,k) + f(n,k-1)). My computer started to feel the strain in the thousands (this algorithm is O(n^2) in space and time). I then googled for the partition of, say, 1034, which is: 9136…
Re: You can't google 9999999..99999999999999999999999
#20The double dot indicates that this is a ranged query. 11..22 would be to search for all integers between 11 and 22. The effect is that the search is too broad. The problem is more likely to be that the range search is a mapreduce that performs a search for each item in the range. You can imagine why that's a bad idea, and some aggressive timeouts are probably what stop it from going too far. Plus the numbers in the r…
http://www.google.com/search?q=%229999999..99999999999999999...