Live data from Hacker News

New Chrome extension: block sites from Google’s web search results

googleblog.blogspot.com

51–60 of 226 posts

Re: New Chrome extension: block sites from Google’s web search results

#51

Earlier quoted context omitted.

They aren't yet using the data for ranking.

They are or probably would be doing that. See this comment by Matt Cutts: http://news.ycombinator.com/item?id=2218531

And you really think no one in the google search team has thought of how it could be abused ? Come on let's be serious here, they are not going to use these results verbatim or even block websites for everyone just because some users wanted to.

Re: New Chrome extension: block sites from Google’s web search results

#53

I just wanted to say thanks to all the people on Hacker News who asked for this option. We'll look at offering a "block site" option directly in the search results over time, but it takes longer to write, test, and launch that code. In the mean time, use this extension to clean up your own search results and tell us which sites you don't want to see in Google.

Thanks for listening to our requests!

Re: New Chrome extension: block sites from Google’s web search results

#54

Assuming it's a normal extension and has to abide by the same rules that Non-Google Authored extensions do, the extension manifest indicates the extension doesn't have access to do any cross domain posts so all the filtering is done client side. Digging a little deeper, it looks like the blocked sites are stored in Chrome's LocalStorage, which if memory serves me correctly is somehow isolated per extension. It should…

As nolok mentioned, the blocking in Chrome takes place on the client side. We're looking at adding block links to Google's search results along with server-side code (which would let your blocks work on any computer you logged in on, for example), but that code takes longer to write and test than the Chrome extension.

Re: New Chrome extension: block sites from Google’s web search results

#56
post #20

1. http://bit.ly/gTADhE 2. Click Install, close page 3. Open each of the links below in a new tab, click block on the first result 4. Win. http://www.google.com/search?q=Mahalo http://www.google.com/search?q=ehow http://www.google.com/search?q=experts-exchange http://www.google.com/search?q=livestrong.com http://www.google.com/search?q=answerbag http://www.google.com/search?q=bills.com http://www.google.com/search?q=…

about.com actually has some interesting information from time to time.

Secondly, the first link that appears for me when you search for experts-exchange is wikipedia.

Re: New Chrome extension: block sites from Google’s web search results

#57

Free karma points to whoever creates a corresponding Firefox extension...

There are a few grease monkey scripts that the same thing. I wrote my own that does this and also fetches more results to fill in the gaps left by the "This site has been blocked" entries, but sadly I forgot to back it up before I upgraded hard drives and wiped the old one.

Re: New Chrome extension: block sites from Google’s web search results

#58
post #20

1. http://bit.ly/gTADhE 2. Click Install, close page 3. Open each of the links below in a new tab, click block on the first result 4. Win. http://www.google.com/search?q=Mahalo http://www.google.com/search?q=ehow http://www.google.com/search?q=experts-exchange http://www.google.com/search?q=livestrong.com http://www.google.com/search?q=answerbag http://www.google.com/search?q=bills.com http://www.google.com/search?q=…

Don't forget about http://www.google.com/search?q=about.com

What's wrong with about.com?

I generally find about.com has high-quality content giving an overview of a topic, much more in-depth than mahalo or eHow.

Re: New Chrome extension: block sites from Google’s web search results

#59
post #18

Why make this a Chrome extension rather than a google labs type feature?

The Chrome extension was faster to roll out and lets us iterate faster as well because it's outside of front-end pushes. We're looking at offering block links in the search results too, but that code takes longer to write, test, and launch.

It seems we've come full circle -- features easier to push out in client software than through modification of server code.
Post reply on HN