Earlier quoted context omitted.
Personally, I wish someone I like, like Colin Percival, would start an email service. I like the way he runs Tarsnap.
The problem with starting an e-mail service is the crazy level of administration and sysadmin headaches it induces merely to be able to reliably send e-mail to 90%+ of endpoints.. let alone anything else. The engineering problem is a pretty interesting one, but the headache of ensuring your users can actually get their mail someplace makes it seem dull or insurmountable to solo developers.
Giving up on Google
151–160 of 192 posts
Re: Giving up on Google
#152Google "search engine"
Actually, they're doing it for other things too:
[web based email] [adverts for publishers] [traffic analytics]
I'm sure there's more.
Wow. That truly is an epic fail. Google have removed Google from the SERPs.
LOL! I love(d?) Google, but they are definitely screwing something up somewhere. These rubbishy results occur when I'm logged out too (well, I don't have Web History or personalized search enabled so I guess that's n/a)
Re: Giving up on Google
#153Earlier quoted context omitted.
I'm not worried, it's just that the gggp of this comment mentioned that search history is protected by a password and so it 'should be safe from prying eyes.' All I did was point out that that data is stored on a server somewhere else and that there are lots of eyes that could be prying there. I'm sure that there are plenty of people that are concerned about their internet use being monitored, for instance, dissident…
Any website that you use could store all kinds of data about you without even telling you. Not to mention your ISP, who knows everything! At least Google is making it clear via Google History that they do have the means to do it.
Re: Giving up on Google
#154Earlier quoted context omitted.
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Most feedback posts don't give us enough specifics to go back and figure out what went wrong and how to make things better. We do have a "Give us feedback" link at the bottom of each search results page which does some neat AJAX-y things. But even then, we get a lot of "Hi, I'm tryin…
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Okay, here goes. Lately I have been doing a lot of C# searches. Google suggest strips out the hash (#) from the suggest items, so I keep getting faked out by likely C programming matches. Can you please stop stripping off the "#"? Otherwise, I'll need to attach a hot wire to my down…
Normally Google doesn't allows searches for punctuation, because doing so would swell the index size a lot for very little return in terms of helpful searches. But since we're engineers, we do search some punctuation, e.g. underscores so you can search for sprintf_s, and terms like C# and F#. I'll ask whether the # can carry through into Suggest.
Re: Giving up on Google
#155Earlier quoted context omitted.
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Most feedback posts don't give us enough specifics to go back and figure out what went wrong and how to make things better. We do have a "Give us feedback" link at the bottom of each search results page which does some neat AJAX-y things. But even then, we get a lot of "Hi, I'm tryin…
Why not ask permission to transmit the last few searches and a snapshot of the results. I mean, I usually only hit "give feedback" when i'm not finding the stuff I want. You'll probably be able to discern a lot from that.
Re: Giving up on Google
#156Earlier quoted context omitted.
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Most feedback posts don't give us enough specifics to go back and figure out what went wrong and how to make things better. We do have a "Give us feedback" link at the bottom of each search results page which does some neat AJAX-y things. But even then, we get a lot of "Hi, I'm tryin…
I wonder if it would help to give some feedback to the ones that you actually took into account? I think I've tried more than a couple of times to give some feedback about the search results. Seeing that nothing happened, and getting nothing but an automated response, I've stopped doing that. Reporting flashing ads to the ad team worked better, they were removed later the same day.
Overall I agree with you, but even if we had that channel, many times the feedback would be: "Yup, that's a bad set of search results. We'll try to come up with a way to make it better, but it might be a while. Getting an algorithm to do better on this search will be hard."
Re: Giving up on Google
#157Earlier quoted context omitted.
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Most feedback posts don't give us enough specifics to go back and figure out what went wrong and how to make things better. We do have a "Give us feedback" link at the bottom of each search results page which does some neat AJAX-y things. But even then, we get a lot of "Hi, I'm tryin…
I have given feedback on search for "BMTC" not returning the official website of BMTC (bmtcinfo.com). (2-3 months back). But the search results haven't changed since then.
$ wget http://bmtcinfo.com/ --2010-09-14 09:01:43-- http://bmtcinfo.com/ Resolving bmtcinfo.com... failed: Name or service not known. wget: unable to resolve host address `bmtcinfo.com'
The url http://bmtcinfo.com/ just doesn't work in a browser or with wget. And trying to fetch the "www" version of the website, it does a 302 redirect to a deeper url. 302 redirects are the ones that don't pass PageRank. The last time we tried to crawl the page, we got an error--probably from the non-www version. I'll see what we can do to find this site better, but returning errors instead of content to Googlebot really hurts that effort.
By the way, we provide a free webmaster console that would let the owner of this domain self-diagnose these issues. The "Fetch as Googlebot" feature lets the owner send Googlebot to fetch a url on their site and see what Googlebot saw, including errors and redirects. If the owner of bmtcinfo.com were to use that tool, they'd probably notice the errors pretty quickly.
Re: Giving up on Google
#158Earlier quoted context omitted.
Not that I can detect. For instance: หาเมนบอร์ดช๊อคเกต775 returns 42k results, and is not exactly a common combination of words on google.com. Extra points if you know what it stands for :)
> หาเมนบอร์ดช๊อคเกต775 'Haa men bord chok ket 775' = 'Find motherboard socket 775.' I would have thought that 'socket' would be a direct English transliteration, and use ซ (s) not ช (ch) though. Are you in Thailand, Jacques? Also, what makes you think this is such an uncommon phrase? It may not rival English, but there are plenty of Thai speakers out there, in many countries.
I wish.
On google.com it would be an uncommon phrase. On the Thai version of google not so much I guess.
Re: Giving up on Google
#159Earlier quoted context omitted.
Not really. I've had this break for me all the time when searching for programming terms. Proof: Google for "what we have here is failure to communicate" http://www.google.com/search?sourceid=chrome&ie=UTF-8... The first hit is the wiki article on the quote (good), but the exact search string is not present on the page.
Click "cached", and you get the explanation: "These terms only appear in links pointing to this page: what we have here is failure to communicate"
"Brand Model 1234 broken control panel"
And get an aggregate review page with a mention of broken control panels for another model and brand on which my model and brand are not listed....
I'm glad that my search term is in a link pointing to this page, but that is worth less than nothing to me...
Re: Giving up on Google
#160Earlier quoted context omitted.
People in Google's search quality team really do like to read posts like this as long as someone mentions the searches they were doing. Okay, here goes. Lately I have been doing a lot of C# searches. Google suggest strips out the hash (#) from the suggest items, so I keep getting faked out by likely C programming matches. Can you please stop stripping off the "#"? Otherwise, I'll need to attach a hot wire to my down…
I'm pretty sure that several search quality people are reading this thread now, but I'll try to mention this explicitly to people. Thanks for the suggestion. Normally Google doesn't allows searches for punctuation, because doing so would swell the index size a lot for very little return in terms of helpful searches. But since we're engineers, we do search some punctuation, e.g. underscores so you can search for sprin…