<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Small things; How Facebook and Twitter share new features</title>
	<atom:link href="http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Fri, 12 Mar 2010 04:42:03 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dion</title>
		<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/comment-page-1#comment-39683</link>
		<dc:creator>dion</dc:creator>
		<pubDate>Wed, 01 Oct 2008 17:14:09 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features#comment-39683</guid>
		<description>@Iraê - Good idea, that would be cool.

@Daniel - Yah, you are right. The X should be a minimize.

@Scott - SWF FTW :)

@Brendan - I agree. They need to keep track of that so it doesn&#039;t pop back up :)</description>
		<content:encoded><![CDATA[<p>@Iraê &#8211; Good idea, that would be cool.</p>
<p>@Daniel &#8211; Yah, you are right. The X should be a minimize.</p>
<p>@Scott &#8211; SWF FTW :)</p>
<p>@Brendan &#8211; I agree. They need to keep track of that so it doesn&#8217;t pop back up :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Gibson</title>
		<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/comment-page-1#comment-39682</link>
		<dc:creator>Brendan Gibson</dc:creator>
		<pubDate>Wed, 01 Oct 2008 17:09:36 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features#comment-39682</guid>
		<description>Have to disagree with you there, Dion.  I find the twitter bar incredibly annoying.  Every time you refresh the page - it&#039;s back up there...</description>
		<content:encoded><![CDATA[<p>Have to disagree with you there, Dion.  I find the twitter bar incredibly annoying.  Every time you refresh the page &#8211; it&#8217;s back up there&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Morgan</title>
		<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/comment-page-1#comment-39681</link>
		<dc:creator>Scott Morgan</dc:creator>
		<pubDate>Wed, 01 Oct 2008 15:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features#comment-39681</guid>
		<description>Another option would be to store the persistent data in a Flash Shared Object. A lot of sites are doing this now. Load a small 5x5 pixel swf on to the page, use javascript to communicate with the swfs API (which are just hooks into the getters and setters of the Shared Object). You can even roll back to flash 8 or 7 so you can almost be guaranteed that everyone has the proper player on their system, if they don&#039;t have Flash you can just use standard cookies. Shared Objects are a lot more difficult to accidently delete. If you really wanted to get fancy you could use the AS3 corelib library and store a JSON object in the shared object (this approach would require Flash Player 9).</description>
		<content:encoded><![CDATA[<p>Another option would be to store the persistent data in a Flash Shared Object. A lot of sites are doing this now. Load a small 5&#215;5 pixel swf on to the page, use javascript to communicate with the swfs API (which are just hooks into the getters and setters of the Shared Object). You can even roll back to flash 8 or 7 so you can almost be guaranteed that everyone has the proper player on their system, if they don&#8217;t have Flash you can just use standard cookies. Shared Objects are a lot more difficult to accidently delete. If you really wanted to get fancy you could use the AS3 corelib library and store a JSON object in the shared object (this approach would require Flash Player 9).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Shaw</title>
		<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/comment-page-1#comment-39680</link>
		<dc:creator>Daniel Shaw</dc:creator>
		<pubDate>Wed, 01 Oct 2008 15:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features#comment-39680</guid>
		<description>Glad to know that clicking on the &#039;X&#039; minimizes the election bar. I never clicked on it because I had assumed that it would go away (&quot;close&quot;). Some sort of minimize icon might have been more semantic. Maybe even a slightly modified down arrow that would match the restore indicator, but not appear to be  a drop down menu.</description>
		<content:encoded><![CDATA[<p>Glad to know that clicking on the &#8216;X&#8217; minimizes the election bar. I never clicked on it because I had assumed that it would go away (&#8221;close&#8221;). Some sort of minimize icon might have been more semantic. Maybe even a slightly modified down arrow that would match the restore indicator, but not appear to be  a drop down menu.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Iraê</title>
		<link>http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features/comment-page-1#comment-39679</link>
		<dc:creator>Iraê</dc:creator>
		<pubDate>Wed, 01 Oct 2008 14:04:08 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/small-things-how-facebook-and-twitter-share-new-features#comment-39679</guid>
		<description>This could be a simple, yet useful thing to implement with HTML5 local database (or gears maybe). They could keep a local copy of a series of actions already taken by the user (i.e. closed that sign, personalized the template, used this or that new feature, etc) and adjust the interface accordingly.

Cookies could become too big to be usefull here and server databese storage could cost more to the site them it benefits from the feature.

Great post. This kind of thing always annoys me too.</description>
		<content:encoded><![CDATA[<p>This could be a simple, yet useful thing to implement with HTML5 local database (or gears maybe). They could keep a local copy of a series of actions already taken by the user (i.e. closed that sign, personalized the template, used this or that new feature, etc) and adjust the interface accordingly.</p>
<p>Cookies could become too big to be usefull here and server databese storage could cost more to the site them it benefits from the feature.</p>
<p>Great post. This kind of thing always annoys me too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
