<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Sitemeter issue resolved</title>
	<atom:link href="http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/</link>
	<description>Daily webanalytics news</description>
	<pubDate>Fri, 21 Nov 2008 13:41:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Sal Vincent</title>
		<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29335</link>
		<dc:creator>Sal Vincent</dc:creator>
		<pubDate>Mon, 04 Aug 2008 00:10:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29335</guid>
		<description>Sitemeter fails to test their changes on the world's most popular browser, they deploy those changes untested to hundreds of partners withot warning, and your response is -- "you are all losers, you should switch to Firefox".

Could you be any more clueless and out of touch?  This is the year 2008, and you are still using every pretext to prattle on about how "special" you are just because you use a different browser?  It is getting really old.</description>
		<content:encoded><![CDATA[<p>Sitemeter fails to test their changes on the world&#8217;s most popular browser, they deploy those changes untested to hundreds of partners withot warning, and your response is &#8212; &#8220;you are all losers, you should switch to Firefox&#8221;.</p>
<p>Could you be any more clueless and out of touch?  This is the year 2008, and you are still using every pretext to prattle on about how &#8220;special&#8221; you are just because you use a different browser?  It is getting really old.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29270</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 03 Aug 2008 17:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29270</guid>
		<description>Oh well..site goes down one night on a Friday. Try to call or Microsoft. I think stuff like this happens and people should not make such a big deal about it. My site goes down once in a while and it sucks, but hey...that's life.</description>
		<content:encoded><![CDATA[<p>Oh well..site goes down one night on a Friday. Try to call or Microsoft. I think stuff like this happens and people should not make such a big deal about it. My site goes down once in a while and it sucks, but hey&#8230;that&#8217;s life.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randall</title>
		<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29265</link>
		<dc:creator>Randall</dc:creator>
		<pubDate>Sun, 03 Aug 2008 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29265</guid>
		<description>85% of our traffic uses IE.  Our site was affected at 6:30 pm PDT on Friday.

We had to scrounch around the web to identify the problem, and could not get all pages handled until 6:30 am the following morning.

I do not believe Sitemeter handled this properly, or with any measure of speed.  An announcement could have (and should have) been placed on their site as soon as the problem was recognized.  They could have reversed the coding change, and should have.  I'm sure whoever caused this 'back-end coding' glitch either knew it within minutes, or should have.

I'm sure many sites lost money, with an average downtime of 8 hours or more.  Don't be surprised for sites to start tallying those losses and consider their options for recovery of real damages.

I'm not happy, and do not expect to allow the sitemeter to operate for us again until all their changes (as announced over the next few days) are finished.

How ridiculous to initiate changes without testing in all browsers... irresponsible.</description>
		<content:encoded><![CDATA[<p>85% of our traffic uses IE.  Our site was affected at 6:30 pm PDT on Friday.</p>
<p>We had to scrounch around the web to identify the problem, and could not get all pages handled until 6:30 am the following morning.</p>
<p>I do not believe Sitemeter handled this properly, or with any measure of speed.  An announcement could have (and should have) been placed on their site as soon as the problem was recognized.  They could have reversed the coding change, and should have.  I&#8217;m sure whoever caused this &#8216;back-end coding&#8217; glitch either knew it within minutes, or should have.</p>
<p>I&#8217;m sure many sites lost money, with an average downtime of 8 hours or more.  Don&#8217;t be surprised for sites to start tallying those losses and consider their options for recovery of real damages.</p>
<p>I&#8217;m not happy, and do not expect to allow the sitemeter to operate for us again until all their changes (as announced over the next few days) are finished.</p>
<p>How ridiculous to initiate changes without testing in all browsers&#8230; irresponsible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael J</title>
		<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29223</link>
		<dc:creator>Michael J</dc:creator>
		<pubDate>Sun, 03 Aug 2008 14:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29223</guid>
		<description>Didn't appreciate webmeter taking my business website down with it- no apology, no notification. Had to physically remove the html code from all my pages (137 pages) and it took me three hours. Now it is supposedly fixed. Wonder how many customers and sales that I lost because of this?????</description>
		<content:encoded><![CDATA[<p>Didn&#8217;t appreciate webmeter taking my business website down with it- no apology, no notification. Had to physically remove the html code from all my pages (137 pages) and it took me three hours. Now it is supposedly fixed. Wonder how many customers and sales that I lost because of this?????</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: d.b. echo</title>
		<link>http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29099</link>
		<dc:creator>d.b. echo</dc:creator>
		<pubDate>Sat, 02 Aug 2008 23:05:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/sitemeter/sitemeter-issue-resolved-2/#comment-29099</guid>
		<description>&lt;i&gt;Who uses IE anyways?&lt;/i&gt;

I do.  And 61% of my visitors do, according to my SiteMeter.

But it's probably precisely that sort of attitude that led to SiteMeter implementing this change without bothering to test it with Internet Explorer.

I do love Firefox, though.  The js3250.dll in it bug continues to provide me with a steady stream of visitors searching for ways to fix it.  

http://anothermonkey.blogspot.com/2007/01/computers-bloody-computers-firefox-and.html

When that stream dries up, I'll consider reinstalling Firefox.  Until then, who needs a browser that spontaneously crashes as often as Firefox does?</description>
		<content:encoded><![CDATA[<p><i>Who uses IE anyways?</i></p>
<p>I do.  And 61% of my visitors do, according to my SiteMeter.</p>
<p>But it&#8217;s probably precisely that sort of attitude that led to SiteMeter implementing this change without bothering to test it with Internet Explorer.</p>
<p>I do love Firefox, though.  The js3250.dll in it bug continues to provide me with a steady stream of visitors searching for ways to fix it.  </p>
<p><a href="http://anothermonkey.blogspot.com/2007/01/computers-bloody-computers-firefox-and.html" >http://anothermonkey.blogspot.com/2007/01/computers-bloody-computers-firefox-and.html</a></p>
<p>When that stream dries up, I&#8217;ll consider reinstalling Firefox.  Until then, who needs a browser that spontaneously crashes as often as Firefox does?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
