Comments on: Google/Firefox, please go easy on the trigger http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/ Thu, 18 Mar 2010 02:32:05 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Justin Briggs http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140648 Justin Briggs Wed, 04 Jun 2008 06:28:25 +0000 http://blog.labnotes.org/?p=1038#comment-140648 I agree Google needs to work on their communication methods, but its a difficult process. Stuff like this has happened multiple times and Google tries to contact the webmaster. If you don't have a domain email or webmaster tools, than you're really out of luck. I agree Google needs to work on their communication methods, but its a difficult process. Stuff like this has happened multiple times and Google tries to contact the webmaster. If you don’t have a domain email or webmaster tools, than you’re really out of luck.

]]> By: http://mylid.net/webdesign http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140382 http://mylid.net/webdesign Wed, 23 Apr 2008 10:53:54 +0000 http://blog.labnotes.org/?p=1038#comment-140382 Such an attempt to contact is only formal. You say: "Google sends emails to potential site owner addresses such as webmaster@domain.com Google also notifies site owners with Webmaster Tools accounts". The real site contacts are often not at these termination points, and they should not be. As you know a common way of contacting a webmaster is via whois. Google could do a whois on the domain and e-mail the Admin contact. Google could also do a whois on the site IP address and thus contact the hosting company. Such an attempt to contact is only formal. You say: “Google sends emails to potential site owner addresses such as webmaster@domain.com Google also notifies site owners with Webmaster Tools accounts”.
The real site contacts are often not at these termination points, and they should not be.
As you know a common way of contacting a webmaster is via whois. Google could do a whois on the domain and e-mail the Admin contact. Google could also do a whois on the site IP address and thus contact the hosting company.

]]> By: Labnotes » Rounded Corners - 201 (I can has Shawarma?) http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140349 Labnotes » Rounded Corners - 201 (I can has Shawarma?) Thu, 17 Apr 2008 06:45:55 +0000 http://blog.labnotes.org/?p=1038#comment-140349 [...] Putting the squeeze on malware is a good idea, I like it.  But this one is going form 0-60 in no seconds. Is anyone on the Firefox team reading this?  Please start small, give site owners time to adjust, and us users something to access in the meanwhile.  I don’t like it when Firefox goes dark. [...] [...] Putting the squeeze on malware is a good idea, I like it.  But this one is going form 0-60 in no seconds. Is anyone on the Firefox team reading this?  Please start small, give site owners time to adjust, and us users something to access in the meanwhile.  I don’t like it when Firefox goes dark. [...]

]]> By: Chris Adams http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140330 Chris Adams Mon, 14 Apr 2008 19:25:46 +0000 http://blog.labnotes.org/?p=1038#comment-140330 I think this is going to become routine - stuff like the WordPress exploits going on right now are distributed and approached a lot more professionally than they used to be. One thing we need is some sort of trusted communication so someone like Google could notify known-responsible ISPs about the problem and the ISP could trigger an immediate relist when the problem has been fixed rather than waiting for the site's [often non-technical] owner to figure out how to contact each search engine and request a review. This would also provide a nice incentive for ISPs to be more responsible than is currently the case. I think this is going to become routine – stuff like the WordPress exploits going on right now are distributed and approached a lot more professionally than they used to be. One thing we need is some sort of trusted communication so someone like Google could notify known-responsible ISPs about the problem and the ISP could trigger an immediate relist when the problem has been fixed rather than waiting for the site’s [often non-technical] owner to figure out how to contact each search engine and request a review. This would also provide a nice incentive for ISPs to be more responsible than is currently the case.

]]> By: Assaf http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140328 Assaf Mon, 14 Apr 2008 17:44:12 +0000 http://blog.labnotes.org/?p=1038#comment-140328 See update above. Apparently while they won't tell you why you've been blacklisted, at least they'll attempt to tell you about it. The hacks are, unfortunately, quite common. Happened to me once (spam, though, not malware) and other people I know. See update above. Apparently while they won’t tell you why you’ve been blacklisted, at least they’ll attempt to tell you about it.

The hacks are, unfortunately, quite common. Happened to me once (spam, though, not malware) and other people I know.

]]> By: Blocked by Google at robubu http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140326 Blocked by Google at robubu Mon, 14 Apr 2008 17:27:58 +0000 http://blog.labnotes.org/?p=1038#comment-140326 [...] folks have told me recently that Google is identifying my site as evil. I assure you it isn’t, however I know why google [...] [...] folks have told me recently that Google is identifying my site as evil. I assure you it isn’t, however I know why google [...]

]]> By: sosiouxme http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140324 sosiouxme Mon, 14 Apr 2008 13:31:00 +0000 http://blog.labnotes.org/?p=1038#comment-140324 could've been hacked in the past and was passing out malware. could be this is a copy of someone else's site and not as benign as it looks. hard to say... trust (or lack thereof) is difficult to establish in an automated fashion. could’ve been hacked in the past and was passing out malware. could be this is a copy of someone else’s site and not as benign as it looks. hard to say… trust (or lack thereof) is difficult to establish in an automated fashion.

]]> By: Christian http://labnotes.org/2008/04/13/googlefirefox-blocking-dev-sites/comment-page-1/#comment-140321 Christian Mon, 14 Apr 2008 07:23:09 +0000 http://blog.labnotes.org/?p=1038#comment-140321 Seems Googles spam protection is starting to cause problems several places. We recently had our company blog <a href="http://www.kuttisme.no">kuttisme.no</a> (which mainly deals in online marketing and responsible search engine visibility/"optimization") banned from Google for 30 days more than a month after our Wordpress installation was hacked (and fixed the same day). This all serves to remind us that having a market dominated by one single big player is rarely a good idea :) Seems Googles spam protection is starting to cause problems several places. We recently had our company blog kuttisme.no (which mainly deals in online marketing and responsible search engine visibility/”optimization”) banned from Google for 30 days more than a month after our Wordpress installation was hacked (and fixed the same day).

This all serves to remind us that having a market dominated by one single big player is rarely a good idea :)

]]>