<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" version="2.0">

<channel>
	<title>Stopdesign</title>
	
	<link>http://stopdesign.com</link>
	<description>Stopdesign is the creative outlet of Douglas Bowman.</description>
	<lastBuildDate>Tue, 02 Mar 2010 19:55:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="stopdesign" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.stopdesign.com/index.xml" /><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.bloglines.com/sub/http://www.stopdesign.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.stopdesign.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
		<title>A browsable, searchable archive of tweets</title>
		<link>http://stopdesign.com/archive/2010/03/02/browsable-searchable-archive-of-tweets.html</link>
		<comments>http://stopdesign.com/archive/2010/03/02/browsable-searchable-archive-of-tweets.html#comments</comments>
		<pubDate>Tue, 02 Mar 2010 19:53:05 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[entries]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://stopdesign.com/?p=2247</guid>
		<description>In the past, I&amp;#8217;ve wanted to browse or search through my own tweets. Viewing my Twitter profile is one way to do that. But if I want to browse back through history, it&amp;#8217;s a chore to go back very far. And forget about searching through my own tweets on Twitter since Twitter Search currently only [...]</description>
			<content:encoded><![CDATA[<p>In the past, I&#8217;ve wanted to browse or search through my own tweets. Viewing my <a href="http://twitter.com/stop">Twitter profile</a> is one way to do that. But if I want to browse back through history, it&#8217;s a chore to go back very far. And forget about <a href="http://twitter.com/#search?q=from%3Astop">searching through my own tweets on Twitter</a> since Twitter Search currently only goes back about a seven days.</p>
<p><a href="http://stopdesign.com/tweets/"><img class="alignright wp-image-2249" title="tweets" src="https://stopdesign.com/img/archive/2010/03/tweets.png" alt="" width="200" height="150" /></a>I know there are a few <a href="http://www.readwriteweb.com/archives/10_ways_to_archive_your_tweets.php">apps</a> or <a href="http://www.readwriteweb.com/archives/how_to_backup_and_search_all_your_friends_tweets_i.php">scripts</a> that create backups and much more for you. But I wanted a database and simple UI completely within my own control. One that wouldn&#8217;t go away if the developer abandoned it. So one Saturday a few weeks ago, in a little over an hour, I had <strong>my own, free,</strong> <a href="http://stopdesign.com/tweets/">browsable, searchable tweet archive</a>. Now I can easily browse back to my <a href="http://stopdesign.com/tweets/4238"><strong>very first tweet</strong></a>, or search for those <a href="http://stopdesign.com/tweets/?s=paul+rand">quotes by <strong>Paul Rand</strong></a> I tweeted last year. This isn&#8217;t anything entirely new. I&#8217;m just writing it up what works for me in case it helps fit some pieces together.<span id="more-2247"></span></p>
<h4>How to set up your own tweet archive with WordPress</h4>
<ol>
<li>Assuming you have a collection of past tweets, the first step is to collect them in one place. <a href="http://tweetbackup.com/">TweetBackup.com</a> provides an easy way to do this. It uses OAuth, so there&#8217;s no need to enter your username or password as long as you&#8217;re already signed into twitter.com. Give them an email address, and your tweets start backing up immediately. (See their <a href="http://tweetbackup.com/faq/">FAQ</a> about a possible limitation of 3200 tweets.)</li>
<li>Once TweetBackup is done grabbing all your tweets (it took about 2 minutes for my ~1,400 tweets), go to the Export tab, and save the RSS format to your local drive</li>
<li>Install a fresh copy of <a href="http://wordpress.org/">WordPress</a> somewhere on your server if you don&#8217;t want tweets intermingled with other WP content. In the Tools section of WordPress, use the built-in RSS importer to import the file you saved from TweetBackup.</li>
<li>Assuming you want WordPress to automatically grab each tweet from this point forward, install the <a href="http://wordpress.org/extend/plugins/twitter-tools/">Twitter Tools plugin</a>, enter your Twitter credentials in its settings screen, and configure it to create a blog post for each of your tweets. (Turn off the option to tweet when a post is created from this blog so the universe doesn&#8217;t explode in some endless loop of repeating tweets and blog posts.)</li>
<li>That&#8217;s it.</li>
</ol>
<h4>A few extra steps, if you&#8217;re up for them</h4>
<ol>
<li>Twitter Tools will handle future tweets correctly. But the format of each tweet from TweetBackup starts with a prefix of your Twitter username, followed by a space and a colon, like this: &#8220;stop: Clicking through the new design of&#8230;&#8221;. I used the <a href="http://wordpress.org/extend/plugins/search-regex/">Search Regex</a> plugin to search for and eliminate that prefix.</li>
<li>Past tweets from TweetBackup won&#8217;t have linked URLs. The <a href="http://wordpress.org/extend/plugins/sem-autolink-uri/">Autolink URI</a> plugin can do this for you automatically.</li>
<li>If you&#8217;re good enough with regular expressions, you can also use the Search Regex plugin to link up any @mentions and #hashtags in your tweets. I suck at regex, so I cheated and used some of the <a href="http://davidwalsh.name/linkify-twitter-feed">patterns from David Walsh</a> within the Search Regex search/replace UI. Technically, you could probably use David&#8217;s first pattern to link up URLs too.</li>
<li>A few WP plugins can enhance the built-in search functionality of WordPress. I&#8217;m using <a href="http://wordpress.org/extend/plugins/search-everything/">Search Everything</a>.</li>
<li><a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache</a> will keep server resources to a minimum and help load pages quickly once they&#8217;re cached.</li>
<li>If you&#8217;re really up for it, you can customize the templates and design as I did. Anything is possible if you&#8217;re familiar with PHP and WordPress templates. For instance, you could try using the <a href="http://wordpress.org/extend/plugins/similar-posts/">Similar Posts</a> plugin to suggest possibly related tweets on the permalink page.</li>
</ol>
<p>Now, every tweet you&#8217;ve written and will write can be duplicated and backed up in your own MYSQL database, accessible via a WordPress front end. Technically, you could probably use any blogging platform or CMS to do this. (It doesn&#8217;t require WordPress.) You&#8217;ll just need a means to import old tweets and automatically grab new tweets.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/XKtwbqwuQs4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2010/03/02/browsable-searchable-archive-of-tweets.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>You cannot copyright a Tweet</title>
		<link>http://stopdesign.com/archive/2010/02/25/you-cannot-copyright-a-tweet.html</link>
		<comments>http://stopdesign.com/archive/2010/02/25/you-cannot-copyright-a-tweet.html#comments</comments>
		<pubDate>Thu, 25 Feb 2010 15:18:28 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2010/02/25/you-cannot-copyright-a-tweet.html</guid>
		<description>Though this may not completely eliminate liability if a publisher or artist rewraps a whole series of your tweets in a different shell, Zeldman makes an interesting point on the limitations of copyright in regards to short phrases (i.e. tweets):
As messages sent via Twitter cannot be longer than 140 characters, they cannot be copyrighted. However [...]</description>
			<content:encoded><![CDATA[<p>Though this may not completely eliminate liability if a publisher or artist rewraps a whole series of your tweets in a different shell, Zeldman makes an interesting point on the limitations of copyright in regards to short phrases (i.e. tweets):</p>
<blockquote><p>As messages sent via Twitter cannot be longer than 140 characters, they cannot be copyrighted. However original, witty, or profound they may be, nothing more than good manners protects your original expression of authorship. If you wish to let other people quote or use your Tweets, you need not <a href="http://www.tweetcc.com/">“license”</a> them; indeed, technically, you cannot license them, since they are in the public domain the instant you publish them.</p></blockquote>
<p><a class="linkurl" href="http://www.zeldman.com/2010/02/25/you-cannot-copyright-a-tweet/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/RzZQWP4CBJ0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2010/02/25/you-cannot-copyright-a-tweet.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accent Folding for Auto-Complete</title>
		<link>http://stopdesign.com/archive/2010/02/23/accent-folding-for-auto-complete.html</link>
		<comments>http://stopdesign.com/archive/2010/02/23/accent-folding-for-auto-complete.html#comments</comments>
		<pubDate>Tue, 23 Feb 2010 18:41:27 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[i18n]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2010/02/23/accent-folding-for-auto-complete.html</guid>
		<description>Carlos Bueno highlights an oft overlooked aspect of internationalization. His address book auto-complete example at the beginning of the article crystalized the problem for me immediately. The solution he discusses for a fuzzy character match dubbed accent folding seems logical, especially in certain contexts. Beyond those contexts, the problem of transliteration gets complicated quickly. link</description>
			<content:encoded><![CDATA[<p>Carlos Bueno highlights an oft overlooked aspect of internationalization. His address book auto-complete example at the beginning of the article crystalized the problem for me immediately. The solution he discusses for a fuzzy character match dubbed <em>accent folding</em> seems logical, especially in certain contexts. Beyond those contexts, the problem of transliteration gets complicated quickly. <a class="linkurl" href="http://www.alistapart.com/articles/accent-folding-for-auto-complete/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/5Pslm8LGT_w" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2010/02/23/accent-folding-for-auto-complete.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>50 Useful Coding Techniques</title>
		<link>http://stopdesign.com/archive/2010/02/21/50-useful-coding-techniques.html</link>
		<comments>http://stopdesign.com/archive/2010/02/21/50-useful-coding-techniques.html#comments</comments>
		<pubDate>Sun, 21 Feb 2010 15:13:41 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[javascript]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2010/02/21/50-useful-coding-techniques.html</guid>
		<description>Smashing Magazine rounds up a few tricks for &amp;#8220;CSS Layouts, Visual Effects and Forms&amp;#8221;. Not everything in here looks useful to me, but I did notice a few gems while quickly browsing through. Bookmarked for later investigation. link</description>
			<content:encoded><![CDATA[<p>Smashing Magazine rounds up a few tricks for &#8220;CSS Layouts, Visual Effects and Forms&#8221;. Not everything in here looks useful to me, but I did notice a few gems while quickly browsing through. Bookmarked for later investigation. <a class="linkurl" href="http://www.smashingmagazine.com/2010/02/18/50-css-and-javascript-techniques-for-layouts-forms-and-visual-effects/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/nrXWU3IK_Vc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2010/02/21/50-useful-coding-techniques.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking Back at Google in 2009</title>
		<link>http://stopdesign.com/archive/2009/12/29/looking-back-at-google-in-2009.html</link>
		<comments>http://stopdesign.com/archive/2009/12/29/looking-back-at-google-in-2009.html#comments</comments>
		<pubDate>Tue, 29 Dec 2009 22:38:32 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[technology]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/12/29/looking-back-at-google-in-2009.html</guid>
		<description>A fairly thorough retrospective of Google and the huge impact the company had over the past year. Check out the list of releases and new ideas Google pushed in 2009. Impressive and scary at the same time. I wish the little blip about me leaving earlier this year weren&amp;#8217;t present, though I&amp;#8217;ll admit that&amp;#8217;s how [...]</description>
			<content:encoded><![CDATA[<p>A fairly thorough retrospective of Google and the huge impact the company had over the past year. Check out the list of releases and new ideas Google pushed in 2009. Impressive and scary at the same time. I wish the little blip about me leaving earlier this year weren&#8217;t present, though I&#8217;ll admit that&#8217;s how I found this article. This paragraph toward the end sums it up best:</p>
<blockquote><p>Google in late 2009 is now covering or aiming to cover web apps, the browser that runs the web apps, the OS that runs the browser, and, according to rumors, even the computer that runs the OS.</p></blockquote>
<p><a class="linkurl" href="http://blogoscoped.com/archive/2009-12-23-n43.html">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/BSGGy2O5YTY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/12/29/looking-back-at-google-in-2009.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Success secrets of graphic designer superstars</title>
		<link>http://stopdesign.com/archive/2009/12/29/success-secrets-of-graphic-designer-superstars.html</link>
		<comments>http://stopdesign.com/archive/2009/12/29/success-secrets-of-graphic-designer-superstars.html#comments</comments>
		<pubDate>Tue, 29 Dec 2009 17:14:06 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[inspiration]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/12/29/success-secrets-of-graphic-designer-superstars.html</guid>
		<description>Worth skimming through, if even just for the eye candy. But also for each designer&amp;#8217;s nuggets of wisdom. link</description>
			<content:encoded><![CDATA[<p>Worth skimming through, if even just for the eye candy. But also for each designer&#8217;s nuggets of wisdom. <a class="linkurl" href="http://willsherwood.com/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/d3jS7T2zx2E" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/12/29/success-secrets-of-graphic-designer-superstars.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Perfect Pitch</title>
		<link>http://stopdesign.com/archive/2009/11/03/perfect-pitch.html</link>
		<comments>http://stopdesign.com/archive/2009/11/03/perfect-pitch.html#comments</comments>
		<pubDate>Tue, 03 Nov 2009 16:58:50 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[perfectpitch]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/11/03/perfect-pitch.html</guid>
		<description>Helping Adactio get that perfect pitch. To nail it, even. You should probably link to his page too, if you&amp;#8217;re so inclined to fight DMCA take-downs for the sake of SEO. link</description>
			<content:encoded><![CDATA[<p>Helping Adactio get that perfect pitch. To nail it, even. You should probably link to his page too, if you&#8217;re so inclined to fight DMCA take-downs for the sake of SEO. <a class="linkurl" href="http://adactio.com/journal/1623/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/yoQbr2qgq6Q" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/11/03/perfect-pitch.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Bottom Posting Sucks</title>
		<link>http://stopdesign.com/archive/2009/10/01/why-bottom-posting-sucks.html</link>
		<comments>http://stopdesign.com/archive/2009/10/01/why-bottom-posting-sucks.html#comments</comments>
		<pubDate>Fri, 02 Oct 2009 05:58:49 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[email]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/10/01/why-bottom-posting-sucks.html</guid>
		<description>I agree. Time for the end of bottom-posting arguments. link</description>
			<content:encoded><![CDATA[<p>I agree. Time for the end of bottom-posting arguments. <a class="linkurl" href="http://www.molly.com/2009/09/29/why-bottom-posting-sucks/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/vmuUbGcojsg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/10/01/why-bottom-posting-sucks.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Deep Breath</title>
		<link>http://stopdesign.com/archive/2009/06/01/a-deep-breath.html</link>
		<comments>http://stopdesign.com/archive/2009/06/01/a-deep-breath.html#comments</comments>
		<pubDate>Mon, 01 Jun 2009 16:38:48 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[stress]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/06/01/a-deep-breath.html</guid>
		<description>You’re encouraging the random and random is how you’re going to win. Random is how you’re going to discover a path through a problem that no one else has found and that starts with breathing deeply.
Even though the subject matter and approach differs, this pairs nicely with an article on A List Apart last week: [...]</description>
			<content:encoded><![CDATA[<blockquote><p>You’re encouraging the random and random is how you’re going to win. Random is how you’re going to discover a path through a problem that no one else has found and that starts with breathing deeply.</p></blockquote>
<p>Even though the subject matter and approach differs, this pairs nicely with an article on A List Apart last week: <a href="http://www.alistapart.com/articles/burnout/">Burnout</a>, by Scott Boms.</p>
<blockquote><p>Your life should be just that—a life</p></blockquote>
<p>Good words, all around. <a class="linkurl" href="http://www.randsinrepose.com/archives/2009/06/01/a_deep_breath.html">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/NNidVroX46U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/06/01/a-deep-breath.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Introducing Typekit</title>
		<link>http://stopdesign.com/archive/2009/05/28/introducing-typekit.html</link>
		<comments>http://stopdesign.com/archive/2009/05/28/introducing-typekit.html#comments</comments>
		<pubDate>Thu, 28 May 2009 16:42:51 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/28/introducing-typekit.html</guid>
		<description>Emphasis is my own&amp;#8230;
As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. This really is [...]</description>
			<content:encoded><![CDATA[<p>Emphasis is my own&#8230;</p>
<blockquote><p>As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. <strong>This really is going to change web design.</strong></p></blockquote>
<p>Also worth checking out, Jeff posted a <a href="http://www.flickr.com/photos/veen/3572372312/">preview of the Typekit home page</a> yesterday. Looking forward to how this will change typography and design for the web. <a class="linkurl" href="http://blog.typekit.com/2009/05/27/introducing-typekit/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/rTHj_k7vrrA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/28/introducing-typekit.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Universal Internet Explorer 6 CSS</title>
		<link>http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html</link>
		<comments>http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html#comments</comments>
		<pubDate>Thu, 21 May 2009 02:00:33 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[browser]]></category>
		<category><![CDATA[css]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html</guid>
		<description>Mr. Clarke advocates creating one single universal style sheet to handle all styling in IE6, and to stop worrying about making content in IE6 look anything like the high-end experience.
I&amp;#8217;m now advocating to my clients (and to you), that where feasible, not to waste hours in time and a client&amp;#8217;s money on lengthy workarounds in [...]</description>
			<content:encoded><![CDATA[<p>Mr. Clarke advocates creating one single universal style sheet to handle all styling in IE6, and to stop worrying about making content in IE6 look anything like the high-end experience.</p>
<blockquote><p>I&#8217;m now advocating to my clients (and to you), that where feasible, not to waste hours in time and a client&#8217;s money on lengthy workarounds in an unnecessary attempt at cross-browser perfection. Instead, you and I should provide simple but effectively designed HTML elements. This means just great typography for headings, paragraphs, quotations, lists, tables and forms and no styling of layout.</p></blockquote>
<p>This will work well for content-focused web sites. And then maybe it&#8217;s officially time to completely drop support of IE6 for web apps. <a class="linkurl" href="http://forabeautifulweb.com/blog/about/universal_internet_explorer_6_css">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/JeZS28NjOGA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/20/universal-internet-explorer-6-css.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Welcome, Wired. We call this land "Internet"</title>
		<link>http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html</link>
		<comments>http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html#comments</comments>
		<pubDate>Tue, 19 May 2009 19:00:34 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[wired]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html</guid>
		<description>Interesting take on the future of Wired (mag vs. website).
Wired is great print, but if the magazine can&amp;#8217;t make money and is shuttered, taking the website down with it, I&amp;#8217;m going to be livid. Not that making money online is easy—it&amp;#8217;s not, especially without sacrificing your ethics and your voice—but if any mainstream outlet should [...]</description>
			<content:encoded><![CDATA[<p>Interesting take on the future of <cite>Wired</cite> (mag vs. website).</p>
<blockquote><p>Wired is great print, but if the magazine can&#8217;t make money and is shuttered, taking the website down with it, I&#8217;m going to be livid. Not that making money online is easy—it&#8217;s not, especially without sacrificing your ethics and your voice—but if any mainstream outlet should be able to make the transition, it should be Wired.</p>
<p>I fear that may be impossible, not just for Wired but for all these old brands, because they can&#8217;t accept that the work at which they have excelled for years will be just as important when it&#8217;s online—and online only.</p></blockquote>
<p>Reading though the comments provides an even more interesting story and a broader perspective. Comments by several former and current Wiredlings, including a few responses by Chris Anderson who passes blame to corporate (Conde Nast) decision-making. <a class="linkurl" href="http://gadgets.boingboing.net/2009/05/18/welcome-wired-we-cal.html">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/LPZCxAnw7pc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/19/welcome-wired-we-call-this-land-internet.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great Designs Should Be Experienced and Not Seen</title>
		<link>http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html</link>
		<comments>http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html#comments</comments>
		<pubDate>Thu, 14 May 2009 22:00:14 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html</guid>
		<description>The best design is that which does its job and stays out of the way. Jared Spool on invisible design:
While all these things are what the designers at Netflix work hard on every day, they go unmentioned by their customers. It&amp;#39;s not because these aspects aren&amp;#39;t important. It&amp;#39;s because the designers have done their job [...]</description>
			<content:encoded><![CDATA[<p>The best design is that which does its job and stays out of the way. Jared Spool on invisible design:</p>
<blockquote><p>While all these things are what the designers at Netflix work hard on every day, they go unmentioned by their customers. It&#39;s not because these aspects aren&#39;t important. It&#39;s because the designers have done their job really well: they&#39;ve made them invisible.</p></blockquote>
<p> <a class="linkurl" href="http://www.uie.com/articles/experiencedesign">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/ktLia4HTA4o" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/14/great-designs-should-be-experienced-and-not-seen.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Choices</title>
		<link>http://stopdesign.com/archive/2009/05/08/choices.html</link>
		<comments>http://stopdesign.com/archive/2009/05/08/choices.html#comments</comments>
		<pubDate>Fri, 08 May 2009 17:21:29 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/05/08/choices.html</guid>
		<description>Craig directed me to this piece today after I complimented him on the new version of Twitterrific for the iPhone, stating how much I love seeing different approaches to Twitter client design. I hadn&amp;#8217;t seen his post (from December 2008) before today, but it&amp;#8217;s a good read that gives insight into some of the decisions [...]</description>
			<content:encoded><![CDATA[<p>Craig directed me to this piece today after I complimented him on the new version of Twitterrific for the iPhone, stating how much I love seeing different approaches to Twitter client design. I hadn&#8217;t seen his post (from December 2008) before today, but it&#8217;s a good read that gives insight into some of the decisions behind Twitteriffic&#8217;s design that are still applicable now.</p>
<blockquote><p>Personally, I welcome this competition. Seeing the work of other developers whose work I respect and admire acts as an inspiration. Looking at how other developers tackle a problem domain often adds insight into solving similar issues with my own code. In other cases, it shows me how I don’t want to implement a feature (without the need to prototype.) In short, competition will make <a href="http://iconfactory.com/twitterrific">Twitterrific</a> better.</p></blockquote>
<p><a class="linkurl" href="http://furbo.org/2008/12/02/choices/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/7qYBb25y6g0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/05/08/choices.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Time to move beyond 960?</title>
		<link>http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html</link>
		<comments>http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html#comments</comments>
		<pubDate>Thu, 23 Apr 2009 21:36:12 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html</guid>
		<description>Cameron asks the inevitable question about width on the Web. Probably not time yet for mainstream. But for showcases of design, why not start experimenting with the new real estate? link</description>
			<content:encoded><![CDATA[<p>Cameron asks the inevitable question about width on the Web. Probably not time yet for mainstream. But for showcases of design, why not start experimenting with the new real estate? <a class="linkurl" href="http://cameronmoll.com/archives/2009/04/is_it_time_to_move_beyond_960/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/8tYD6Q9pmVU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/23/time-to-move-beyond-960.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tal Leming on Web Fonts</title>
		<link>http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html</link>
		<comments>http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html#comments</comments>
		<pubDate>Wed, 22 Apr 2009 17:56:32 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[type]]></category>
		<category><![CDATA[typography]]></category>
		<category><![CDATA[webfonts]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html</guid>
		<description>Seemingly reasonable middle-ground suggestions here that would allow web typography to move forward, allow people to use all the free fonts they want, yet continue to allow type designers to earn a living. link</description>
			<content:encoded><![CDATA[<p>Seemingly reasonable middle-ground suggestions here that would allow web typography to move forward, allow people to use all the free fonts they want, yet continue to allow type designers to earn a living. <a class="linkurl" href="http://talleming.com/2009/04/21/web-fonts/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/D__fiXlx1FM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/22/tal-leming-on-web-fonts.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>In Defense of Eye Candy</title>
		<link>http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html</link>
		<comments>http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html#comments</comments>
		<pubDate>Wed, 22 Apr 2009 17:42:35 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[beauty]]></category>
		<category><![CDATA[design]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html</guid>
		<description>Stephen Anderson:
The more we learn about people, and how our brains process information, the more we learn the truth of that phrase: form and function aren’t separate items. If we believe that style somehow exists independent of functionality, that we can treat aesthetics and function as two separate pieces, then we ignore the evidence that [...]</description>
			<content:encoded><![CDATA[<p>Stephen Anderson:</p>
<blockquote><p>The more we learn about people, and how our brains process information, the more we learn the truth of that phrase: form and function aren’t separate items. If we believe that style somehow exists independent of functionality, that we can treat aesthetics and function as two separate pieces, then we ignore the evidence that beauty is much more than decoration. Our brains can’t help but agree.</p></blockquote>
<p>Can&#8217;t say that I agree with all the examples he used. But important points that stand on their own, nonetheless. <a class="linkurl" href="http://www.alistapart.com/articles/indefenseofeyecandy">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/ULtLIuFwmAo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/22/in-defense-of-eye-candy.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fluid Images</title>
		<link>http://stopdesign.com/archive/2009/04/17/fluid-images.html</link>
		<comments>http://stopdesign.com/archive/2009/04/17/fluid-images.html#comments</comments>
		<pubDate>Sat, 18 Apr 2009 01:00:03 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/17/fluid-images.html</guid>
		<description>Nice going, Ethan. Definitely one to keep in the ol&amp;#8217; bag o&amp;#8217; tricks. link</description>
			<content:encoded><![CDATA[<p>Nice going, Ethan. Definitely one to keep in the ol&#8217; bag o&#8217; tricks. <a class="linkurl" href="http://unstoppablerobotninja.com/entry/fluid-images/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/MQF1vcji9Ys" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/17/fluid-images.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Apple notebook packaging comparison</title>
		<link>http://stopdesign.com/archive/2009/04/12/apple-packaging.html</link>
		<comments>http://stopdesign.com/archive/2009/04/12/apple-packaging.html#comments</comments>
		<pubDate>Mon, 13 Apr 2009 05:54:01 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[entries]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[packaging]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/12/apple-notebook-packaging-comparison.html</guid>
		<description>Interesting comparison (my own) of packaging for Apple notebooks. I&amp;#8217;ve been noticing a trend over the last few years to cut way down on box size for both hardware and software. But I still think it&amp;#8217;s interesting to see side-by-side comparisons for similar items over time. This first photo shows the original box for a [...]</description>
			<content:encoded><![CDATA[<p>Interesting comparison (my own) of packaging for Apple notebooks. I&#8217;ve been noticing a trend over the last few years to cut way down on box size for both hardware and software. But I still think it&#8217;s interesting to see side-by-side comparisons for similar items over time. This <a href="http://www.flickr.com/photos/stop/3437277676/">first photo</a> shows the original box for a 12&quot; PowerBook G4 purchased in 2004 (black box) next to the box for the current generation 15&quot; MacBook Pro (white box) purchased in 2009.</p>
<p>Another <a href="http://www.flickr.com/photos/stop/3436482831/">similar photo</a> compares packaging for the 12&quot; iBook purchased in 2006 next to the box for the current 13&quot; white MacBook purchased in 2009.</p>
<p>In both cases, the newer notebook is <strong>larger</strong> than the older notebook, yet still uses a much <strong>smaller</strong> box.</p>
<p>After recent Unboxings&trade; of the MB and MBP, I noted there&#8217;s no less &#8220;stuff&#8221; in the box as far as hardware, adapters, install discs, and printed material. The new packaging designs just forgo the thick molded styrofoam padding of the old boxes.</p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/64gZW6-Bu5U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/12/apple-packaging.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Attribution and Affiliation on All Things Digital</title>
		<link>http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html</link>
		<comments>http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html#comments</comments>
		<pubDate>Thu, 09 Apr 2009 16:27:25 +0000</pubDate>
		<dc:creator>Douglas Bowman</dc:creator>
				<category><![CDATA[links]]></category>
		<category><![CDATA[attribution]]></category>
		<category><![CDATA[content]]></category>

		<guid isPermaLink="false">http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html</guid>
		<description>Andy Baio digs into the reuse of certain content by AllThingsD for their Voices section:
Ultimately, if authors are happy, there&amp;#8217;s no problem. But it seems like there&amp;#8217;s a divide between two types of writers online: unaffiliated independent bloggers running their own sites and bloggers employed by larger online magazines.
Also, be sure to read the related [...]</description>
			<content:encoded><![CDATA[<p>Andy Baio digs into the reuse of certain content by AllThingsD for their <a href="http://voices.allthingsd.com/">Voices</a> section:</p>
<blockquote><p>Ultimately, if authors are happy, there&#8217;s no problem. But it seems like there&#8217;s a divide between two types of writers online: unaffiliated independent bloggers running their own sites and bloggers employed by larger online magazines.</p></blockquote>
<p>Also, be sure to read the <a href="http://dashes.com/anil/2009/04/fair-use-for-fair-people.html">related response from Anil Dash</a> about how the Associated Press plans to handle a similar reuse of content:</p>
<blockquote><p>If the Associated Press made its argument on the basis of credibility and reputation, transparency and accountability, as the web-native publishers have, it would be far easier to defend their desire to share in the business model developed by the aggregators.</p></blockquote>
<p><a class="linkurl" href="http://waxy.org/2009/04/all_things_digital_and_transparency_in_online_journalism/">link</a></p>
<img src="http://feeds.feedburner.com/~r/stopdesign/~4/07EMLj7XJeI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://stopdesign.com/archive/2009/04/09/attribution-and-affiliation-on-all-things-digital.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss><!-- Dynamic page generated in 0.422 seconds. --><!-- Cached page generated by WP-Super-Cache on 2010-03-13 08:29:42 --><!-- Compression = gzip -->
