Earlier quoted context omitted.
Yes, it doesn't hit some strange error page though.
Correct. Instead it returns some generally useless results that are likely not at all what the user desired. Truthfully this seems about what I expect from Microsoft.
You can't google 9999999..99999999999999999999999
41–50 of 84 posts
Re: You can't google 9999999..99999999999999999999999
#42Earlier quoted context omitted.
Yes, it doesn't hit some strange error page though.
Correct. Instead it returns some generally useless results that are likely not at all what the user desired. Truthfully this seems about what I expect from Microsoft.
If the user entered "9999999..99999999999999999999999" in the search box, what would you say he desired to get in return?
Serious question, cause I have no clue about why would anyone genuinely want to search for that ...
Re: You can't google 9999999..99999999999999999999999
#43The 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…
Re: You can't google 9999999..99999999999999999999999
#44Earlier quoted context omitted.
Even better, LOCK DOWN YOUR GOOGLE ACCOUNT WITH DOUBLE AUTHENTICATION, then set Google alerts for your: credit card, or if paranoid, partial credit card # "123456789 " Email address Home address Phone number screen name (e.g.: "andrenotgiant" -site:ycombinator.com) Bank acct partial Password, Password partial "p@ssw0r "
Sweet, now someone just has to get into my google account settings and I'm screwed.
Re: You can't google 9999999..99999999999999999999999
#45On 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
#46Yes you can: http://www.google.com/xhtml?q=9999999..999999999999999999999...
Re: You can't google 9999999..99999999999999999999999
#47Earlier quoted context omitted.
Yes, it doesn't hit some strange error page though.
Correct. Instead it returns some generally useless results that are likely not at all what the user desired. Truthfully this seems about what I expect from Microsoft.
Re: You can't google 9999999..99999999999999999999999
#48The 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…
Then why does 100000..100000 get the same error? Not a huge span, and not likely to contain anything all too sensitive.
This range works: 99999..1000000
Increment that first digit and it will fail though.
Re: You can't google 9999999..99999999999999999999999
#49Reading the comments here gave me an idea....google your own credit card numbers to check if its already in some scammer's index. While no results might not necessarily mean you are safe, a positive match is a clear red flag.
Even better, LOCK DOWN YOUR GOOGLE ACCOUNT WITH DOUBLE AUTHENTICATION, then set Google alerts for your: credit card, or if paranoid, partial credit card # "123456789 " Email address Home address Phone number screen name (e.g.: "andrenotgiant" -site:ycombinator.com) Bank acct partial Password, Password partial "p@ssw0r "
Re: You can't google 9999999..99999999999999999999999
#50Earlier quoted context omitted.
Correct. Instead it returns some generally useless results that are likely not at all what the user desired. Truthfully this seems about what I expect from Microsoft.
Instead it returns some generally useless results that are likely not at all what the user desired If the user entered "9999999..99999999999999999999999" in the search box, what would you say he desired to get in return? Serious question, cause I have no clue about why would anyone genuinely want to search for that ...
So, if Bing is trying to "emulate" google in that way for more advanced queries, they are doing it wrong.
Since google is sort of the defacto standard for search right now, I would say that Bing's response would be out of the ordinary for what a user accustomed to doing those kinds of searches would expect.