<?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>isnoop.net blog &#187; UI</title>
	<atom:link href="http://blog.isnoop.net/tag/ui/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.isnoop.net</link>
	<description>It&#039;s a Doozy!</description>
	<lastBuildDate>Tue, 22 Nov 2011 17:53:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Web Developers: Don’t Be Password Idiots</title>
		<link>http://blog.isnoop.net/2009/06/22/web-developers-don%e2%80%99t-be-password-idiots/</link>
		<comments>http://blog.isnoop.net/2009/06/22/web-developers-don%e2%80%99t-be-password-idiots/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 17:08:06 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Sites of Interest]]></category>
		<category><![CDATA[annoyances]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[passwords]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.isnoop.net/?p=319</guid>
		<description><![CDATA[As a follow-up to my last post, here are a few tips to help keep you from driving your site users away with misguided password restrictions. #1: Consider Context Your tweets may be precious to you, but as a web developer, you should understand the differences between password security for Twitter and for online banking. [...]]]></description>
		<wfw:commentRss>http://blog.isnoop.net/2009/06/22/web-developers-don%e2%80%99t-be-password-idiots/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Web Developers: Don&#8217;t Be Username Idiots</title>
		<link>http://blog.isnoop.net/2009/06/18/web-developers-dont-be-username-idiots/</link>
		<comments>http://blog.isnoop.net/2009/06/18/web-developers-dont-be-username-idiots/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 22:34:35 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Opinion]]></category>
		<category><![CDATA[Rants]]></category>
		<category><![CDATA[Sites of Interest]]></category>
		<category><![CDATA[annoyances]]></category>
		<category><![CDATA[best practices]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.isnoop.net/?p=313</guid>
		<description><![CDATA[Just a quick note to any developer, site owner, or project manager who is in charge of developing a user login system: Don&#8217;t put unreasonable restrictions on usernames. It is sensible to prevent people from creating names containing certain characters or names of extreme length. However, some sites go too far by requiring all user [...]]]></description>
		<wfw:commentRss>http://blog.isnoop.net/2009/06/18/web-developers-dont-be-username-idiots/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Me blog pretty</title>
		<link>http://blog.isnoop.net/2009/06/18/me-blog-pretty/</link>
		<comments>http://blog.isnoop.net/2009/06/18/me-blog-pretty/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 16:11:04 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[annoyances]]></category>
		<category><![CDATA[UI]]></category>

		<guid isPermaLink="false">http://blog.isnoop.net/?p=306</guid>
		<description><![CDATA[They say clothes make the man, so it stands to reason that the theme makes the blog. After receiving several moans about my blog&#8217;s styling, I&#8217;ve finally decided to do something about it. No more Kubrik theme for me. For those who don&#8217;t care for the WordPress default theme, I do hope this one is [...]]]></description>
		<wfw:commentRss>http://blog.isnoop.net/2009/06/18/me-blog-pretty/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>On Omitting Protocols From HTTP/HTTPS URLs</title>
		<link>http://blog.isnoop.net/2007/09/14/on-omitting-protocols-from-httphttps-urls/</link>
		<comments>http://blog.isnoop.net/2007/09/14/on-omitting-protocols-from-httphttps-urls/#comments</comments>
		<pubDate>Fri, 14 Sep 2007 21:54:47 +0000</pubDate>
		<dc:creator>Ian</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[UI]]></category>
		<category><![CDATA[UX]]></category>

		<guid isPermaLink="false">http://isnoop.net/blog/2007/09/14/on-omitting-protocols-from-httphttps-urls/</guid>
		<description><![CDATA[Many websites offer the flexibility to display the same page via both SSL and HTTP. The major problem with offering this is the possibility that embedded content will not be served via the same protocol; many browsers will throw an error if an SSL page embeds HTTP images. However, there is a simple and W3C [...]]]></description>
		<wfw:commentRss>http://blog.isnoop.net/2007/09/14/on-omitting-protocols-from-httphttps-urls/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

