<?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: Mike Hanson, Douglas Crockford, and Facebook; A tale of security, privacy, and performance</title>
	<atom:link href="http://almaer.com/blog/mike-hanson-douglas-crockford-and-facebook-a-tale-of-security-privacy-and-performance/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/mike-hanson-douglas-crockford-and-facebook-a-tale-of-security-privacy-and-performance</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</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/mike-hanson-douglas-crockford-and-facebook-a-tale-of-security-privacy-and-performance/comment-page-1#comment-46488</link>
		<dc:creator>dion</dc:creator>
		<pubDate>Sat, 24 Apr 2010 18:58:20 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2666#comment-46488</guid>
		<description>Chris,

Thanks for the detailed and thought out comment.

On the URL deceiving piece, I just think that the component could do more to alert the user. As a power user for example, I would be happy to hover over the like button for a second and get told what URL it is going to hit etc :)

But, I totally understand that the case that matters isn&#039;t the power user case. We can still do more to help those users too.

Cheers,

Dion</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Thanks for the detailed and thought out comment.</p>
<p>On the URL deceiving piece, I just think that the component could do more to alert the user. As a power user for example, I would be happy to hover over the like button for a second and get told what URL it is going to hit etc :)</p>
<p>But, I totally understand that the case that matters isn&#8217;t the power user case. We can still do more to help those users too.</p>
<p>Cheers,</p>
<p>Dion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://almaer.com/blog/mike-hanson-douglas-crockford-and-facebook-a-tale-of-security-privacy-and-performance/comment-page-1#comment-46487</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Sat, 24 Apr 2010 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2666#comment-46487</guid>
		<description>Interesting times, no?

A couple of responses:

I actually think it&#039;s a feature, rather than a bug, that you can put a Like button on your page that points to ANY link. This is no different than so many ShareThis, Post to Buzz, Digg This, and other buttons out in the wild. Furthermore, if, say, I&#039;m running some campaign on a microsite for my beverage VocaVola, I&#039;m going to want you to like the primary URL for my product, NOT the microsite.

Yes, you can totally deceive users into doing the wrong thing, but in this case I think the benefits to well-intentioned people is FAR greater than the few abusers that might try to game the system (if Facebook gets wind of your evil tactics, they could just block you from hosting the iframe anyway).

I&#039;m also supportive of adding more social verbs to the browser (big surprise, right?). In fact, the Follow verb in my social agent mockups could serve a similar purpose:

http://factoryjoe.com/blog/2010/03/16/the-social-agent-part-3-follow/

The problem is reaching critical mass — and beyond that — starting with identity in the browser. Facebook&#039;s Like button only works because most people already have Facebook accounts and are signed in most of the time. For similar functionality to work in the browser (and for the incentive to exist for publishers) you&#039;d need to be able to Like or Follow things that then get sent to a public profile or activity stream (otherwise you&#039;re just bookmarking things locally, and no advertiser or marketer will care about that).

So until we get identity in the browser, this stuff will continue happening on the server-to-server side.

Finally, as for performance — I think you need to look at the sheer ease of integration for publishers. You include at minimum an iframe and you&#039;re done. Nothing else to worry about. Couldn&#039;t be simpler, and where you want the Like button, it goes — no need to need with with your HTML head at all.

When it comes to adding these &quot;social plugins&quot; we really need to think about a novice audience and how much expertise they have. Facebook is powerful because of how simple they make integrating with them — dispensing with complexity and power user features to address the mass market.

That approach is single-handedly the most dangerous threat to the open web in my mind — since to date, much of the open web&#039;s adherents love the nitty gritty details and power that comes from mastering complexity. Unless we can make our technologies more accessible, Facebook will continue to dominate an ever-increasing audience.</description>
		<content:encoded><![CDATA[<p>Interesting times, no?</p>
<p>A couple of responses:</p>
<p>I actually think it&#8217;s a feature, rather than a bug, that you can put a Like button on your page that points to ANY link. This is no different than so many ShareThis, Post to Buzz, Digg This, and other buttons out in the wild. Furthermore, if, say, I&#8217;m running some campaign on a microsite for my beverage VocaVola, I&#8217;m going to want you to like the primary URL for my product, NOT the microsite.</p>
<p>Yes, you can totally deceive users into doing the wrong thing, but in this case I think the benefits to well-intentioned people is FAR greater than the few abusers that might try to game the system (if Facebook gets wind of your evil tactics, they could just block you from hosting the iframe anyway).</p>
<p>I&#8217;m also supportive of adding more social verbs to the browser (big surprise, right?). In fact, the Follow verb in my social agent mockups could serve a similar purpose:</p>
<p><a href="http://factoryjoe.com/blog/2010/03/16/the-social-agent-part-3-follow/" rel="nofollow">http://factoryjoe.com/blog/2010/03/16/the-social-agent-part-3-follow/</a></p>
<p>The problem is reaching critical mass — and beyond that — starting with identity in the browser. Facebook&#8217;s Like button only works because most people already have Facebook accounts and are signed in most of the time. For similar functionality to work in the browser (and for the incentive to exist for publishers) you&#8217;d need to be able to Like or Follow things that then get sent to a public profile or activity stream (otherwise you&#8217;re just bookmarking things locally, and no advertiser or marketer will care about that).</p>
<p>So until we get identity in the browser, this stuff will continue happening on the server-to-server side.</p>
<p>Finally, as for performance — I think you need to look at the sheer ease of integration for publishers. You include at minimum an iframe and you&#8217;re done. Nothing else to worry about. Couldn&#8217;t be simpler, and where you want the Like button, it goes — no need to need with with your HTML head at all.</p>
<p>When it comes to adding these &#8220;social plugins&#8221; we really need to think about a novice audience and how much expertise they have. Facebook is powerful because of how simple they make integrating with them — dispensing with complexity and power user features to address the mass market.</p>
<p>That approach is single-handedly the most dangerous threat to the open web in my mind — since to date, much of the open web&#8217;s adherents love the nitty gritty details and power that comes from mastering complexity. Unless we can make our technologies more accessible, Facebook will continue to dominate an ever-increasing audience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
