<?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>cdevroe.com &#187; urls</title>
	<atom:link href="http://cdevroe.com/tag/urls/feed/" rel="self" type="application/rss+xml" />
	<link>http://cdevroe.com</link>
	<description>by Colin Devroe</description>
	<lastBuildDate>Fri, 25 May 2012 18:07:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>	<atom:link rel='hub' href='http://cdevroe.com/?pushpress=hub'/>
<cloud domain='cdevroe.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Twitter&#8217;s URL shortening technique makes copy/paste difficult</title>
		<link>http://cdevroe.com/notes/twitter-url-copypaste/</link>
		<comments>http://cdevroe.com/notes/twitter-url-copypaste/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 17:02:56 +0000</pubDate>
		<dc:creator>Colin Devroe</dc:creator>
				<category><![CDATA[Notes]]></category>
		<category><![CDATA[bit.ly]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[url shortening]]></category>
		<category><![CDATA[urls]]></category>

		<guid isPermaLink="false">http://cdevroe.com/?p=3232</guid>
		<description><![CDATA[Twitter, by default, uses Bit.ly to shorten URLs for use with SMS, the API, etc. But on its Web site Twitter shows you the original URL (or at least part of it) so that people know where they&#8217;ll be going if they click on the link. Or, at least that is why I think they [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter, by default, uses Bit.ly to shorten URLs for use with SMS, the API, etc. But on its Web site Twitter shows you the original URL (or at least part of it) so that people know where they&#8217;ll be going if they click on the link. Or, at least that is why I think they are doing it. If they were to keep the Bit.ly URL then people wouldn&#8217;t know what will happen if they click on the link.</p>
<p>However, this causes some problems when trying to copy/paste a tweet. See the screenshot of <a href="http://twitter.com/cdevroe/status/5997875149">this tweet</a>.</p>
<p><a href="http://twitter.com/cdevroe/status/5997875149"><img src="http://cdevroe.com/wp-content/mobile/photos/2009/11/Twitter-_-Colin-Devroe_-The-last-item-we-need-to-s-....jpg" alt="Twitter, short url" title="Twitter, short url" width="460" /></a></p>
<p>If you try to copy/paste that Tweet you&#8217;ll end up getting an unusable URL. Perhaps Twitter should throw the 140 character limit out of the window on the tweet permalinks to make the full URL visible. This would make it easier to copy/paste but also simple to see whether or not the URL you are clicking on will lead to a Web page, a PDF file, an MP3 file, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://cdevroe.com/notes/twitter-url-copypaste/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>These aren&#8217;t the droids you&#8217;re looking for URLs</title>
		<link>http://cdevroe.com/notes/no-droids-here/</link>
		<comments>http://cdevroe.com/notes/no-droids-here/#comments</comments>
		<pubDate>Mon, 10 Aug 2009 14:45:29 +0000</pubDate>
		<dc:creator>Colin Devroe</dc:creator>
				<category><![CDATA[Notes]]></category>
		<category><![CDATA[404]]></category>
		<category><![CDATA[best-practices]]></category>
		<category><![CDATA[error pages]]></category>
		<category><![CDATA[kyle slattery]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[urls]]></category>
		<category><![CDATA[web site]]></category>
		<category><![CDATA[web-development]]></category>

		<guid isPermaLink="false">http://cdevroe.com/?p=2668</guid>
		<description><![CDATA[Page not found. Error 404. Those of us that build Web sites for a living have all had to deal with creating these pages. Planning for people to stumble across a URL that we don&#8217;t plan on is fairly important to the user&#8217;s experience on your site. However, many 404 pages could be done better. [...]]]></description>
			<content:encoded><![CDATA[<p>Page not found. Error 404. Those of us that build Web sites for a living have all had to deal with creating these pages. Planning for people to stumble across a URL that we don&#8217;t plan on is fairly important to the user&#8217;s experience on your site. However, many 404 pages could be done better. Today we&#8217;re going to focus on one use case &#8211; the uses when you know what the user is actually looking for Â you just know you don&#8217;t have it.</p>
<p>Fellow Viddler and friend <a href="http://kyleslattery.com">Kyle Slattery</a> is reworking his tag search pages. He&#8217;s created a really nice way to filter through the various types of content on his site based on tag search results. For instance, going to <a href="http://kyleslattery.com/notebook/tags/colindevroe">a tag search for my name</a> will result in a few photos and a few links that he tagged with my name. You can then filter those results to <a href="http://kyleslattery.com/notebook/photos/tags/colindevroe">only show you the photos</a> or <a href="http://kyleslattery.com/notebook/links/tags/colindevroe">only the links</a>.</p>
<p>But what if you hack the URL and <a href="http://kyleslattery.com/notebook/links/tags/asdf">search for a tag that shows no results</a>? At current Kyle shows an error page. However, there was no error. His Web site should never link you to a page that doesn&#8217;t return any results (<a href="http://kyleslattery.com/notebook/entries/tags/colindevroe">though it does right now</a>). So how did the person end up here? They may have done a search, they may have hacked the URL, or someone else linked them to this page. Which ever way they ended up on that URL &#8211; there is still no reason to show an error.</p>
<p>This brings me to why I call these types of URLs &#8220;These aren&#8217;t the droids you&#8217;re looking for URLs&#8221;. These are URLs where you know what the person is looking for (droids) you just don&#8217;t have any. In the example URL I use above, a tag search for my name filtered by entries, Kyle does a good job of stating that there are no entries tagged with my name. This is much better than showing an error. In the other example, of a tag search that ultimately returns no results, he should do something very similar. This isn&#8217;t an error. There is just no content on his site that is tagged with &#8216;asdf&#8217;.</p>
<p>One of the suggestions I gave to him was to do a search through his own tags and try to see if, perhaps, they&#8217;ve mistyped the tag. I&#8217;m not sure what &#8216;asdf&#8217; could have been, maybe sad? Or, what if someone spells my name with two Ls? This isn&#8217;t easy to program against &#8211; but there is an easier option that he could set up. Offer a search box with the tag that they entered already filled in and show a message of &#8220;Sorry, but I have nothing tagged with &#8216;asdf&#8217;. Maybe you misspelled what you&#8217;re looking for?&#8221;</p>
<p>My site isn&#8217;t a good example of best practices here. It used to be. But I had to hack WordPress to bits to get it to work last time and I&#8217;ve since upgraded WordPress too many times for those old hacks to work. However, if you&#8217;re looking for good examples &#8211; I&#8217;m sure Kyle&#8217;s site will end up being a pretty good example soon enough.</p>
<p>Have you seen any really good examples of this?</p>
]]></content:encoded>
			<wfw:commentRss>http://cdevroe.com/notes/no-droids-here/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>FriendFeed on the iPhone</title>
		<link>http://cdevroe.com/links/friendfeed-iphone/</link>
		<comments>http://cdevroe.com/links/friendfeed-iphone/#comments</comments>
		<pubDate>Tue, 01 Jul 2008 13:20:47 +0000</pubDate>
		<dc:creator>Colin Devroe</dc:creator>
				<category><![CDATA[Links]]></category>
		<category><![CDATA[flickr]]></category>
		<category><![CDATA[friendfeed]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[mobile]]></category>
		<category><![CDATA[techcrunch]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[urls]]></category>

		<guid isPermaLink="false">http://cdevroe.com/?p=831</guid>
		<description><![CDATA[FriendFeed launches an iPhone-friendly version of their Website, and I think it is great.]]></description>
			<content:encoded><![CDATA[<p><img title="iPhone version of FriendFeed" src="http://cdevroe.com/wp-content/mobile/photos/2008/07/s5000151.jpg" alt="An iPhone with FriendFeed on it." /></p>
<p><a href="http://friendfeed.com/">FriendFeed</a>, of which <a href="http://friendfeed.com/">I&#8217;m a member</a>, recently launched an iPhone-friendly version of their site. Â Notably, however, they&#8217;ve done it in such a way that I much prefer to some of the ways other sites have done it. Â They detect the iPhone&#8217;s mobile browser and automatically format it for you, rather than requiring you to remember the URL of the iPhone-friendly site.</p>
<p><a href="http://flickr.com/">Flickr</a>, on the other hand, has <a href="http://m.flickr.com/">a mobile Website</a> that &#8211; while it works fairly well on the iPhone (though it isn&#8217;t built for it) &#8211; is notÂ interchangeableÂ with the normal Website. Â What I mean to say is, if someone links me to a Flickr photo on my iPhone either <a href="http://twitter.com/cdevroe/">via Twitter</a>, FriendFeed, or even through an SMS message &#8211; I&#8217;m forced to be taken to the full-fledged, slow-loading Website without so much as the choice of loading the mobile version. Â At least with Twitter I&#8217;m able to simply prepend the URL with m.*, which switches the site into &#8220;mobile mode&#8221;, and see the same content. Â Flickr&#8217;s URLs for their mobile site aren&#8217;t hackable.</p>
<p>FriendFeed does have hackable URLs ((Just insert /iphone/ into any URL.)). Combine the hackability of their URLs with the detection of the iPhone and you&#8217;ve got nearly a perfect solution for iPhone users.</p>
<p>Side note: I love the FriendFeed looks nearly the same on my iPhone as it does on my personal computer. Â FriendFeed&#8217;s design lends itself to this because of its simplicity, lightness, and straight-forward &#8220;the content is the design&#8221; approach.</p>
<p>Source:Â <a href="http://blog.friendfeed.com/2008/06/friendfeed-iphone-interface.html">FriendFeed iPhone interface</a>.<br />
Via: <a href="http://www.techcrunch.com/2008/06/30/friendfeed-finally-gets-iphone-friendly/">TechCrunch: FriendFeed Finally Gets iPhone Friendly</a> ((I don&#8217;t like the use of the word finally in this title.)).</p>
]]></content:encoded>
			<wfw:commentRss>http://cdevroe.com/links/friendfeed-iphone/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

