<?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; best practices</title>
	<atom:link href="http://blog.isnoop.net/tag/best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.isnoop.net</link>
	<description>It&#039;s a Doozy!</description>
	<lastBuildDate>Wed, 11 Nov 2009 10:33:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<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>8</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 names [...]]]></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>
	</channel>
</rss>
