<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bokardo &#187; blogging</title>
	<atom:link href="http://bokardo.com/tag/blogging/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Sun, 29 Jan 2012 11:35:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Why people don&#8217;t trust &#8220;bloggers&#8221;</title>
		<link>http://bokardo.com/archives/why-people-dont-trust-bloggers/</link>
		<comments>http://bokardo.com/archives/why-people-dont-trust-bloggers/#comments</comments>
		<pubDate>Wed, 30 Apr 2008 12:31:48 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/?p=762</guid>
		<description><![CDATA[Jeremiah Owyang claims that people don&#8217;t trust bloggers. To back up this claim, he cites three market research studies showing that when given a choice, people would choose to listen to their friends and family rather than &#8220;bloggers&#8221;. The three studies were done by respected marketing research companies: Forrester, Edelman, and Pollara. They all agree [...]]]></description>
			<content:encoded><![CDATA[<p>Jeremiah Owyang claims that <a href="http://www.web-strategist.com/blog/2008/04/29/who-do-people-trust-it-aint-bloggers/">people don&#8217;t trust bloggers</a>. To back up this claim, he cites three market research studies showing that when given a choice, people would choose to listen to their friends and family rather than &#8220;bloggers&#8221;.</p>
<p>The three studies were done by respected marketing research companies: Forrester, Edelman, and Pollara. They all agree on the same thing: that bloggers just don&#8217;t elicit much trust when compared to other sources of information. </p>
<p>I can&#8217;t help but think that these studies weighted the questions&#8230;<em>oh just a little bit</em>. I mean, who would trust someone based solely on the fact that they happen to write a blog? Does merely creating a blogger account and whipping out a few blog posts make one a trusted authority on&#8230;anything? Of course not.  </p>
<p>It&#8217;s kind of like asking: &#8220;Who do you trust more: a family member or someone who can use wordpress?&#8221;. The question just doesn&#8217;t teach us anything new. So the reason why people don&#8217;t trust &#8220;bloggers&#8221; in the context of these studies is because they don&#8217;t know who those bloggers are. </p>
<p>Now, Jeremiah&#8217;s point was to push back on the unfortunate conventional wisdom that merely writing a blog means you&#8217;re having an authentic conversation with an audience. This focus on technology over interaction is <a href="http://bokardo.com/archives/the-problem-with-social-media-marketing/">the problem with social media marketing</a>, and Jeremiah was right to push back on that. But I don&#8217;t believe that bloggers don&#8217;t have trust. Of course bloggers have some level of trust. The people who trust them are their audience. (I&#8217;m sure Jeremiah sure hopes that his audience trusts him) </p>
<p>So, if instead of asking a meaningless question these studies asked &#8220;Do you trust bloggers who you read regularly/subscribe to?&#8221; most people would answer that they do. But that&#8217;s not what the studies asked&#8230;they asked about a faceless, nameless, random blogger. Not only is this a poor question, but it puts the entire studies under a shadow of doubt. It&#8217;s almost as if the question were asked just so that the researchers could come to that conclusion. </p>
<p>What bloggers don&#8217;t have, and what the studies might show, is <em>automatic</em> trust. Joe Blogger doesn&#8217;t automatically have permission to talk to you simply because he knows how to use WordPress. Blogging is about relationships, like most of life, and you need to earn any respect and permission you get. </p>
<p>There are few shortcuts here. But let&#8217;s not swing the pendulum completely the other way and suggest that bloggers aren&#8217;t trusted at all. The reality is that you have to prove yourself with each action, over time, building up trust and experience slowly, steadily. If it were any other way, then the word trust wouldn&#8217;t mean anything. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/why-people-dont-trust-bloggers/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Why I&#8217;m excited about the Google Social Graph API</title>
		<link>http://bokardo.com/archives/why-im-excited-about-the-google-social-graph-api/</link>
		<comments>http://bokardo.com/archives/why-im-excited-about-the-google-social-graph-api/#comments</comments>
		<pubDate>Sun, 03 Feb 2008 14:33:24 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[Amazon]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Social Design]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/why-im-excited-about-the-google-social-graph-api/</guid>
		<description><![CDATA[The <a href="http://code.google.com/apis/socialgraph/">Google Social Graph API</a> is a new programming API that allows developers to expose social relationships embedded in web sites. What does this mean for regular folks like you and me? Read on. 

Do you ever feel like your personal information is spread across the web in a whole bunch of separate places? An account here, a profile there? A friends list here and a friends list there? All your information, but in all different places all incomplete at the same time? 

<img src="http://bokardo.com/images/social-graph-api.gif" alt="Google Social Graph API" style="float:right;margin:0 0 10px 100px;" />

The Social Graph API helps solve this "silos of information" problem by allowing people to write software that understands who your friends are. It does this by reading your web site or blog and making connections between the social profiles you have across the web. 

For example, imagine you have a blog, which is your home on the web. You also have an Amazon profile, a Twitter profile, and a Facebook profile. So you have four profiles spread across the web, seemingly unconnected. Amazon has no idea who your friends on Facebook or Twitter are, and vice-versa, and this is a good thing from a privacy standpoint. These sites shouldn't be able to find out everything about you with you giving them permission.

But what if you wanted these sites to know a bit about each other? What if you want to combine your Amazon book history with your friends lists at Facebook so that you can see what your friends are reading and let Amazon give you recommendations based on your similarity with them? Or, perhaps you just joined Twitter and want to know which of your Facebook friends are already there so you don't have to go hunting for them? (see <a href="http://code.google.com/apis/socialgraph/">video</a>) Here we see real-world examples of how cross-pollinating your personal information between these sites can not only be efficient, but desirable...]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://code.google.com/apis/socialgraph/">Google Social Graph API</a> is a new programming API that allows developers to expose social relationships embedded in web sites. What does this mean for regular folks like you and me? Read on. </p>
<p>Do you ever feel like your personal information is spread across the web in a whole bunch of separate places? An account here, a profile there? A friends list here and a friends list there? All your information, but in all different places all incomplete at the same time? </p>
<p><img src="http://bokardo.com/images/social-graph-api.gif" alt="Google Social Graph API" style="float:right;margin:0 0 10px 100px;" /></p>
<p>The Social Graph API helps solve this &#8220;silos of information&#8221; problem by allowing people to write software that understands who your friends are. It does this by reading your web site or blog and making connections between the social profiles you have across the web. </p>
<p>For example, imagine you have a blog, which is your home on the web. You also have an Amazon profile, a Twitter profile, and a Facebook profile. So you have four profiles spread across the web, seemingly unconnected. Amazon has no idea who your friends on Facebook or Twitter are, and vice-versa, and this is a good thing from a privacy standpoint. These sites shouldn&#8217;t be able to find out everything about you with you giving them permission.</p>
<p>But what if you wanted these sites to know a bit about each other? What if you want to combine your Amazon book history with your friends lists at Facebook so that you can see what your friends are reading and let Amazon give you recommendations based on your similarity with them? Or, perhaps you just joined Twitter and want to know which of your Facebook friends are already there so you don&#8217;t have to go hunting for them? (see <a href="http://code.google.com/apis/socialgraph/">video</a>) Here we see real-world examples of how cross-pollinating your personal information between these sites can not only be efficient, but desirable. (Not everyone will want to do this, however)</p>
<p>This type of scenario is what the Google Social Graph API is going to help solve. It does this by reading information on your blog that describes your other online profiles. So you might declare that you have a Twitter profile at <a href="http://twitter.com/bokardo">http://twitter.com/bokardo</a> or you have a Facebook profile at <a href="http://www.facebook.com/profile.php?id=500576058">http://www.facebook.com/profile.php?id=500576058</a>. Now, given your permission, Amazon can go out and find your Twitter friends and perhaps make book recommendations to you. Or, when you join a new social network, you can simply add your friends from existing networks with the click of a button. </p>
<p>So that&#8217;s the big reason why I&#8217;m excited by the Social Graph API: it helps to solve a real tough problem brought on by the proliferation of social networks. But there are several more reasons, too: </p>
<h2>No Dependence on Google (or anyone else)</h2>
<p>While Google is providing the API, nobody is dependent on them for creating or storing our relationships. This is done by the individual (as well as the services we sign up for). This means that Google isn&#8217;t in control of our relationship content. This is very much like how Search works. We own the content that we write on our web site. Google simply indexes it and provides tools to find, filter, and sort it. Google is an aggregator, not a creator. Google will be in competition to have the best aggregator of the graph. </p>
<p>The best way to explain this might be to point out that others can do exactly what Google is doing here. Since the relationship information is embedded within web sites <em>anybody</em> can index this information. So competitors can come along and try to provide a better API or better tools than Google. </p>
<h2>Not a Walled Garden like Facebook</h2>
<p>As <a href="http://www.buzzmachine.com/2008/02/02/the-internet-is-the-social-network/">Jeff Jarvis says</a>: &#8220;<em>The internet is the social network</em>&#8220;. Walled gardens are not. Facebook is a great place to socialize. But they don&#8217;t own the relationships that happen there. Unlike Facebook, Google isn&#8217;t trying to own our social graph. This is incredibly important for the openness of the web. (btw: Jeff doesn&#8217;t think XFN and FOAF will gain traction&#8230;but I think they will because they are easy to implement and because solving this problem is too important. RSS and trackbacks are two technologies that succeeded in the same way) </p>
<p>This is in contrast to how Facebook runs things, which is by their permission. They want to own the relationship data. That&#8217;s why this API by Google is, to me, still a far better alternative. They are simply providing the best tool and keeping competition open. </p>
<p>A good indicator of this is to take a look at the first words on the Social Graph API: &#8220;Build critical mass on your website&#8221;. Would these words ever show up on anything by FB? NO. Their words would be &#8220;Build critical mass on <em>our</em> website&#8221;. </p>
<h2>Based on Open Standards</h2>
<p>The social relationships that the API exposes are encoded in regular old HTML using the XFN and FOAF formats. These are open standards that anybody can use. These are very easy to write and understand. Web developers will be able to learn what they need to in about 5 minutes in order to write these formats. Go HTML!</p>
<p>It will take a bit longer for blog publishers to write plugins that publish these formats for us, so that non-developers can publish their relationships as well. But with the amazing number of developers already creating plugins and other extensions, this won&#8217;t be a problem. </p>
<h2>An Ecosystem</h2>
<p>The Social Graph API is an ecosystem that anybody can play in. Since the relationship data is available to anybody, the spoils will go to the best tools that take advantage of them. Thus we have an ecosystem of open competition that allows anybody to play. Anybody with some spare time on their hands can jump in and create some cool program that helps people stay in better touch with their friends or somehow leverages those relationships. This move by Google cements their belief in the web as platform and reinforces their corporate mission to &#8220;help organize the world&#8217;s information&#8221;. </p>
<h2>APIs are Great</h2>
<p>This move by Google underscores the importance of APIs. The best thing about APIs is that we simply don&#8217;t know (and can&#8217;t imagine) how useful they can be. Developers will undoubtedly dream up a myriad of ways to use the API, some of which will become killer applications. The power of APIs is not what we can see plainly, but what we can&#8217;t see quite yet. </p>
<h2>The User is in Charge</h2>
<p>This is the biggest part of why I&#8217;m excited. My personal relationship information isn&#8217;t behind some walled garden. I&#8217;m in control of my own social graph! If I want people to know <a href="http://twitter.com/bokardo">I have a Twitter account</a>, then I can. If I don&#8217;t want them to be sure then I won&#8217;t make that relationship explicit on my blog.</p>
<h2>The Domain as Identity is Realized</h2>
<p>I don&#8217;t write about it often, but you may remember some posts about <a href="http://bokardo.com/archives/domain-as-identity/">domain as identity</a> I&#8217;ve written in the past. The Google Social Graph API is now getting us there by recognizing when we define our own relationships in our own domain. As more and more services look to our domain for verification, that only puts us more in charge of our online identity. Combine this with <a href="http://openid.net">OpenID</a>, and the idea of domain as identity really takes shape. </p>
<p>In the same way that we are in control of our own bodies, we need to be in control of our own domains. This is how we&#8217;re going to get privacy, if we want it. If you feel that you&#8217;re not in control of your domain, then you need to take your business elsewhere. This is why I dislike services that require you to have a subdomain within some other domain&#8230;those services that let you use your own domain are far preferable because you can at any point move your domain elsewhere. Just like you move your residence IRL. </p>
<h2>What do I need to do?</h2>
<p>So where does this leave us? Well, it leaves us with two very obvious next steps. </p>
<ol>
<li>Get your own domain! &#8211; if you don&#8217;t have your own domain&#8230;go get one! (and not a subdomain)</li>
<li>Mark up your code &#8211; use the XFN and FOAF formats to markup your site, or use a service that does this for you. I seriously need to do this myself. (I have a FOAF file, that&#8217;s about it)</li>
</ol>
<p>It won&#8217;t be long before developers take advantage of the Social Graph API to really leverage these relationships. There is already software taking advantage of the API. Google has provided some tools that allow you to <a href="http://socialgraph-resources.googlecode.com/svn/trunk/samples/findcontacts.html">discover your contacts</a>. Play around with this and you can see the power of this API. We might actually have some coherence to personal information on the web after all.</p>
<h2>Going forward</h2>
<p>The truth is that Facebook, Amazon, or even Twitter never had a good glimpse of my true social network anyway. Therefore, they had an incomplete social graph. I never gave Facebook my email list, they don&#8217;t know anything about my blog, and I&#8217;m going to keep it that way. While Facebook and others can create a fun place to hang out, they don&#8217;t own the relationships I create there. I do. </p>
<p>Also, it should be pointed out that Google released the Social Graph API on the same day that Microsoft announced their intention to take over Yahoo. The irony of this can&#8217;t be more complete. </p>
<p>One is a sign of the past. One is a sign of the future. </p>
<p><strong>Update:</strong> <a href="http://bokardo.com/archives/the-danger-of-social-markers-made-public/">Discussion on privacy implications of the Social Graph API</a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/why-im-excited-about-the-google-social-graph-api/feed/</wfw:commentRss>
		<slash:comments>32</slash:comments>
		</item>
		<item>
		<title>Making private identity public</title>
		<link>http://bokardo.com/archives/making-private-identity-public/</link>
		<comments>http://bokardo.com/archives/making-private-identity-public/#comments</comments>
		<pubDate>Wed, 31 Oct 2007 13:55:23 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/making-private-identity-public/</guid>
		<description><![CDATA[Chris Anderson, editor in chief at Wired, has <a href="http://www.longtail.com/the_long_tail/2007/10/sorry-pr-people.html">published a list of 329 email addresses</a> that have been used to send him PR SPAM in the last month. He says he's fed up: 

<blockquote>"I've had it. I get more than 300 emails a day and my problem isn't spam, it's PR people. Lazy flacks send press releases to the Editor in Chief of Wired because they can't be bothered to find out who on my staff, if anyone, might actually be interested in what they're pitching."</blockquote>

Being someone who gets a small amount of PR SPAM (~10 a day), I certainly sympathize with Anderson's move here. It's  tiresome to spend valuable time weeding through emails that at first seem addressed to you, until you realize they're simply sent to a huge list of bloggers. They're not personal messages. They're generic. Some PR folks even lie and say "I've been reading your blog and I love everything you write, your child is beautiful, and may your family receive honor forever...etc...etc". But after that it quickly becomes clear that they never refer to my blog specifically and they never tell me anything related to the topics I write about. It's not informing. It's insulting.

Here's an example of one I got the other day. It's not nearly as bad as some, but just as useless. It starts out...]]></description>
			<content:encoded><![CDATA[<p>Chris Anderson, editor in chief at Wired, has <a href="http://www.longtail.com/the_long_tail/2007/10/sorry-pr-people.html">published a list of 329 email addresses</a> that have been used to send him PR SPAM in the last month. He says he&#8217;s fed up: </p>
<blockquote><p>&#8220;I&#8217;ve had it. I get more than 300 emails a day and my problem isn&#8217;t spam, it&#8217;s PR people. Lazy flacks send press releases to the Editor in Chief of Wired because they can&#8217;t be bothered to find out who on my staff, if anyone, might actually be interested in what they&#8217;re pitching.&#8221;</p></blockquote>
<p>Being someone who gets a small amount of PR SPAM (~10 a day), I certainly sympathize with Anderson&#8217;s move here. It&#8217;s  tiresome to spend valuable time weeding through emails that at first seem addressed to you, until you realize they&#8217;re simply sent to a huge list of bloggers. They&#8217;re not personal messages. They&#8217;re generic. Some PR folks even lie and say &#8220;I&#8217;ve been reading your blog and I love everything you write, your child is beautiful, and may your family receive honor forever&#8230;etc&#8230;etc&#8221;. But after that it quickly becomes clear that they never refer to my blog specifically and they never tell me anything related to the topics I write about. It&#8217;s not informing. It&#8217;s insulting.</p>
<p>Here&#8217;s an example of one I got the other day. It&#8217;s not nearly as bad as some, but just as useless. It starts out: </p>
<blockquote><p>Joshua,</p>
<p>Hope you had a great weekend. I wanted to give you a heads up on this great partnership StreetAdvisor is announcing this week with Australiaâ€™s top real estate website realestate.com.au. REA has tapped StreetAdvisor to give homebuyers, owners, renters and real estate agents with a great tool to help find the right property, in the right neighborhood.</p>
</blockquote>
<p>And my question is: &#8220;How is this in any way valuable to me or my audience?&#8221;. No doubt Anderson asks a similar question when he gets SPAM. </p>
<p>Anderson&#8217;s response is a good lesson in a common problem with Identity on the Web. When Identity is known, behavior becomes civilized very quickly. When identity is not known, or not public as the case may be, behavior turns ugly. </p>
<p>When PR people send these broadcast emails, their identity is known to the receiver, but <em>only the receiver</em>. They rely on that fact to try to encourage the receiver to publish something about them (be it in Wired or on Bokardo). They take the chance that you&#8217;ll be fooled into thinking their information is worth publishing, <em>while also realizing that if not you&#8217;ll probably ignore it</em>. This last bit is crucial&#8230;the spammers expect certain behavior from the receivers&#8230;most spammers know that a large majority of people will simply ignore what they send. </p>
<p>But Anderson took the matter into his own hands and made the identities of those PR spammers public, and thereby changed the normal rules of engagement. </p>
<p>Now, he&#8217;s opened up their behavior for public scrutiny. He&#8217;s allowing other people to offer their judgment. The effect that this will have is that those email addresses will probably be ignored or blacklisted even more often than they currently are. He&#8217;s hoping that by making an example of these people they&#8217;ll change their behavior in the future. </p>
<p>You&#8217;ll notice the commenters on Anderson&#8217;s piece are divided over this. There are people who are cheering him, saying &#8220;way to go!&#8221;. There are also people (presumably people who are on the list) who are saying &#8220;get over yourself&#8221;. </p>
<p>This is public ridicule at its best, and it&#8217;s one of the few ways to combat private solicitation. When Anderson makes a formerly private relationship (one he didn&#8217;t want anyway) public, he knows that the public will label this as bad behavior.   </p>
<p>Most large-scale spammers aren&#8217;t trying to create a real relationship, so they don&#8217;t have to use real email addresses. But PR people usually have to use their real addresses because they do want a real relationship with the receiver. Little do they realize how annoying their solicitation is&#8230;perhaps Anderson&#8217;s move will wizen them up.</p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/making-private-identity-public/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>It&#8217;s Just People Talking</title>
		<link>http://bokardo.com/archives/its-just-people-talking/</link>
		<comments>http://bokardo.com/archives/its-just-people-talking/#comments</comments>
		<pubDate>Thu, 07 Jun 2007 10:20:02 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/its-just-people-talking/</guid>
		<description><![CDATA[Was reading <a href="http://epeus.blogspot.com/2007/06/keening-for-culture.html">Kevin Marks' thoughts</a> on the <a href="http://bokardo.com/archives/cult-of-the-pundit/">Cult of the <strike>Amateur</strike> Pundit</a> and found this gem from Hitchiker's Guide author Douglas Adams in <a href="http://www.douglasadams.com/dna/19990901-00-a.html">How to Stop Worrying and Love the Internet</a>

<blockquote><p>"Because the Internet is so new we still donâ€™t really understand what it is. We mistake it for a type of publishing or broadcasting, because thatâ€™s what weâ€™re used to. So people complain that thereâ€™s a lot of rubbish online, or that itâ€™s dominated by Americans, or that you canâ€™t necessarily trust what you read on the web. Imagine trying to apply any of those criticisms to what you hear on the telephone. Of course you canâ€™t â€˜trustâ€™ what people tell you on the web anymore than you can â€˜trustâ€™ what people tell you on megaphones, postcards or in restaurants. Working out the social politics of who you can trust and why is, quite literally, what a very large part of our brain has evolved to do. For some batty reason we turn off this natural scepticism when we see things in any medium which require a lot of work or resources to work in, or in which we canâ€™t easily answer back â€“ like newspapers, television or granite. Hence â€˜carved in stone.â€™ What should concern us is not that we canâ€™t take what we read on the internet on trust â€“ of course you canâ€™t, itâ€™s just people talking â€“ but that we ever got into the dangerous habit of believing what we read in the newspapers or saw on the TV â€“ a mistake that no one who has met an actual journalist would ever make. One of the most important things you learn from the internet is that there is no â€˜themâ€™ out there. Itâ€™s just an awful lot of â€˜usâ€™."</p></blockquote>]]></description>
			<content:encoded><![CDATA[<p>Was reading <a href="http://epeus.blogspot.com/2007/06/keening-for-culture.html">Kevin Marks&#8217; thoughts</a> on the <a href="http://bokardo.com/archives/cult-of-the-pundit/">Cult of the <strike>Amateur</strike> Pundit</a> and found this gem from Hitchiker&#8217;s Guide author Douglas Adams in <a href="http://www.douglasadams.com/dna/19990901-00-a.html">How to Stop Worrying and Love the Internet</a></p>
<blockquote><p>&#8220;Because the Internet is so new we still donâ€™t really understand what it is. We mistake it for a type of publishing or broadcasting, because thatâ€™s what weâ€™re used to. So people complain that thereâ€™s a lot of rubbish online, or that itâ€™s dominated by Americans, or that you canâ€™t necessarily trust what you read on the web. Imagine trying to apply any of those criticisms to what you hear on the telephone. Of course you canâ€™t â€˜trustâ€™ what people tell you on the web anymore than you can â€˜trustâ€™ what people tell you on megaphones, postcards or in restaurants. Working out the social politics of who you can trust and why is, quite literally, what a very large part of our brain has evolved to do. For some batty reason we turn off this natural scepticism when we see things in any medium which require a lot of work or resources to work in, or in which we canâ€™t easily answer back â€“ like newspapers, television or granite. Hence â€˜carved in stone.â€™ What should concern us is not that we canâ€™t take what we read on the internet on trust â€“ of course you canâ€™t, itâ€™s just people talking â€“ but that we ever got into the dangerous habit of believing what we read in the newspapers or saw on the TV â€“ a mistake that no one who has met an actual journalist would ever make. One of the most important things you learn from the internet is that there is no â€˜themâ€™ out there. Itâ€™s just an awful lot of â€˜usâ€™.&#8221;</p>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/its-just-people-talking/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Two Great Videos in Plain English</title>
		<link>http://bokardo.com/archives/two-great-videos-in-plain-english/</link>
		<comments>http://bokardo.com/archives/two-great-videos-in-plain-english/#comments</comments>
		<pubDate>Wed, 06 Jun 2007 12:16:22 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/two-great-videos-in-plain-english/</guid>
		<description><![CDATA[Lee Lefever over at <a href="http://www.commoncraft.com/">Common Craft</a> has posted two nice videos about how and why to use new technology. Lee, who is also using the term "social design", is obviously aware that not everybody is on the social media bandwagon yet. These videos are a great primer for folks who want an explanation of what RSS and Wikis <em>actually are</em>. They're fun, too. 

<h2>RSS in Plain English</h2>

<object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/0klgLsSxGsU"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/0klgLsSxGsU" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object>]]></description>
			<content:encoded><![CDATA[<p>Lee Lefever over at <a href="http://www.commoncraft.com/">Common Craft</a> has posted two nice videos about how and why to use new technology. Lee, who is also using the term &#8220;social design&#8221;, is obviously aware that not everybody is on the social media bandwagon yet. These videos are a great primer for folks who want an explanation of what RSS and Wikis <em>actually are</em>. They&#8217;re fun, too. </p>
<h2>RSS in Plain English</h2>
<p><object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/0klgLsSxGsU"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/0klgLsSxGsU" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object></p>
<h2>Wikis in Plain English</h2>
<p><object width="425" height="350"><param name="movie" value="http://www.youtube.com/v/-dnL00TdmLY"></param><param name="wmode" value="transparent"></param><embed src="http://www.youtube.com/v/-dnL00TdmLY" type="application/x-shockwave-flash" wmode="transparent" width="425" height="350"></embed></object></p>
<p>Lee is doing some <a href="http://www.commoncraft.com/">great work</a>, focusing on the implications of social media for communities. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/two-great-videos-in-plain-english/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Cult of the Pundit</title>
		<link>http://bokardo.com/archives/cult-of-the-pundit/</link>
		<comments>http://bokardo.com/archives/cult-of-the-pundit/#comments</comments>
		<pubDate>Wed, 30 May 2007 11:46:25 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/cult-of-the-pundit/</guid>
		<description><![CDATA[<em>When are we going to acknowledge that millions of people writing poorly (while slowly improving) is better than millions of people doing the alternative...not writing at all?</em>

You hear the argument all the time: bloggers are poor writers who produce mountains of useless prose and very little quality work. The most recent case is Neil Henry's <a href="http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2007/05/29/EDGFKQ20N61.DTL">The Decline of News</a>, in which he makes the following insult to bloggers:

<blockquote><p>"Meantime, I can't help but fear a future, increasingly barren of skilled journalists, in which Google "news" searches turn up not news, but the latest snarky rants from basement bloggers..."</p></blockquote>]]></description>
			<content:encoded><![CDATA[<p><em>When are we going to acknowledge that millions of people writing poorly (while slowly improving) is better than millions of people doing the alternative&#8230;not writing at all?</em></p>
<p>You hear the argument all the time: bloggers are poor writers who produce mountains of useless prose and very little quality work. The most recent case is Neil Henry&#8217;s <a href="http://www.sfgate.com/cgi-bin/article.cgi?file=/chronicle/archive/2007/05/29/EDGFKQ20N61.DTL">The Decline of News</a>, in which he makes the following insult to bloggers:</p>
<blockquote><p>&#8220;Meantime, I can&#8217;t help but fear a future, increasingly barren of skilled journalists, in which Google &#8220;news&#8221; searches turn up not news, but the latest snarky rants from basement bloggers&#8230;&#8221;</p>
</blockquote>
<p>Clay Shirky reiterates a similar sentiment, in <a href="http://many.corante.com/archives/2007/05/24/what_are_we_going_to_say_about_cult_of_the_amateur.php">a post defending Andrew Keen&#8217;s controversial book Cult of the Amateur</a>, that there is too much poor content out there:</p>
<blockquote><p>&#8220;talent is unevenly distributed, and everyone knows it. Indeed, one of the many great things about the net is that talent can now express itself outside traditional frameworks; this extends to blogging, of course, but also to music, as Clive Thompson described in his <a href="http://www.nytimes.com/2007/05/13/magazine/13audience-t.html?ex=1336708800&#038;en=1d5b472eddd4dcad&#038;ei=5124&#038;partner=permalink&#038;exprod=permalink">great NY Times piece</a>, or to software, as with Linusâ€™ talent as an OS developer, and so on. The price of this, however, is that the amount of poorly written or produced material has expanded a million-fold. Increased failure is an inevitable byproduct of increased experimentation, and finding new filtering methods for dealing with an astonishingly adverse signal-to-noise ratio is the great engineering challenge of our age&#8221;</p>
</blockquote>
<p>But what about the increase in good writing as well? What about those blogs that are about that one topic that you find fascinating&#8230;the blog that <em>couldn&#8217;t have existed</em> 8 years ago, and now you can&#8217;t live without? Why aren&#8217;t we celebrating those more? Why so much focus on the negative aspects and not the positive ones?</p>
<p>I find the &#8220;cult of the amateur&#8221; argument tiresome. Sure, we have a huge increase in content, and, following the <a href="http://en.wikipedia.org/wiki/Power_law">power law</a>, most of it won&#8217;t be relevant to <em>you</em> or <em>me</em>. But that doesn&#8217;t mean its not relevant to <em>somebody</em>. </p>
<h2>People read blogs for one of two reasons</h2>
<p>You see, most people read blogs for one of two reasons: they know the person writing it or they&#8217;re interested in the topic the person is writing about, or both. That&#8217;s why, when you ask any person about the average value of content on the web, they say &#8220;it&#8217;s useless&#8221;, because most content isn&#8217;t by people we know and isn&#8217;t about the relatively few topics we&#8217;re interested in. </p>
<p>To that end, those millions of personal blogs where someone is writing about their daily routine that in no way could ever interest you probably have a family member or friend who <em>is</em> interested, and  who doesn&#8217;t care if they spell everything right or could use a grammar refresher. In addition, a whole lot of writing is done for the sake of it, to get ideas down on paper, even if nobody ever reads it. </p>
<h2>Cult of the Pundit</h2>
<p>Most bloggers certainly don&#8217;t care what pundits think&#8230;they don&#8217;t even know that people are complaining&#8230;maybe we should call this the <em>Cult of the Pundit</em>. The cult of complaining about things that we fail to see the value in and so dismiss entirely.  </p>
<p>This is the same problem with social networking sites&#8230;people ridiculed social sites to no end because they couldn&#8217;t see the value in all that socializing. Now, however, people&#8217;s tunes are changing because those sites are being valued in the billions. Most blogs don&#8217;t have that luxury, however, because most of their audiences will always be small. </p>
<p>I agree with Clay that a great engineering challenge is filtering. But I also think that we have other challenges that are as important&#8230;like learning to write and express ourselves in the world. </p>
<p>So if the alternative to all this blogging is not blogging, not writing on a daily basis, then I&#8217;m not sure but we&#8217;re creating an even bigger problem. I would rather have people writing poorly than not at all. </p>
<h2>Yochai Benkler: What is quality?</h2>
<p>Not everyone is willing to give up on humanity so fast as Keen and other critics. Yochai Benkler, <a href="http://zero.newassignment.net/filed/yochai_benkler">when asked</a> if he still thought that &#8220;the practice of producing culture makes us all more sophisticated readers, viewers, and listeners, as well as more engaged makers&#8221;, an argument he makes in his book, <a href="http://www.amazon.com/gp/product/0300110561/">The Wealth of Networks</a>, had this to say: </p>
<blockquote><p>&#8220;I think there&#8217;s a lot of anxiety about where quality comes from in distributed environments. At the same time&#8212;and this is understandable, we value great art, we value quality everything, we don&#8217;t want it to disappear. The question is: what is quality? and how much are we getting from the mass media culture that pervaded the 20th century? High production doesn&#8217;t mean quality. The best music didn&#8217;t necessarily make it commercial. Mass media doesn&#8217;t necessarily give us quality; it does give us passivity, and I think that&#8217;s unattractive. The thing we see today are cultural practices of review and annotation and recursion that we see everywhere (f. ex. on YouTube) do require a different mode of participation. A lot of it will be crap, and a lot of what comes out of mainstream media will be crap, as will a lot of what comes out of supposedly authorized art. Really great stuff is rare. It&#8217;s rare in organized systems, it&#8217;s rare in decntralized systems. Unless you think the system you&#8217;re coming from is really perfect at identifying, eliciting, and distributing high quality, then you really have to examine the relative merit of these two systems. It&#8217;s not at all clear to me that the new system is suppressive of quality. The declaration of quality comes from a set of exchanges as opposed to authorization by somebody who is supposedly an expert who says, &#8220;this is art and that is not art.&#8221;</p>
</blockquote>
<h2>What was it like during the Renaissance?</h2>
<p>Sometimes, in my most optimistic moments, I wonder what it was like at the beginning of the Renaissance. Were there thousands of people in Florence writing, painting and sculpting and doing it poorly? Were they constantly flying by the seat of their pants, creating new media without having an established foundation upon which to build? Were there people who constantly excoriated them for doing something new&#8230;badly? </p>
<p>While Clay is right to consider Keen&#8217;s argument with fresh eyes, he has to agree that Keen is little more than a shock jock. Even if Keen&#8217;s got good points hidden in his book (I haven&#8217;t read it), it is still plain what he&#8217;s trying to do. He&#8217;s painting the world in black and white when there are millions of folks experimenting with color.</p>
<p>What isn&#8217;t clear is how much better off we&#8217;ll be with so many people learning how to write. Maybe we will have citizen journalists that deliver news faster and more comprehensive than before. Maybe we&#8217;ll have better technology analysts who are specialists in their field and not just good generalists from the big newspapers. </p>
<p>Or maybe, just maybe, we&#8217;ll have one or two Michelangelos surface who make everyone forget how much kerfuffle was made about the Cult of the Amateur. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/cult-of-the-pundit/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Give people something to copy</title>
		<link>http://bokardo.com/archives/give-people-something-to-copy/</link>
		<comments>http://bokardo.com/archives/give-people-something-to-copy/#comments</comments>
		<pubDate>Mon, 14 May 2007 19:17:13 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/give-people-something-to-copy/</guid>
		<description><![CDATA[<em>Quick blogging tip</em>: When someone writes an <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/2007/05/my_hero_for_tod.html">incredibly flattering post</a> about you, don't immediately link to the flattering post. Why?

Because many times when someone does this, the link can actually be hurtful because it's not a real link to quality content. The author, the flattered one, often pretends they're really writing about the rest of the post and not the part about themselves. But they're really writing to point out that someone likes them. 

I'm not immune to this. I've done it too. But its completely obvious. In some cases, someone will actually point to someone else's post and <em>not mention</em> that there is a part of the post about them...pretending to ignore it. That is so weird though, when you go read the post and wonder...does the person think I'm an idiot? 

Instead, wait until that person writes something really cool, and then link to that.]]></description>
			<content:encoded><![CDATA[<p><em>Quick blogging tip</em>: When someone writes an <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/2007/05/my_hero_for_tod.html">incredibly flattering post</a> about you, don&#8217;t immediately link to the flattering post. Why?</p>
<p>Because many times when someone does this, the link can actually be hurtful because it&#8217;s not a real link to quality content. The author, the flattered one, often pretends they&#8217;re really writing about the rest of the post and not the part about themselves. But they&#8217;re really writing to point out that someone likes them. </p>
<p>I&#8217;m not immune to this. I&#8217;ve done it too. But its completely obvious. In some cases, someone will actually point to someone else&#8217;s post and <em>not mention</em> that there is a part of the post about them&#8230;pretending to ignore it. That is so weird though, when you go read the post and wonder&#8230;does the person think I&#8217;m an idiot? </p>
<p>Instead, wait until that person writes something really cool, and then link to that. In this case, Mark Earls, whose blog is <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/">Herd, the hidden truth about who we are</a>,  has written an insightful post about how humans copy each other so much: <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/2007/05/copying_is_good.html">Copying is Good</a>.</p>
<p>He says: </p>
<blockquote><p>&#8220;Whatever our culture (and of course our own minds) tell us, human beings are copying machines. We do it all the time from the moment we are born to the day we die. Copying is a much more important form of learning for humans than it is for other primates.</p>
<p>One of the plausible explanations for this is that human beings are born c.12months premature into much more sophisticated social lives than any other primate; this requires a lot of learning and it seems easiest to get the thing roughly down first of all and correct things (if necessary) later on. Copying is an ideal strategy for this kind of &#8220;stupid&#8221; infant; it&#8217;s just something that stays switched on through our adult lives, also.&#8221;</p>
</blockquote>
<p>His resulting design suggestion? &#8220;Give people something to copy&#8221;. </p>
<p>Now this is social design! This is how to take advantage of <em>what people already do</em> socially and make tools to help support it. </p>
<p>If you link immediately and don&#8217;t wait, you&#8217;re actually diluting the value of your link because people unfamiliar with the blog will think that&#8217;s what they write about or the only reason you linked to them is because they write flattering stuff. Instead, you owe it to your readers to link to the cream of their crop. </p>
<p>And, by the way, this is how to keep a high pagerank. Always obsess over what you link to. Make sure its good and adds to the conversation! And, in terms of full disclosure, mention that they wrote <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/2007/05/my_hero_for_tod.html">something very flattering</a> about you. <img src='http://bokardo.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>You need to show your readers why their blog is a good read&#8230;so save your links for a <a href="http://herd.typepad.com/herd_the_hidden_truth_abo/2007/05/copying_is_good.html">post that pushes the discussion forward</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/give-people-something-to-copy/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The Blog is the New Resume</title>
		<link>http://bokardo.com/archives/the-blog-is-the-new-resume/</link>
		<comments>http://bokardo.com/archives/the-blog-is-the-new-resume/#comments</comments>
		<pubDate>Thu, 19 Apr 2007 14:30:44 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/the-blog-is-the-new-resume/</guid>
		<description><![CDATA[Bokardoan Adam Darowski suggests that <a href="http://www.darowski.com/tracesofinspiration/2007/03/06/the-blog-is-the-new-resume/">the blog is the new resume</a>. I think he's absolutely right...whenever anyone wants to know anything about me I send them here. 

This immediately brings several things to bear:

<ol>

<li><strong>Your blog represents you.</strong><br />
Represent! Your blog is speaking for you...to folks who might not know anything about you. Is it saying the right thing? is it saying the same thing you would say if you met someone for the first time?</li>
</ol>

...]]></description>
			<content:encoded><![CDATA[<p>Bokardoan Adam Darowski suggests that <a href="http://www.darowski.com/tracesofinspiration/2007/03/06/the-blog-is-the-new-resume/">the blog is the new resume</a>. I think he&#8217;s absolutely right&#8230;whenever anyone wants to know anything about me I send them here. </p>
<p>This immediately brings several things to bear:</p>
<ol>
<li><strong>Your blog represents you.</strong><br />
Represent! Your blog is speaking for you&#8230;to folks who might not know anything about you. Is it saying the right thing? is it saying the same thing you would say if you met someone for the first time?</li>
<li><strong>Your blog is serious business.</strong><br />
It has the power to completely sway someone&#8217;s opinion about you. It fulfills the needs of lurkers everywhere who Google you to see what kind of person you are. Show them your best. (if you&#8217;re looking for work this is extremely important)</li>
<li><strong>You blog is an archive.</strong><br />
Your blog is an archive of your life that has its effects over time. What you write today will be there a year from now and is it any good? Really? Is it worth reading again? Sometimes you should ask yourself this question before publishing&#8230;</li>
<li><strong>Your blog isn&#8217;t the only mirror of your life.</strong><br />
Folks are getting savvy to the places that people are building online. Your facebook account, MySpace account, LinkedIn profile, Flickr set&#8230;all of these represent you, too. Make sure not that they paint you in an unfailing light, but that they represent you accurately. The best defense is truthfulness&#8230;be sure to always be truthful about yourself and everything will fall into place. </p>
</li>
<li><strong>Your blog is your unedited version of yourself.</strong><br />
Your blog is what you say when there is nobody standing over your shoulder telling you what to do. It demonstrates how you think outside the rules. It is one of the very few places where you have complete editorial control. Don&#8217;t take that for granted.</li>
</ol>
<h2>What if I don&#8217;t have a blog?</h2>
<p>It&#8217;s OK that you don&#8217;t have a blog. But realize that you&#8217;re competing with many folks who do&#8230;and that&#8217;s only going to get harder over time. So, if you can, start one. Give it a go. </p>
<p>If you&#8217;re unsure, well, here are a couple pieces to get you started:</p>
<ul>
<li><a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for Would-be Bloggers</a></li>
<li><a href="http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/">9 <em>More</em> Lessons for Would-be Bloggers</a>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/the-blog-is-the-new-resume/feed/</wfw:commentRss>
		<slash:comments>53</slash:comments>
		</item>
		<item>
		<title>Make your Blog more Usable</title>
		<link>http://bokardo.com/archives/make-your-blog-more-usable/</link>
		<comments>http://bokardo.com/archives/make-your-blog-more-usable/#comments</comments>
		<pubDate>Tue, 10 Apr 2007 01:20:23 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/make-your-blog-more-usable/</guid>
		<description><![CDATA[My referral logs point me to <a href="http://www.idratherbewriting.com/">Tom Johnson</a>, author of a nice post called <a href="http://www.idratherbewriting.com/2007/04/09/twenty-usability-tips-for-your-blog-%e2%80%94-condensed-from-dozens-of-bloggers-experiences/#more-533">Twenty Usability Tips for Your Blog</a>. Tom read my recent post on <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for would-be Bloggers</a> and uses Bokardo as an example of a site with a topic (social design). Cool!

Running down Tom's list is an exercise in agreement. He's uncovered many of the important daily activities of a blogger. There are only one or two that I don't practice...not really out of disagreement but more out of laziness. ;) 

Tom has an interesting topic of his own: "I blog about how emerging technologies such as blogging, podcasting, wikis, open source, and Web 2.0 can be applied to technical writing.". 

Sometimes my referral logs lead to the best stuff. Thanks for the post, Tom! ]]></description>
			<content:encoded><![CDATA[<p>My referral logs point me to <a href="http://www.idratherbewriting.com/">Tom Johnson</a>, author of a nice post called <a href="http://www.idratherbewriting.com/2007/04/09/twenty-usability-tips-for-your-blog-%e2%80%94-condensed-from-dozens-of-bloggers-experiences/#more-533">Twenty Usability Tips for Your Blog</a>. Tom read my recent post on <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for would-be Bloggers</a> and uses Bokardo as an example of a site with a topic (social design). Cool!</p>
<p>Running down Tom&#8217;s list is an exercise in agreement. He&#8217;s uncovered many of the important daily activities of a blogger. There are only one or two that I don&#8217;t practice&#8230;not really out of disagreement but more out of laziness. <img src='http://bokardo.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  </p>
<p>Tom has an interesting topic of his own: &#8220;I blog about how emerging technologies such as blogging, podcasting, wikis, open source, and Web 2.0 can be applied to technical writing.&#8221;. </p>
<p>Sometimes my referral logs lead to the best stuff. Thanks for the post, Tom! </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/make-your-blog-more-usable/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Kudos to Kathy Sierra</title>
		<link>http://bokardo.com/archives/kudos-to-kathy-sierra/</link>
		<comments>http://bokardo.com/archives/kudos-to-kathy-sierra/#comments</comments>
		<pubDate>Tue, 27 Mar 2007 03:08:04 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/kudos-to-kathy-sierra/</guid>
		<description><![CDATA[The recent <a href="http://www.techmeme.com/070326/p72#a070326p72">situation involving Kathy Sierra</a> is horrible: she's received death threats to the point that she doesn't feel safe even speaking at conferences. <a href="http://headrush.typepad.com/creating_passionate_users/2007/03/as_i_type_this_.html">Her post is scary</a>.

Many folks are saying things like <a href="http://www.techmeme.com/070326/p72#a070326p72">"this is the underbelly of the blogosphere"</a>. 

No, it isn't. It's the underbelly of humankind...]]></description>
			<content:encoded><![CDATA[<p>The recent <a href="http://www.techmeme.com/070326/p72#a070326p72">situation involving Kathy Sierra</a> is horrible: she&#8217;s received death threats to the point that she doesn&#8217;t feel safe even speaking at conferences. <a href="http://headrush.typepad.com/creating_passionate_users/2007/03/as_i_type_this_.html">Her post is scary</a>.</p>
<p>Many folks are saying things like <a href="http://www.techmeme.com/070326/p72#a070326p72">&#8220;this is the underbelly of the blogosphere&#8221;</a>. </p>
<p>No, it isn&#8217;t. It&#8217;s the underbelly of humankind. This stuff has happened forever, to all kinds and sorts of people, in all walks of life, for thousands of years. It wasn&#8217;t right in prehistory. It wasn&#8217;t right in Greek and Roman times. It wasn&#8217;t right when the major religions blossomed. It wasn&#8217;t right in Medieval times, it wasn&#8217;t right during Enlightenment, and it&#8217;s not right now. </p>
<p>This is the Social Web. This is the point where the distinction between what&#8217;s going on offline and what&#8217;s going on online isn&#8217;t important anymore. Posting an anonymous comment is the same as yelling at someone across the street. The <em>only difference</em> is that its recorded for others to see. </p>
<p>And you know what? That might be a good thing. The silver lining is that this behavior is public, and the community is pushing back on itself. The right things are being said. &#8220;This is unacceptable.&#8221; &#8220;This is wrong.&#8221; &#8220;This is bullshit.&#8221; We won&#8217;t stand for this. </p>
<p>That&#8217;s what a strong community does. It condemns bad behavior publicly, loudly, and absolutely. Kudos to Kathy for saying what happened, and for having the courage to fight back.</p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/kudos-to-kathy-sierra/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>9 More Lessons for Would-Be Bloggers</title>
		<link>http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/</link>
		<comments>http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/#comments</comments>
		<pubDate>Mon, 26 Mar 2007 14:08:44 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/</guid>
		<description><![CDATA[<em>A follow up to <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for Would-be Bloggers</a>. A few more lessons learned in 7 years of blogging.</em>

<h2>Write Follow-up Posts</h2>

This post is an example of this lesson in action. Two weeks ago I wrote <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for Would-be Bloggers</a> and it got a good amount of traffic: people seemed to enjoy it. Darren Rowse of <a href="http://www.problogger.net/">Problogger</a>, who I've read for some time, embraced it and <a href="http://www.problogger.net/archives/2007/03/14/lessons-from-the-heart-for-would-be-bloggers/">added his own thoughts</a>. I had some great comments left on my blog and I thought about them and considered other lessons that I've learned. I kept writing them down as I thought of them and eventually built up 9 more of them to write this here post. 

So when something resonates with folks, keep paying attention to it. There might be openings for a follow-up post. When you do write up a follow-up post, link back to the original, assuming that some people will have never read it. And if the follow-up works, maybe start a series of posts on the topic. And then, a book. And after that...well you get the idea. ]]></description>
			<content:encoded><![CDATA[<p><em>A follow up to <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for Would-be Bloggers</a>. A few more lessons learned in 7 years of blogging.</em></p>
<h2>Write Follow-up Posts</h2>
<p>This post is an example of this lesson in action. Two weeks ago I wrote <a href="http://bokardo.com/archives/9-lessons-for-would-be-bloggers/">9 Lessons for Would-be Bloggers</a> and it got a good amount of traffic: people seemed to enjoy it. Darren Rowse of <a href="http://www.problogger.net/">Problogger</a>, who I&#8217;ve read for some time, embraced it and <a href="http://www.problogger.net/archives/2007/03/14/lessons-from-the-heart-for-would-be-bloggers/">added his own thoughts</a>. I had some great comments left on my blog and I thought about them and considered other lessons that I&#8217;ve learned. I kept writing them down as I thought of them and eventually built up 9 more of them to write this here post. </p>
<p>So when something resonates with folks, keep paying attention to it. There might be openings for a follow-up post. When you do write up a follow-up post, link back to the original, assuming that some people will have never read it. And if the follow-up works, maybe start a series of posts on the topic. And then, a book. And after that&#8230;well you get the idea. </p>
<h2>When you screw up, say so immediately</h2>
<p>Admitting idiocy is one of the most important things a blogger can do. It completely diffuses a situation that could quickly turn ugly. For some reason we have an assumption that admitting a wrong is like kicking a puppy&#8230;some people would do almost anything to avoid it. But I remember listening to a podcast of <a href="http://en.wikipedia.org/wiki/Adam_Bosworth">Adam Bosworth</a>, who is a damn smart guy (VP at Google), in which a point he made was quickly refuted&#8230;and instead of defending his position he said immediately: &#8220;Yes, you&#8217;re right. I stand corrected.&#8221; As a listener I was completely disarmed&#8230;when was the last time someone said they stand corrected? The result is that I&#8217;ve ended up having more respect for Adam than I did previously. So pay attention to people who admit when they&#8217;re wrong&#8230;they&#8217;re the type of people worth listening to because you know they&#8217;re not trying to spin anything. And the funny thing is, that if you admit you&#8217;re wrong, people might just start assuming that in the other cases you&#8217;re right. </p>
<h2>Know when to take it offline</h2>
<p>Several times I&#8217;ve had folks come to my site and try to embarrass or criticize me personally in the comments on a post. Whenever this happens, you have to immediately take it offline. Send them an email and explain your situation. More than likely, they&#8217;ll cool down after that. </p>
<p>I recently ran into this with my <a href="http://bokardo.com/archives/infoprefixation/">Death of IA</a> posts&#8230;I had some IA folks come and really lay into me, trying to insult me in front of my audience. It&#8217;s fine to argue the points of a post, but its another thing to let someone criticize you outside the bounds of your writing on a personal level. In these cases I simply wrote them an email stating that I would be glad to consider their points as long as they stuck to the content of my post&#8230;sometimes this works and sometimes it doesn&#8217;t. Sometimes you just have to stop the discussion and move on. So remember that its your blog and your audience&#8230;you&#8217;re the editor and you decide what is worth arguing and what isn&#8217;t. </p>
<h2>Link back to your good stuff</h2>
<p>Some folks don&#8217;t link back to their good stuff enough. Hopefully you have a greatest hits section on your site, but in addition to that refer to something you&#8217;ve previously written. If you wrote it well, it will be easy to do, because your post will act as a reference for the topic. Others will pick up on that and perhaps link as well. </p>
<p>One caveat&#8230;rarely quote yourself. For some reason it&#8217;s a big turnoff&#8230;maybe too much self-flattery or something. Instead, simply repeat the idea in a slightly different way, resetting the context for the idea that you want to talk about again. But please, don&#8217;t quote yourself&#8230;quoting is an activity we should reserve for people other than ourselves. </p>
<h2>Reread to yourself</h2>
<p>Blogs aren&#8217;t books, poems, or even journalism. They&#8217;re conversations, so they need to be conversational. Make them read like how you talk. I can&#8217;t tell you how many times I&#8217;ve written something that wasn&#8217;t conversational that didn&#8217;t resonate&#8230;because I was trying to be too formal. Then, I&#8217;ll write a post very quickly and conversationally and it will lead to something. That&#8217;s a funny thing about blog posts&#8230;people do treat them as a conversation. And, except for being asynchronous, they are. </p>
<h2>Treat every post as a possible later reference</h2>
<p>This is something that I&#8217;ve only realized of late. Treat every post as a reference going forward. If you&#8217;re a programmer, think about the DRY principle: Don&#8217;t Repeat Yourself. Write something once, write it well (revise until necessary) and then feel free to refer back to it later. One of my frustrations is when I&#8217;ll have a couple posts on the same idea that don&#8217;t work very well&#8230;because I put them up too hastily. Better to write it once, take your time, and make it something that not just you, but others can reference later on. </p>
<p>A good example of this is my post <a href="http://bokardo.com/archives/judging_design_superficially/">The Dangers of Judging Web Design Superficially</a>. I wrote this almost three years ago, and recently linked back to it. Someone picked it up just the other day, linked to it from a well-trafficked blog, and sent a whole bunch of readers my way. You never know when stuff like this will happen, so treat every post as a target. </p>
<h2>Keep updating your best posts</h2>
<p>This goes along with the previous one. If you take your posts seriously, and you treat them as an reference archive, then people will link to them and send traffic to them over time. So, if the post could use pruning, or additions, be sure to go back and add them. It&#8217;s OK&#8230;this isn&#8217;t paper we&#8217;re publishing on. Just go back and change it, and maybe add a note that you&#8217;ve done so. </p>
<h2>Name things (e.g. <a href="http://bokardo.com/archives/the-delicious-lesson/">The Del.icio.us Lesson</a>, <a href="http://bokardo.com/archives/the-chanel-lesson/">The Chanel No. 5 Lesson</a>)</h2>
<p>This one I learned with <a href="http://bokardo.com/archives/the-delicious-lesson/">The Del.icio.us Lesson</a>, which I had actually written about before I named it. After I named it, it became my most read post of all-time. The idea is also a relatively clear one, so people could easily understand it, but I think that naming really drove it home and associated the idea with the Del.icio.us name&#8230;which is a very popular and well-known site. Of course, don&#8217;t name things just because you can, and make sure that if you name something that there is a real importance to the idea you&#8217;re naming. I knew it was important because people kept repeating it to me over and over&#8230;I just happened to be the person who wrote it down. </p>
<h2>Link to the quiet, unknown ones </h2>
<p>I know because I am a quiet one (or used to be). Link to people who nobody has heard of, just to give them some exposure. They&#8217;re just as smart as anybody else, they&#8217;ve got just as much to say. They just don&#8217;t have the attention yet. I remember reading Noah Brier back before either of us had much of an audience and were working out our blogging kinks&#8230;linking back and forth every once in a while. Well, Noah&#8217;s now kicking some serious butt and he&#8217;s got a good audience&#8230;his <a href="http://likemind.us/">Likeminds meetups</a> are growing and growing. </p>
<p>It works like this: people expecting company clean the house. If a blogger is expecting company (readers), they&#8217;re much more likely to work on their blog and make it better. Conversely, if they are unknown, they&#8217;re not really expecting anybody, and this lowers their own expectations of what and how they write. My guess is that any blogger out there, if they were told they could have a spot in an upcoming edition of the New Yorker alongside Malcolm Gladwell and James Suroweiki, would rise to the occasion and write their very best. They would care more, pay much more attention to what they write, and really knock one out of the park. </p>
<p>Any editors of the New Yorker reading this&#8230;? I&#8217;m waiting. <img src='http://bokardo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p><strong>Translations</strong>: <a href="http://fiksz.klog.hu/138/99-lecke-hezitalo-konyvtarosoknak-es-kezdo-bloggereknek/">Hungarian</a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/feed/</wfw:commentRss>
		<slash:comments>38</slash:comments>
		</item>
		<item>
		<title>9 Lessons for Would-be Bloggers</title>
		<link>http://bokardo.com/archives/9-lessons-for-would-be-bloggers/</link>
		<comments>http://bokardo.com/archives/9-lessons-for-would-be-bloggers/#comments</comments>
		<pubDate>Sun, 11 Mar 2007 15:43:18 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/9-lessons-for-would-be-bloggers/</guid>
		<description><![CDATA[<em>A few lessons learned in 7 years of blogging.</em>

I attended the <a href="http://2007.sxsw.com/interactive/programming/panels/?action=show&#038;id=IAP060277">Writing, Better</a> panel here at SXSW. I've been thinking about it ever since, both because I wanted the conversation to go on for a few more hours and because so many people here are bloggers that blogging comes up every few minutes or so. Here are some lessons that I've learned about blogging...hopefully they can be of help to others...
]]></description>
			<content:encoded><![CDATA[<p><em>A few lessons learned in 7 years of blogging. Also read <a href="http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/">9 More Lessons for Would-be Bloggers</a></em></p>
<p>I attended the <a href="http://2007.sxsw.com/interactive/programming/panels/?action=show&#038;id=IAP060277">Writing, Better</a> panel here at SXSW. I&#8217;ve been thinking about it ever since, both because I wanted the conversation to go on for a few more hours and because so many people here are bloggers that blogging comes up every few minutes or so. Here are some lessons that I&#8217;ve learned about blogging&#8230;hopefully they can be of help to others. </p>
<h2>It&#8217;s only an initial fear</h2>
<p>The problem with blogging isn&#8217;t just the writing part. It&#8217;s also the putting-myself-on-public-display part. Many would-be bloggers that I&#8217;ve met don&#8217;t blog because they&#8217;re not comfortable with throwing themselves to the wolves&#8230;putting their ideas out into the world for all to see. Once you do that, of course, you open yourself up for criticism, and goodness knows that you&#8217;ll get some! But you&#8217;ll also get encouragement, and some people will really groove on what you say. Once you get a little practice under your belt, you&#8217;ll find that it&#8217;s only an initial fear&#8230;it gets easier as you go along to share your ideas. </p>
<h2>You have something valuable to say</h2>
<p>One of the biggest problems is that some people don&#8217;t think they have anything useful to say. They think: look at all the incredible amount of writing out there already&#8230;what can I add to it? Ironically, its <em>those</em> people who probably have the <em>most</em> to say, but they&#8217;re concerned that they won&#8217;t say it well or in the right way. Those are the people who care about what they say and know that words have tremendous power. They consider the act of writing as an act of conversation, as opposed to others who see it as a way to make money or a way to promote something. We need those people to recognize that they do have something valuable to say, and that the blogosphere would be better, not worse, with them contributing. </p>
<p>I remember meeting <a href="http://www.flickr.com/photos/x180/22480214/in/set-510355/">Paul Rademacher</a>, creator of <a href="http://housingmaps.com">HousingMaps</a> (before Google had an API!) and hearing this story from him. He didn&#8217;t think he had anything to add. I couldn&#8217;t believe it! Here&#8217;s a guy who created an amazingly-cool web application in his spare time while working as an animation engineer for Dreamworks!, and he didn&#8217;t think that anybody would want to hear what he had to say. Well, it&#8217;s that sort of different thinking that we need! After I met him, I kept wondering how many other folks are like him that are silent in the blogosphere. </p>
<h2>When in doubt, post.</h2>
<p>I keep telling the same story to would-be bloggers. A couple weeks ago I was working on a post for Bokardo and it wasn&#8217;t going well&#8230;I couldn&#8217;t get to what I wanted to say. So I looked around, realized that I hadn&#8217;t posted the <a href="http://bokardo.com/archives/five-principles-to-design-by/">5 Principles to Design By</a> from my <a href="http://bokardo.com/about/">about page</a>, and just posted that. It has now become the post that many people recognize my blog from, because in some way one of the five principles touched a nerve with them. I did not predict this, and don&#8217;t think I could have. So when it doubt&#8230;post. You can always un-publish it if you need to.</p>
<h2>Use the comments for refining your point</h2>
<p>Lots of times I&#8217;ll post and my point won&#8217;t be crystal clear. Someone will read it and leave a comment saying so. When someone does this, when they take time out of their busy day to read what you&#8217;ve said and respond to it, TAKE IT AS A GIFT. Always remember that these people are right! They&#8217;re your readers, and so if something isn&#8217;t clear to them then it&#8217;s probably not clear to the others who who haven&#8217;t read it yet or don&#8217;t have the time to leave comments. So you have to take the time to go back and make your point clear. Whatever you do, don&#8217;t argue with them, don&#8217;t say that they didn&#8217;t understand the point. Let them know you&#8217;re hearing them and try to clarify what you mean. And, if its a relatively big change, make sure to go back and change your original post to reflect that, so readers coming in get your most up-to-date thinking. </p>
<h2>Everything is beta</h2>
<p>My theory for Bokardo is that everything is beta. That lets me stop worrying about publishing end-all, be-all pieces that set the world on fire. If my blog is my beta (the blog itself is not beta&#8230;it&#8217;s the <em>thoughts</em> that are beta), then it becomes a place for trying out ideas and refining them. After I do that, I&#8217;ll republish the best ideas somewhere else&#8230;in a talk I give or in a <a href="http://www.uie.com/articles/">UIEtips article</a> or an article in an <a href="http://digital-web.com">online magazine</a>. Some posts will rise to the top and have lasting power, like my piece on the <a href="http://bokardo.com/archives/the-delicious-lesson/">Del.icio.us Lesson</a>, but the vast majority don&#8217;t. So don&#8217;t worry if your writing is beta&#8230;that&#8217;s perfectly OK.  </p>
<h2>Have a schtick</h2>
<p>I write about lots of things here on Bokardo, but my schtick is that I write about social design. I even have the words explained on every page on this site. Why is this? Well, it helps me keep a focus for the blog&#8230;to keep the posts moving in a general direction. This vastly improves my ability to figure out what to write about, because I&#8217;ve got a flag to fly. Before I had a clear focus I used to flounder when I couldn&#8217;t decide what to write about&#8230;I ended up with a much less focused blog and poorer posts because of it. </p>
<p>One caveat, though. You have to <em>really</em> believe in your schtick&#8230;you have to think that the topic is important and have to have <em>passion</em> for it. You can still deviate from the topic, as I&#8217;m doing with this post, and that&#8217;s OK. It&#8217;s a lot easier to write exceptions to the rule than it is to not have a rule in the first place. So plant your flag&#8230;have a schtick&#8230;it not only makes writing easier but you&#8217;ll also get other people thinking about your blog in terms of it. It&#8217;s kind of like a brand in this way. </p>
<h2>Correct English be-damned</h2>
<p>People don&#8217;t care very much whether you write in complete sentences, use correct grammar, or are copy-edited. It&#8217;s much more visceral and fast. They care about ideas&#8230;are you adding good ideas to the idea-pool? Are you telling them something they knew but haven&#8217;t articulated or haven&#8217;t thought about yet? If you spend a lot of time blogging, make sure that you spend it on clarity&#8230;that every word is understandable and your ideas are clear. Notice that in this post I&#8217;m being very-straightforward&#8230;it&#8217;s clear what I&#8217;m talking about. This isn&#8217;t always easy&#8230;and it takes practice and time. Don&#8217;t let the simple posts fool you&#8230;that&#8217;s the goal. </p>
<h2>Show your greatest hits</h2>
<p>A tactical lesson I learned from Brian Clark, who writes highly-recommended <a href="http://www.copyblogger.com/">CopyBlogger</a>. Create a greatest hits module for your blog and display it on all pages. This will be an instant target for new readers, who will be funneled into your best content. It will also help remind regular readers what you&#8217;ve said in the past, and help them think about your blog in those terms. And if you&#8217;re just starting out, put all of your posts in it. You can easily take them out as new greatest hits emerge. </p>
<h2>People <em>are</em> listening</h2>
<p>For every person who posts a comment on your blog, you have 10 (or 100) readers who won&#8217;t. Always remember that! Even if you don&#8217;t get the 100 comments that you were hoping for doesn&#8217;t mean that people didn&#8217;t like the post or that they didn&#8217;t consider it&#8230;it just means that they didn&#8217;t have anything to initially say or couldn&#8217;t at the time. This is a hard problem&#8230;because if you don&#8217;t travel a lot then you might never know that there are people who are reading and just not saying much. If you do travel, make sure you let people know who you are and what your blog is, and you&#8217;ll be pleasantly surprised at how many readers you have. </p>
<p><em>Got lessons of your own?</em> Share them in the comments or write your own post and let me know so that I can link to you. </p>
<p>Update: Also read <a href="http://bokardo.com/archives/9-more-lessons-for-would-be-bloggers/">9 More Lessons for Would-be Bloggers</a></p>
<p><strong>Translations</strong>: <a href="http://blog.joablen.com/?p=21">Espa&#241;ol</a> | <a href="http://fiksz.klog.hu/138/99-lecke-hezitalo-konyvtarosoknak-es-kezdo-bloggereknek/">Hungarian</a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/9-lessons-for-would-be-bloggers/feed/</wfw:commentRss>
		<slash:comments>210</slash:comments>
		</item>
		<item>
		<title>Gender Issues</title>
		<link>http://bokardo.com/archives/gender-issues/</link>
		<comments>http://bokardo.com/archives/gender-issues/#comments</comments>
		<pubDate>Thu, 01 Mar 2007 18:26:24 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/gender-issues/</guid>
		<description><![CDATA[<a href="http://annezelenka.com/">Anne Zelenka</a>, who I had the pleasure of meeting at the <a href="http://www.techmeme.com/070227/p63#a070227p63">Adobe Engage</a> event on Tuesday, adds a valuable viewpoint to the <a href="http://www.kottke.org/07/02/gender-diversity-at-web-conferences">recent gender discussion <strike>started</strike> reignited by Jason Kottke</a>. (Anne and I have cross-linked in the past...she's a deep thinker on social issues) 

<blockquote><p>"Gender is an important category of diversity because women experience radically different life patterns and external expectations than men and so by including a critical mass of women you are more likely to get some orthogonal perspectives than if you include more men. Now of course you can go after diverse men tooâ€“and you should if you are concerned about overcoming groupthink and echo chamber effects. But if you leave out women almost entirely, you are leaving out representatives of half your potential audience. Even given similar intelligence profiles, career paths, and temperaments, a woman and a man are likely to have very different views on technologyâ€¦ because they come at it from vastly different experiences of the world. We experience more conflicting messages and more ambivalence around working in technology and working with technology than men do. Society expects different things from us, so we in turn may focus on what seems unimportant or uninteresting to men."</p></blockquote>

<a href="http://annezelenka.com/2007/02/working-with-the-architecture-of-the-space">More here</a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://annezelenka.com/">Anne Zelenka</a>, who I had the pleasure of meeting at the <a href="http://www.techmeme.com/070227/p63#a070227p63">Adobe Engage</a> event on Tuesday, adds a valuable viewpoint to the <a href="http://www.kottke.org/07/02/gender-diversity-at-web-conferences">recent gender discussion <strike>started</strike> reignited by Jason Kottke</a>. (Anne and I have cross-linked in the past&#8230;she&#8217;s a deep thinker on social issues) </p>
<blockquote><p>&#8220;Gender is an important category of diversity because women experience radically different life patterns and external expectations than men and so by including a critical mass of women you are more likely to get some orthogonal perspectives than if you include more men. Now of course you can go after diverse men tooâ€“and you should if you are concerned about overcoming groupthink and echo chamber effects. But if you leave out women almost entirely, you are leaving out representatives of half your potential audience. Even given similar intelligence profiles, career paths, and temperaments, a woman and a man are likely to have very different views on technologyâ€¦ because they come at it from vastly different experiences of the world. We experience more conflicting messages and more ambivalence around working in technology and working with technology than men do. Society expects different things from us, so we in turn may focus on what seems unimportant or uninteresting to men.&#8221;</p>
</blockquote>
<p><a href="http://annezelenka.com/2007/02/working-with-the-architecture-of-the-space">More here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/gender-issues/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Going to SXSW</title>
		<link>http://bokardo.com/archives/going-to-sxsw/</link>
		<comments>http://bokardo.com/archives/going-to-sxsw/#comments</comments>
		<pubDate>Mon, 26 Feb 2007 09:29:21 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/going-to-sxsw/</guid>
		<description><![CDATA[This will be my first trip to the venerable <a href="http://2007.sxsw.com/interactive/">SXSW Interactive Festival</a> in Austin. If any of you, my fair readers, are attending I would love to meet up and chat. Drop me a line via email or in the comments...

Of course, we wouldn't chat about blogging...probably more along the lines of Texas BBQ and beer. :)]]></description>
			<content:encoded><![CDATA[<p>This will be my first trip to the venerable <a href="http://2007.sxsw.com/interactive/">SXSW Interactive Festival</a> in Austin. If any of you, my fair readers, are attending I would love to meet up and chat. Drop me a line via email or in the comments&#8230;</p>
<p>Of course, we wouldn&#8217;t chat about blogging&#8230;probably more along the lines of Texas BBQ and beer. <img src='http://bokardo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/going-to-sxsw/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Rebuilding the Old Boss</title>
		<link>http://bokardo.com/archives/rebuilding-the-old-boss/</link>
		<comments>http://bokardo.com/archives/rebuilding-the-old-boss/#comments</comments>
		<pubDate>Wed, 14 Feb 2007 16:08:57 +0000</pubDate>
		<dc:creator>Josh</dc:creator>
				<category><![CDATA[blogging]]></category>
		<category><![CDATA[Social Design]]></category>

		<guid isPermaLink="false">http://bokardo.com/archives/rebuilding-the-old-boss/</guid>
		<description><![CDATA[Looking down the headlines at <a href="http://www.techmeme.com/">Techmeme</a> lately has been like looking at the news headlines from the big corps in the world. 

Of the <a href="http://www.techmeme.com/070214/h1035">first five big stories at the moment</a>, 3 come from the New York Times, 1 from Google, and 1 from Microsoft. ]]></description>
			<content:encoded><![CDATA[<p>Looking down the headlines at <a href="http://www.techmeme.com/">Techmeme</a> lately has been like looking at the news headlines from the big corps in the world. </p>
<p>Of the <a href="http://www.techmeme.com/070214/h1035">first five big stories at the moment</a>, 3 come from the New York Times, 1 from Google, and 1 from Microsoft. </p>
<p>On the one hand, this is good for the New York Times&#8230;they&#8217;re obviously keeping up with the blogosphere, as well as they should&#8230;they&#8217;ve got some of the best writers in the world there. </p>
<p>If Google and Microsoft even sneeze they get noticed in the blogosphere. Today the &#8220;big&#8221; news is that Google Webmaster is coming out of beta and Microsoft&#8217;s response to the speculation about the next version of Windows&#8230;WOW.</p>
<p>(thankfully, my buddy Richard MacManus from <a href="http://www.readwriteweb.com/">Read/WriteWeb</a> is sixth in line&#8230;with some <a href="http://www.readwriteweb.com/archives/online_video_index.php">novel analysis of online video technologies</a>.</p>
<p>I don&#8217;t think this is a bad thing for Techmeme, either. It&#8217;s just tracking what the blogs are talking about&#8230;and what they&#8217;re talking about is what big media is talking about. If it is tracking the social streams of news, then that&#8217;s great, even if it feels like an echo chamber at times. </p>
<p>From a personal standpoint, I try to read people who shy away from recapitulating. On second thought, maybe I don&#8217;t subscribe to them simply because I know I can find the info out on Techmeme. That&#8217;s probably more likely. </p>
<p>Sometimes I struggle with choosing topics myself. Obviously, there is news that should be shared, like the recent <a href="http://bokardo.com/archives/pew-study-28-of-online-americans-have-used-the-internet-to-tag-content/">Pew study on Tagging</a>, for example. I want you folks to know about that, so I&#8217;ll blog about it even though I know there is a high probability that you&#8217;ll hear about it elsewhere. </p>
<p>I appreciate what <a href="http://www.alexbarnett.net/blog/">Alex Barnett</a> said. Something to the effect of: &#8220;If I see it on Techmeme, I won&#8217;t blog about it&#8221;. I probably wouldn&#8217;t go to that extreme, but I understand the sentiment. </p>
<p>I wonder if people who have been around for several paradigm-changing technologies watch this sort of thing happening and secretly repeat to themselves: &#8220;meet the new boss, same as the old boss&#8221;. </p>
<p>(Update: Ironically, <a href="http://www.techmeme.com/070214/h1415">this post made Techmeme</a> (under the Read/WriteWeb article)</p>
]]></content:encoded>
			<wfw:commentRss>http://bokardo.com/archives/rebuilding-the-old-boss/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

