<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: watching the firefox 3.1 beta 3 release on social media networks</title>
	<atom:link href="http://www.0xdeadbeef.com/weblog/2009/03/watching-the-firefox-31-beta-3-release-on-social-media-networks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.0xdeadbeef.com/weblog/2009/03/watching-the-firefox-31-beta-3-release-on-social-media-networks/</link>
	<description>I love you.</description>
	<lastBuildDate>Wed, 25 Jan 2012 17:08:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Craig</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/03/watching-the-firefox-31-beta-3-release-on-social-media-networks/comment-page-1/#comment-182021</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Sun, 15 Mar 2009 15:57:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1166#comment-182021</guid>
		<description>I love these ideas... I remember when I worked in support (quite a long time ago) and I started creating daily emails on all suspected issues in a new release that was sent to all internal and external support staff.  It greatly sped up identifying suspected issues, collecting info, and subsequently communicating workarounds and fixes following a release.  

And these techniques are great as it allows you to get a handle on issues as quickly as possible, that perhaps weren&#039;t directly reported (or reportable), and get a better idea of impact.  A great benefit of mining social networks (that doesn&#039;t involve trying to market something to me)</description>
		<content:encoded><![CDATA[<p>I love these ideas&#8230; I remember when I worked in support (quite a long time ago) and I started creating daily emails on all suspected issues in a new release that was sent to all internal and external support staff.  It greatly sped up identifying suspected issues, collecting info, and subsequently communicating workarounds and fixes following a release.  </p>
<p>And these techniques are great as it allows you to get a handle on issues as quickly as possible, that perhaps weren&#8217;t directly reported (or reportable), and get a better idea of impact.  A great benefit of mining social networks (that doesn&#8217;t involve trying to market something to me)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Kwong</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/03/watching-the-firefox-31-beta-3-release-on-social-media-networks/comment-page-1/#comment-181742</link>
		<dc:creator>Gary Kwong</dc:creator>
		<pubDate>Sat, 14 Mar 2009 05:30:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1166#comment-181742</guid>
		<description>&gt; Then the devnews post is replicated on the Mozilla Blog, so there are *two* non-inviting pages telling people to link only to them.

I find this weird too, the Mozilla Blog usually dupes the info on Devnews, and doesn&#039;t offer anything else useful.</description>
		<content:encoded><![CDATA[<p>&gt; Then the devnews post is replicated on the Mozilla Blog, so there are *two* non-inviting pages telling people to link only to them.</p>
<p>I find this weird too, the Mozilla Blog usually dupes the info on Devnews, and doesn&#8217;t offer anything else useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Ruderman</title>
		<link>http://www.0xdeadbeef.com/weblog/2009/03/watching-the-firefox-31-beta-3-release-on-social-media-networks/comment-page-1/#comment-181667</link>
		<dc:creator>Jesse Ruderman</dc:creator>
		<pubDate>Fri, 13 Mar 2009 19:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.0xdeadbeef.com/weblog/?p=1166#comment-181667</guid>
		<description>I think we could do a better job of having a &quot;canonical URL&quot; for beta releases.

At least on delicious, most people link to the all-beta page, since it&#039;s pretty and has a prominent download link.  But that page doesn&#039;t do a great job of telling you what&#039;s new or what to be careful about.

Then there&#039;s the devnews post, which tells people to link to it but is much less inviting.  It&#039;s a bunch of text, most of which is irrelevant to many beta users.  It emphasizes warnings in too many ways, which ends up annoying me more than drawing my attention to them.  And it tries to encourage users to read the release notes, which as even longer and lower signal-to-noise.

Then the devnews post is replicated on the Mozilla Blog, so there are *two* non-inviting pages telling people to link only to them.</description>
		<content:encoded><![CDATA[<p>I think we could do a better job of having a &#8220;canonical URL&#8221; for beta releases.</p>
<p>At least on delicious, most people link to the all-beta page, since it&#8217;s pretty and has a prominent download link.  But that page doesn&#8217;t do a great job of telling you what&#8217;s new or what to be careful about.</p>
<p>Then there&#8217;s the devnews post, which tells people to link to it but is much less inviting.  It&#8217;s a bunch of text, most of which is irrelevant to many beta users.  It emphasizes warnings in too many ways, which ends up annoying me more than drawing my attention to them.  And it tries to encourage users to read the release notes, which as even longer and lower signal-to-noise.</p>
<p>Then the devnews post is replicated on the Mozilla Blog, so there are *two* non-inviting pages telling people to link only to them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

