<?xml version="1.0"?>
<!-- RSS generated by OPML Editor version 0.72 on 8/29/07; 10:59:53 AM Pacific -->
<rss version="2.0">
	<channel>
		<title>Scripting News</title>
		<link>http://www.scripting.com/</link>
		<description>It's even worse than it appears.</description>
		<language>en-us</language>
		<copyright>Copyright 1997-2007 Dave Winer</copyright>
		<pubDate>Wed, 29 Aug 2007 07:00:00 GMT</pubDate>
		<lastBuildDate>Wed, 29 Aug 2007 17:59:53 GMT</lastBuildDate>
		<docs>http://blogs.law.harvard.edu/tech/rss</docs>
		<generator>OPML Editor version 0.72</generator>
		<managingEditor>dave@scripting.com</managingEditor>
		<webMaster>dave@scripting.com</webMaster>
		<item>
			<title>Working with reporters</title>
			<link>http://www.scripting.com/stories/2007/08/29/workingWithReporters.html</link>
			<description>
				&lt;p&gt;&lt;img src=&quot;http://images.scripting.com/archiveScriptingCom/2007/08/29/bigGulp.jpg&quot; width=&quot;95&quot; height=&quot;153&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named bigGulp.jpg&quot;&gt;More and more reporters are accepting that a blog can be a good source of quotes. For example, today there's an interesting &lt;a href=&quot;http://machinist.salon.com/feature/2007/08/29/blockbuster_netflix/&quot;&gt;piece&lt;/a&gt; in Salon, explaining why Blockbuster is gaining on Netflix. It showed up in my referrer log, so I was pretty sure I was quoted.&lt;/p&gt;
				&lt;p&gt;I got the closing quote in the story, and it's a good one, an observation I'm proud of. I'm also happy with the way it was said. It was transcribed perfectly, because copy/paste is error-free, where a reporter grabbing soundbites in a phone interview is likely to make mistakes.&lt;/p&gt;
				&lt;p&gt;Here's the quote. &lt;i&gt;&quot;It may not be obvious, but Netflix is a social network, and the more the networks open and let the user's data be portable, the more power it gives developers to do interesting things with the data,&quot; Winer wrote. &quot;Netflix has always had a great attitude about customers. It would make sense for them to be the first to trust us with our own data.&quot;&lt;/i&gt;&lt;/p&gt;
				&lt;p&gt;I stopped doing interviews about a year ago. As a result, I haven't gotten quoted as often as I used to, but I'd prefer to not be quoted than to be quoted saying something stupid, dishonest or wrong. The reporter's filters really get in the way. Their assumption that everyone they interview is selling something, or lying to them, or hiding the truth really screws up the process.&lt;/p&gt;
				&lt;p&gt;Also, I like the quote beacuse it shows that interesting stuff happened at Gnomedex that wasn't about you-know-who. &lt;img src=&quot;http://www.scripting.com/gifs/QBullets/qbullets/sidesmiley.gif&quot; width=&quot;11&quot; height=&quot;11&quot; border=&quot;0&quot; alt=&quot;smile&quot;&gt;&lt;/p&gt;
				&lt;p&gt;PS: Mike at &lt;a href=&quot;http://www.hackingnetflix.com/2007/08/salon-on-the-ne.html&quot;&gt;Hacking Netflix&lt;/a&gt; was misquoted in Salon after a phone interview. It was a big misquote (he said he waited for Netflix for 3 months, they quoted him as saying he waited for Blockbuster). And how ironic that Mike misquoted me, saying that I do interviews only email. I didn't say that and I &lt;i&gt;never&lt;/i&gt; do interviews by email. &lt;/p&gt;
				</description>
			<pubDate>Wed, 29 Aug 2007 15:16:14 GMT</pubDate>
			<guid>http://www.scripting.com/stories/2007/08/29/workingWithReporters.html</guid>
			</item>
		<item>
			<title>We fact check your ass</title>
			<link>http://www.scripting.com/stories/2007/08/29/weFactCheckYourAss.html</link>
			<description>
				&lt;p&gt;&lt;img src=&quot;http://images.scripting.com/archiveScriptingCom/2007/08/29/gecko.jpg&quot; width=&quot;114&quot; height=&quot;249&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named gecko.jpg&quot;&gt;I don't know what Scoble is up to, but he's my friend, not just the business kind of friend. So it's my job to help him get back on track, or find out why I'm wrong, so I can get back on track. &lt;/p&gt;
				&lt;p&gt;The title of this piece &quot;We fact check your ass&quot; was a synthesis from the early days of blogging. There are a few key ideas about blogging in that short phrase.&lt;/p&gt;
				&lt;p&gt;1. There are many of us.&lt;/p&gt;
				&lt;p&gt;2. We care about the truth.&lt;/p&gt;
				&lt;p&gt;3. We use colorful language. &lt;img src=&quot;http://www.scripting.com/gifs/QBullets/qbullets/sidesmiley.gif&quot; width=&quot;11&quot; height=&quot;11&quot; border=&quot;0&quot; alt=&quot;smile&quot;&gt;&lt;/p&gt;
				&lt;p&gt;So this leads to a bunch of good blogger behavior, stuff Scoble knows about, stuff Scoble has evangelized. A person who puts his ideas out there takes the risk of putting out &lt;i&gt;incorrect&lt;/i&gt; ideas, but that's not a problem if there are lots of people fact checking his or her ass.&lt;/p&gt;
				&lt;p&gt;So here's what you should do when you say something that's incorrect. As soon as you realize it, correct it. Maybe offer an explanation, but that seems optional. But first and foremost, fix the bug.&lt;/p&gt;
				&lt;p&gt;Everyone is telling him this, but he's not getting the message. Simply say &quot;I made a mistake&quot; and every piece from this point on won't have to guess what happened. &lt;/p&gt;
				&lt;p&gt;PS: TwitterGram &lt;a href=&quot;http://twitter.com/davewiner/statuses/234777962&quot;&gt;explaining&lt;/a&gt; this in my own voice.&lt;/p&gt;
				&lt;p&gt;PPS: Wired &lt;a href=&quot;http://blog.wired.com/business/2007/08/trend-debunking.html&quot;&gt;piece&lt;/a&gt; posted late yesterday.&lt;/p&gt;
				</description>
			<pubDate>Wed, 29 Aug 2007 13:18:36 GMT</pubDate>
			<guid>http://www.scripting.com/stories/2007/08/29/weFactCheckYourAss.html</guid>
			</item>
		</channel>
	</rss>
