<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Stay N' Alive</title>
	
	<link>http://staynalive.com</link>
	<description>My View of the Real-Time Web - Tech and Rants From Jesse Stay, The "Social" Geek</description>
	<lastBuildDate>Thu, 11 Mar 2010 18:08:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<cloud domain="staynalive.com" port="80" path="/?rsscloud=notify" registerProcedure="" protocol="http-post" />
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/StayNAlive" /><feedburner:info uri="staynalive" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Tech News</media:category><itunes:explicit>no</itunes:explicit><itunes:subtitle>My View of the Real-Time Web - Tech and Rants From Jesse Stay, The "Social" Geek</itunes:subtitle><itunes:category text="Technology"><itunes:category text="Tech News" /></itunes:category><geo:lat>40.650496</geo:lat><geo:long>-111.995912</geo:long><creativeCommons:license>http://creativecommons.org/licenses/by-sa/3.0/</creativeCommons:license><image><link>http://creativecommons.org/licenses/by-sa/3.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image><feedburner:emailServiceId>StayNAlive</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Brazen Careerist Launches Site for Job Seekers That Gen-Y-ers Can Actually Enjoy</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/SpnAtXlpKOM/</link>
		<comments>http://staynalive.com/articles/2010/03/11/brazen-careerist-gen-y/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 10:35:28 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[startups]]></category>
		<category><![CDATA[brazen careerist]]></category>
		<category><![CDATA[gen-y]]></category>
		<category><![CDATA[generation y]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[social network]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=6166</guid>
		<description>Generation Y, those that grew up with the web and many of which probably know of no life without it, is prime target for those looking for fresh blood in the Job Marketplace.  It is this generation that is just entering the marketplace, and which Employer after Employer is fighting to gain access to.  These [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.40.00-AM.png" ><img class="alignright size-full wp-image-6168" title="Screen shot 2010-03-11 at 3.40.00 AM" src="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.40.00-AM.png" alt="" width="169" height="67" /></a>Generation Y, those that grew up with the web and many of which probably know of no life without it, is prime target for those looking for fresh blood in the Job Marketplace.  It is this generation that is just entering the marketplace, and which Employer after Employer is fighting to gain access to.  These are the founders of Facebook, the latest entries to the Google workforce, and the future of Microsoft.  These are those that will shape the ideas of our future.  Just recently, <a href="http://brazencareerist.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/brazencareerist.com');">Brazen Careerist</a>, a site targeted towards Job Seekers, became one of the first to jump at this market by building an entire Social Network targeted towards the Generation Y Job Seeker.</p>
<p>Brazen Careerist hits all the points that Gen Yers love.  Being a much more open audience than their older peers, the site focuses on this fact, bringing attention to a Facebook or Twitter-like stream.  The first question it asks you is, &#8220;What are you thinking?&#8221;, a question the Gen-Y audience is likely to be more than willing to share with employers.  The entire site integrates well with Facebook Connect, Twitter, LinkedIn, and other networks, enabling users to share across multiple networks, import from their favorite sites, and discuss the ideas their friends are sharing.</p>
<p>In my early 20s, working for startups such as <a href="http://freeservers.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/freeservers.com');">Freeservers.com</a>, and <a href="http://onegreatfamily.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/onegreatfamily.com');">OneGreatFamily.com</a>, I was known as the idea man.  At the time I didn&#8217;t have that much experience, but, being the entrepreneur that I am, I always had an idea that I was sharing.  I think you can still see this today on this blog, Twitter, and Facebook.</p>
<p>Brazen Careerist helps to highlight the less-experienced workers&#8217; way of thinking by enabling thoughts, and ideas to be shared and discussed.  For an idea person such as myself, this service is a God-send in empowering the truly innovative minds of our society.  At the same time it is a great tool for employers to discover those bright minds, as, one of the first questions most employers ask in the interview process is &#8220;Tell me about yourself&#8221;.</p>
<p>Let&#8217;s face it.  <a href="http://linkedin.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/linkedin.com');">LinkedIn</a> is for old people.  It has hardly innovated over the years.  While still a great network for the Gen-Xers and more experienced workforce to network, it is just too hard for a new employee entering into the workforce to get the most out of such a site, especially in a group of people so willing to share information about themselves.  The new Brazen Careerist takes the LinkedIn Resume, but adds to it the ability for each potential employee to truly express themselves in a way history just hasn&#8217;t manifested yet.  In a much more open workforce it seems suitable a new entrant into the networking marketplace came forward.</p>
<p>If you&#8217;re one of these Gen-Yers looking to gain an edge with your peers and potential employers, Brazen Careerist is the perfect tool to accomplish that.  I encourage you to check it out and let me know what you think in the comments.  You can also &#8220;fan&#8221; me there at <a href="http://www.brazencareerist.com/profile/jesse-stay" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.brazencareerist.com');">http://www.brazencareerist.com/profile/jesse-stay</a>.</p>
<p style="text-align: center;"><a href="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.38.47-AM.png" ><img class="aligncenter size-full wp-image-6167" title="Screen shot 2010-03-11 at 3.38.47 AM" src="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.38.47-AM.png" alt="" width="659" height="542" /></a></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F11%2Fbrazen-careerist-gen-y%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F11%2Fbrazen-careerist-gen-y%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/V0RH8OWYIPsASvuXFCKg4pNwvlo/0/da"><img src="http://feedads.g.doubleclick.net/~a/V0RH8OWYIPsASvuXFCKg4pNwvlo/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/V0RH8OWYIPsASvuXFCKg4pNwvlo/1/da"><img src="http://feedads.g.doubleclick.net/~a/V0RH8OWYIPsASvuXFCKg4pNwvlo/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=SpnAtXlpKOM:MVjffcA3F9Q:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=SpnAtXlpKOM:MVjffcA3F9Q:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=SpnAtXlpKOM:MVjffcA3F9Q:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=SpnAtXlpKOM:MVjffcA3F9Q:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=SpnAtXlpKOM:MVjffcA3F9Q:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=SpnAtXlpKOM:MVjffcA3F9Q:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=SpnAtXlpKOM:MVjffcA3F9Q:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=SpnAtXlpKOM:MVjffcA3F9Q:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/SpnAtXlpKOM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/03/11/brazen-careerist-gen-y/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.40.00-AM.png" />
		<media:content url="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.40.00-AM.png" medium="image">
			<media:title type="html">Screen shot 2010-03-11 at 3.40.00 AM</media:title>
		</media:content>
		<media:content url="http://staynalive.com/files/2010/03/Screen-shot-2010-03-11-at-3.38.47-AM.png" medium="image">
			<media:title type="html">Screen shot 2010-03-11 at 3.38.47 AM</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F11%2Fbrazen-careerist-gen-y%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/03/11/brazen-careerist-gen-y/</feedburner:origLink></item>
		<item>
		<title>Please Do Twitter a Favor and Join SocialToo</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/5qPSPDRAMJI/</link>
		<comments>http://staynalive.com/articles/2010/03/08/please-do-twitter-a-favor-and-join-socialtoo/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 23:19:47 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[SocialToo.com]]></category>
		<category><![CDATA[Twitter]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[dms]]></category>
		<category><![CDATA[malicious]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=6116</guid>
		<description>Today we announced on the SocialToo blog that we&amp;#8217;ve enabled our phishing protection for all 60,000+ SocialToo users (and many, many more to come).  This project means a lot to me, as it means the more people that use it, the fewer phishing DMs will be received, links won&amp;#8217;t be clicked, passwords won&amp;#8217;t be [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/03/v7_n_phishing02.jpg" ><img class="alignright size-full wp-image-6117" title="gone phishing" src="http://staynalive.com/files/2010/03/v7_n_phishing02.jpg" alt="" width="185" height="110" /></a>Today <a href="http://blog.socialtoo.com/2010/03/08/enabling-phishing-protection-for-all-socialtoo-users/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.socialtoo.com');">we announced</a> on the <a href="http://socialtoo.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/socialtoo.com');">SocialToo</a> blog that we&#8217;ve enabled our phishing protection for all 60,000+ SocialToo users (and many, many more to come).  This project means a lot to me, as it means the more people that use it, the fewer phishing DMs will be received, links won&#8217;t be clicked, passwords won&#8217;t be shared, and accounts won&#8217;t be compromised.  The more I can help prevent this from happening, I think the better for the web in general.</p>
<p>In total, SocialToo has blocked near 200,000 total spam DMs sent to our users, and over 25,000 of those were malicious, phishing, and trapped automatically by our filters.  5,000 of those were just since enabling it on all accounts.  That&#8217;s 25,000 dms that could have been collecting your Twitter credentials, could have compromised your account, and could have spread further by compromising your account.  This service is powerful.</p>
<p>The service gets enabled automatically for any user that just logs in with their Twitter credentials at http://socialtoo.com.  Of course, I&#8217;d love it if you tried our other features, set up some filters, maybe tracked who followed you and stopped following you the previous day on Twitter, but more than anything I want you to help the web in general by eradicating these pesky dms!  Each dm we detect gets deleted from your Twitter account, often before you can see it in your favorite Twitter client, doesn&#8217;t get sent in our DM e-mails (found on your <a href="http://socialtoo.com/filters" onclick="javascript:urchinTracker ('/outbound/article/socialtoo.com');">Filters</a> page), and a message is sent on your behalf to <a href="http://twitter.com/spam" onclick="javascript:urchinTracker ('/outbound/article/twitter.com');">@spam</a> also notifying Twitter of the compromised account.</p>
<p>Please, if you haven&#8217;t had reason to join SocialToo yet, now is the time.  This is your opportunity to, just by logging in, help make Twitter a cleaner place.  Be sure to <a href="http://blog.louisgray.com/2010/03/socialtoo-expands-twitter-phishing.html" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.louisgray.com');">check out Louis Gray&#8217;s experience</a> with this service on his blog &#8211; I think he too has had similar experience in seeing the success of having this enabled.</p>
<p>Oh, and stay tuned, other than this and our <a href="http://blog.socialtoo.com/2010/03/05/a-new-way-to-manage-your-twitter-dms-the-new-socialtoo-design/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.socialtoo.com');">new design launch</a>, we&#8217;ve got some more really big news coming tomorrow that I think you&#8217;re going to really like.</p>
<p><em>Image courtesy </em><a href="http://www.v3.co.uk/vnunet/specials/2127679/gone-phishing" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.v3.co.uk');"><em>http://www.v3.co.uk/vnunet/specials/2127679/gone-phishing</em></a></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F08%2Fplease-do-twitter-a-favor-and-join-socialtoo%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F08%2Fplease-do-twitter-a-favor-and-join-socialtoo%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/81d5aI1ZhZbSTSzR7tmBU8WeyVU/0/da"><img src="http://feedads.g.doubleclick.net/~a/81d5aI1ZhZbSTSzR7tmBU8WeyVU/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/81d5aI1ZhZbSTSzR7tmBU8WeyVU/1/da"><img src="http://feedads.g.doubleclick.net/~a/81d5aI1ZhZbSTSzR7tmBU8WeyVU/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=5qPSPDRAMJI:0DqjdwAzOVg:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=5qPSPDRAMJI:0DqjdwAzOVg:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=5qPSPDRAMJI:0DqjdwAzOVg:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=5qPSPDRAMJI:0DqjdwAzOVg:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=5qPSPDRAMJI:0DqjdwAzOVg:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=5qPSPDRAMJI:0DqjdwAzOVg:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=5qPSPDRAMJI:0DqjdwAzOVg:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=5qPSPDRAMJI:0DqjdwAzOVg:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/5qPSPDRAMJI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/03/08/please-do-twitter-a-favor-and-join-socialtoo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/03/v7_n_phishing02.jpg" />
		<media:content url="http://staynalive.com/files/2010/03/v7_n_phishing02.jpg" medium="image">
			<media:title type="html">gone phishing</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F08%2Fplease-do-twitter-a-favor-and-join-socialtoo%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/03/08/please-do-twitter-a-favor-and-join-socialtoo/</feedburner:origLink></item>
		<item>
		<title>Did Google Reinvent the Wheel by Adopting the Protocols They Chose?</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/8JyeIbXhTyo/</link>
		<comments>http://staynalive.com/articles/2010/03/06/did-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 00:43:05 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[open standards]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[facebook api]]></category>
		<category><![CDATA[open]]></category>
		<category><![CDATA[openplatform]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=6078</guid>
		<description>In a response to my article here, DeWitt Clinton of Google defined what he deemed the definition of &amp;#8220;open&amp;#8221; to be.  According to DeWitt, &amp;#8220;the first is licensing of the protocols themselves, with respect to who can legally implement them and/or who can legally fork them.&amp;#8221;  I argue if this were the case, then why [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/03/wheel.jpeg" ><img class="alignright size-full wp-image-6079" title="wheel" src="http://staynalive.com/files/2010/03/wheel.jpeg" alt="" width="270" height="309" /></a>In <a href="http://www.google.com/buzz/dclinton/KuXDg9P8Q8z/Jesse-Stay-A-few-points-of-clarification-to-your" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.google.com');">a response</a> to <a href="http://staynalive.com/articles/2010/03/03/the-web-is-no-longer-open/" target="_blank" >my article here</a>, DeWitt Clinton of Google <a href="http://www.google.com/buzz/dclinton/KuXDg9P8Q8z/Jesse-Stay-A-few-points-of-clarification-to-your" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.google.com');">defined what he deemed the definition of &#8220;open&#8221; to be</a>.  According to DeWitt, &#8220;the first is licensing of the protocols themselves, with respect to who can legally implement them and/or who can legally fork them.&#8221;  I argue if this were the case, then why didn&#8217;t Google clone and standardize what Facebook is doing, where m<a href="http://www.facebook.com/press/info.php?statistics" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.facebook.com');">any, many more developers are already integrating and writing code for</a>?  Facebook itself is part of the Open Web Foundation, and applies the same principles as Google to allowing others to clone the APIs they provide to developers.</p>
<p>DeWitt&#8217;s second definition of &#8220;open&#8221; revolves around, according to DeWitt, &#8220;the license by which the data itself is made available. (The Terms and Conditions, so to speak.) The formal definitions are less well established here (thus far!), but it ultimately has to do with who owns the data and what proprietary rights over it are asserted.&#8221;  Even Facebook makes clear in its terms that you own your data, and they&#8217;re even working to build protocols to enable website owners to host and access this data on their own sites.  Why did Google have to write their own Social Graph API or access lesser-used protocols (such as FOAF or OpenID) when they could, in reality, be standardizing what <a href="http://www.facebook.com/press/info.php?statistics" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.facebook.com');">millions</a> (or more?) of other developers are already utilizing with Facebook Connect and the Facebook APIs to access friend data?  Google could easily duplicate the APIs Facebook has authored (<a href="http://developers.facebook.com/fbopen/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/developers.facebook.com');">even using the open source libraries Facebook provides for it</a>), and have a full-fledged, &#8220;open&#8221; social network built from these APIs many developers are already building upon.  I would argue there are/were many more developers writing for Facebook than were developing under the open protocols and standards Google chose to adapt.  I&#8217;d like to see some stats if that is not the case.  Granted, even Facebook is giving way to Google to adopt some of these other &#8220;open&#8221; standards so developers have choice in this matter, even if they were one of the few adopting the other standards.</p>
<p>I still think Google is adopting these standards because it benefits Google, not the user or developer.  If Google wanted to benefit the majority of the audience of developers they would have cloned the already &#8220;open&#8221; Facebook APIs rather than adopt the much lesser-adopted other protocols they have chosen to go by.  This is a matter of competition, being the &#8220;hero&#8221;, and a brilliant marketing strategy.  Is Google evil for doing this?  Of course not.  Do I hate Google for this?  Only for the reason that I have to now adapt all the apps I write in Facebook to new &#8220;open&#8221; APIs Google is choosing to adopt.</p>
<p>IMO, if Google wanted to truly benefit the developer they would have chosen to clone the existing &#8220;open&#8221; APIs developers were already writing for.  This is a marketing play, plain and simple.  It may have started with geeks not wanting to get into the Facebook worlds, but management agreed because in the end, it benefits Google, not their competitors.  If you don&#8217;t think so, you should ask Dave Winer <a href="http://www.scripting.com/stories/2010/03/04/googleAndRss.html" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.scripting.com');">why Google is not implementing RSS or rssCloud instead of Atom and PSHB</a> (I&#8217;m completely baffled by that one, too).</p>
<p><em>Image courtesy </em><a href="http://northerndoctor.com/2009/04/17/re-inventing-the-wheel/" onclick="javascript:urchinTracker ('/outbound/article/northerndoctor.com');"><em>http://northerndoctor.com/2009/04/17/re-inventing-the-wheel/</em></a></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F06%2Fdid-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F06%2Fdid-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/AXSOJ5p8xAN486zR8F1Pm-PviyQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/AXSOJ5p8xAN486zR8F1Pm-PviyQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/AXSOJ5p8xAN486zR8F1Pm-PviyQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/AXSOJ5p8xAN486zR8F1Pm-PviyQ/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=8JyeIbXhTyo:EHIAPAWRaws:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=8JyeIbXhTyo:EHIAPAWRaws:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=8JyeIbXhTyo:EHIAPAWRaws:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=8JyeIbXhTyo:EHIAPAWRaws:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=8JyeIbXhTyo:EHIAPAWRaws:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=8JyeIbXhTyo:EHIAPAWRaws:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=8JyeIbXhTyo:EHIAPAWRaws:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=8JyeIbXhTyo:EHIAPAWRaws:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/8JyeIbXhTyo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/03/06/did-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose/feed/</wfw:commentRss>
		<slash:comments>24</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/03/wheel.jpeg" />
		<media:content url="http://staynalive.com/files/2010/03/wheel.jpeg" medium="image">
			<media:title type="html">wheel</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F06%2Fdid-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/03/06/did-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose/</feedburner:origLink></item>
		<item>
		<title>The Web is No Longer Open</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/D6IuiMeTBvU/</link>
		<comments>http://staynalive.com/articles/2010/03/03/the-web-is-no-longer-open/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 05:48:35 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[open standards]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[kynetx]]></category>
		<category><![CDATA[open]]></category>
		<category><![CDATA[open web]]></category>
		<category><![CDATA[opengraph]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5999</guid>
		<description>&amp;#8220;So it can benefit everyone.&amp;#8221;
That&amp;#8217;s what a Google employee said today as he tried to explain Google&amp;#8217;s recent push to have websites use the &amp;#8216;rel=&amp;#8221;me&amp;#8221;&amp;#8216; meta HTML tags to identify pages a user owns on the web.  It&amp;#8217;s not a bad strategy &amp;#8211; index the entire web, know every single website out there, and when [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/03/8004372_f433474266.jpeg" ><img class="alignright size-full wp-image-6000" title="open web" src="http://staynalive.com/files/2010/03/8004372_f433474266.jpeg" alt="" width="300" height="300" /></a><a href="http://www.google.com/buzz/dclinton/dNzWYc2oGcw/You-might-think-were-a-little-nuts-for-all-this" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.google.com');">&#8220;So it can benefit everyone.&#8221;</a></p>
<p>That&#8217;s what a Google employee said today as he tried to explain Google&#8217;s recent push to have websites use the &#8216;rel=&#8221;me&#8221;&#8216; meta HTML tags to identify pages a user owns on the web.  It&#8217;s not a bad strategy &#8211; index the entire web, know every single website out there, and when they change, and now the web is your network.  The thing is, since the &#8220;open&#8221; web hasn&#8217;t had a natural way of identifying websites owned by users, Google, the current controller of this network, needed a way to do it.  Why not make people identify their websites to Google&#8217;s SocialGraph network, and call it &#8220;open&#8221; so it benefits everyone?  I&#8217;m sorry, but the &#8220;open&#8221; web that we all grew up in is dead now that 2 or 3 entities have indexed it all.  This is now <em>their</em> network.</p>
<p>Let&#8217;s contrast that to Facebook, the &#8220;Walled Garden&#8221;, criticized for being closed due to tight privacy controls and not willing to open up to the outside web.  Of course, all that is a myth &#8211; Facebook too has provided ways for website owners to identify themselves to Facebook on the &#8220;open&#8221; web, making Facebook itself the controller of that social graph data, thereby giving Facebook a new role in who &#8220;owns&#8221; the &#8220;open&#8221; web.  Facebook has even made known in its developer roadmap its intention to build an &#8220;OpenGraph API&#8221;, making every website owner&#8217;s site a Facebook Fan Page in the Facebook network.  Don&#8217;t kid yourself that Facebook wants a role in this as well.  They&#8217;re a major threat to Google, too because of this.</p>
<p>Then there&#8217;s Twitter, just starting to realize how to play in this game, now starting to collect user data for search in their own network.  Don&#8217;t count them out just yet, as they too will soon be trying to find ways to get you to identify your website on <em>their</em> network.</p>
<p>So we&#8217;ll soon have 3 ways of identifying our websites on the &#8220;open&#8221; web.  I can identify my site through Facebook, as you see by the Facebook Connect login buttons scattered around.  I can identify myself in the Google SocialGraph APIs, which, if you view the source of this site you&#8217;ll see a &#8216;rel=&#8221;me&#8221;&#8216; meta tag identifying my site so Google can search it.  Who knows what Twitter will provide to bring my site into its network.  Each network is providing its easiest ways of identifying your site within their own Social Graph, and calling it &#8220;open&#8221; so other developers can bring their stuff into their networks easily, without rewriting code.</p>
<p>I think it&#8217;s time we stop tricking ourselves into thinking the web is open at all.  Google is in control of the web &#8211; they have it all indexed.  Now that we are seeing that he who owns the Social Graph has a new way of controlling and indexing the web, which we are seeing by Facebook&#8217;s massive growth (400+ million users!), I think Google feels threatened.  They&#8217;ll play every &#8220;open&#8221; term in the book to gain that control back.  Of course the new meta tags are beneficial &#8211; is it really beneficial to &#8220;everybody&#8221; though?  I argue the one entity it benefits most is Google.  Yeah, it benefits developers if we can get everyone to agree on what &#8220;open&#8221; is, but that will never happen.  I think it&#8217;s time we accept that now that the web is controlled and indexed by only a few large corporations, it is far from &#8220;open&#8221;.  &#8221;Open&#8221; is nothing more than a marketing term, and I think we can thank Google for that.  No, that&#8217;s not a bad thing &#8211; it&#8217;s just reality.</p>
<p>Do these technologies really &#8220;benefit everyone&#8221; when <a href="http://www.wired.com/epicenter/2009/04/wikipedia-found/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.wired.com');">no other search startup has a remote chance of competing with owning the &#8220;open web&#8221; network</a>?</p>
<p><em>Further note:</em></p>
<p><em>How do we solve this?  I truly believe the only solution to giving the user control of the web again is via client-side, truly user-controlled technologies like what <a href="http://kynetx.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/kynetx.com');">Kynetx</a> offers.  Action Cards, Information Cards, Selectors, and browser-side technologies that bring context back in the user&#8217;s hands are the only way we&#8217;re going to make the web &#8220;open&#8221; again.  The future will be the battle for the client &#8211; I hope the user wins that battle.</em></p>
<p><em><a href="http://www.flickr.com/photos/lwr/8004372/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.flickr.com');">Image courtesy Leo Reynolds</a></em></p>
<p>UPDATE: DeWitt Clinton of Google, who wrote the quote above this post is in response to, issued his own response <a href="http://goo.gl/fb/RjnO" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/goo.gl');">here</a>.  The comments there are interesting, albeit a lot of current and former Google employees trying to defend their case.  I still hold that no matter what Google does now, due to the size of their index, any promotion of the &#8220;open web&#8221; is still to their benefit.  I don&#8217;t think Google should be denying that.</p>
<p>UPDATE 2: My response to DeWitt&#8217;s response is <a href="http://staynalive.com/articles/2010/03/06/did-google-reinvent-the-wheel-by-adopting-the-protocols-they-chose/" target="_blank" >here</a> &#8211; why didn&#8217;t Google just clone Facebook&#8217;s APIs if their intention was to benefit the developer and end-user?</p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F03%2Fthe-web-is-no-longer-open%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F03%2Fthe-web-is-no-longer-open%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/roILBrlWNUYdURD92a_4UIS59HE/0/da"><img src="http://feedads.g.doubleclick.net/~a/roILBrlWNUYdURD92a_4UIS59HE/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/roILBrlWNUYdURD92a_4UIS59HE/1/da"><img src="http://feedads.g.doubleclick.net/~a/roILBrlWNUYdURD92a_4UIS59HE/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=D6IuiMeTBvU:23OoMKkRLWY:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=D6IuiMeTBvU:23OoMKkRLWY:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=D6IuiMeTBvU:23OoMKkRLWY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=D6IuiMeTBvU:23OoMKkRLWY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=D6IuiMeTBvU:23OoMKkRLWY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=D6IuiMeTBvU:23OoMKkRLWY:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=D6IuiMeTBvU:23OoMKkRLWY:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=D6IuiMeTBvU:23OoMKkRLWY:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/D6IuiMeTBvU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/03/03/the-web-is-no-longer-open/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/03/8004372_f433474266.jpeg" />
		<media:content url="http://staynalive.com/files/2010/03/8004372_f433474266.jpeg" medium="image">
			<media:title type="html">open web</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F03%2F03%2Fthe-web-is-no-longer-open%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/03/03/the-web-is-no-longer-open/</feedburner:origLink></item>
		<item>
		<title>Is Google Stealing Authors’ Copyright With Buzz?</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/xLwYtp2UK0A/</link>
		<comments>http://staynalive.com/articles/2010/02/25/is-google-stealing-authors-copyright-with-buzz/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 23:14:30 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[ads]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[google reader]]></category>
		<category><![CDATA[rss]]></category>
		<category><![CDATA[scraping]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5864</guid>
		<description>2 years ago I shared about a blogger and follower/friend of mine, Ali Akbar, who purchased the domain, googleappsengine.com (he still owns it) in order to create an AppEngine-related blog (since Google apparently forgot to purchase the domain).  Ali received a threatening Cease-and-Desist from Google shortly after asking him to immediately discontinue use of the [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/02/Alt-tag-text-goes-here.jpeg" ><img class="alignright size-full wp-image-5866" title="The Ant Bully - courtesy Warner Bros. Entertainment - http://entertainment.howstuffworks.com/framed.htm?parent=movie-guide-2006.htm&amp;url=http://www2.warnerbros.com/antbully/" src="http://staynalive.com/files/2010/02/Alt-tag-text-goes-here.jpeg" alt="" width="240" height="287" /></a>2 years ago <a href="http://staynalive.com/articles/2008/05/16/google-bullies-blogger-to-surrender-googleappsenginecom/" target="_blank" >I shared about a blogger</a> and follower/friend of mine, Ali Akbar, who purchased the domain, <a href="http://appsengine.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/appsengine.com');">googleappsengine.com</a> (he still owns it) in order to create an AppEngine-related blog (since Google apparently forgot to purchase the domain).  Ali received a threatening Cease-and-Desist from Google shortly after asking him to immediately discontinue use of the domain and &#8220;Take immediate steps to transfer the Domain Name to Google&#8221;.  It would appear that Google needs to take a dose of its own medicine though.  To my surprise, I&#8217;ve realized recently that my articles from StayNAlive.com and other blogs are being shared, in their full text, on <a href="http://buzz.google.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/buzz.google.com');">Buzz</a> and having my ads stripped from them, without my permission.</p>
<p>For those unaware, there&#8217;s a &#8220;<a href="http://staynalive.com/feed" target="_blank" >subscribe</a>&#8221; button when you visit this blog that allows anyone to obtain the RSS of this blog and plug it into a Reader.  For those of you reading this in a Reader, thank you, and you&#8217;re already aware of this.  One thing I have done with those feeds if you haven&#8217;t noticed is at the bottom of each post in the RSS, I&#8217;ve added <a href="http://adsense.google.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/adsense.google.com');">Google Adsense</a> to my feeds so I can at least cover my costs of running this blog and make at least a few cents a day trying to re-coup costs of hosting and time spent writing posts.  If you visit <a href="http://staynalive.com/feed" target="_blank" >http://staynalive.com/feed</a> in a browser like Chrome, you can look at the raw feed and see the ads at the bottom of each post.  Or, if you&#8217;re reading this post in a traditional feed reader, look down at the bottom of this post and you&#8217;ll see the ad.</p>
<p>However, there&#8217;s a feature on Buzz that enables anyone reading my shared posts to expand the summarized content and view the entire post, right in Buzz.  For one, I didn&#8217;t give Buzz permission to do this on shared posts, and second, Buzz is stripping out my ads, depriving me of that potential revenue rather than either displaying those ads, or redirecting the user back to my site where I can monetize that in some other form.  This is blatant copyright infringement if you ask me!  Now, if you expand my posts, since it&#8217;s integrated into Gmail, look over to the right &#8211; see those ads?  Yup, I&#8217;m not getting a penny of that.</p>
<p>Google is now monetizing my content, and neglecting to ask for my permission in doing so, while removing what I had put in place to monetize my content.  Starting today, I&#8217;m removing my blog from my <a href="http://profile.google.com/jessestay" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/profile.google.com');">Google Profile</a>, as well as my Google Reader shares so that I don&#8217;t help further the copyright infringement on other blogs I share.  The problem that still exists is that anyone who shares my content from Google Reader will also have my content available on Buzz in full format, and my ads stripped.  There&#8217;s no way to stop it, and Google is encouraging this wrong practice.</p>
<p>To be clear, I&#8217;m fine with them either displaying the ads that I put there (and allowing me to monetize off the other ads that are on the page), or just summarizing the article and encouraging users to click through to my site.  I&#8217;m <em>not</em> okay with Google scraping my content, stripping my ads, altering my content, and pushing it out for them to get 100% of the revenues off of something I spent time and money making.</p>
<p>Google, how is this not evil?  Maybe I should use <a href="http://staynalive.com/articles/2008/05/16/google-bullies-blogger-to-surrender-googleappsenginecom/" target="_blank" >Google&#8217;s own Cease and Desist letter</a> to get them to stop this practice.  Or would that itself be copyright infringement?</p>
<p><em>Image courtesy </em><a href="http://entertainment.howstuffworks.com/framed.htm?parent=movie-guide-2006.htm&amp;url=http://www2.warnerbros.com/antbully/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/entertainment.howstuffworks.com');"><em>Warner Bros. Entertainment</em></a><em> &#8211; &#8220;The Ant Bully&#8221;</em></p>
<p><em><span style="font-style: normal;">UPDATE: The Google Buzz Team did contact me on Buzz (Ironically, considering the content of this post), and they say they&#8217;re going to have the ad scraping issue fixed by next week.</span></em></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F25%2Fis-google-stealing-authors-copyright-with-buzz%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F25%2Fis-google-stealing-authors-copyright-with-buzz%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/5flM3JOVZFeI8jf7NcGjjC6LNPE/0/da"><img src="http://feedads.g.doubleclick.net/~a/5flM3JOVZFeI8jf7NcGjjC6LNPE/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/5flM3JOVZFeI8jf7NcGjjC6LNPE/1/da"><img src="http://feedads.g.doubleclick.net/~a/5flM3JOVZFeI8jf7NcGjjC6LNPE/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xLwYtp2UK0A:q1OMKCztD40:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xLwYtp2UK0A:q1OMKCztD40:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xLwYtp2UK0A:q1OMKCztD40:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xLwYtp2UK0A:q1OMKCztD40:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xLwYtp2UK0A:q1OMKCztD40:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xLwYtp2UK0A:q1OMKCztD40:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xLwYtp2UK0A:q1OMKCztD40:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xLwYtp2UK0A:q1OMKCztD40:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/xLwYtp2UK0A" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/25/is-google-stealing-authors-copyright-with-buzz/feed/</wfw:commentRss>
		<slash:comments>36</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/02/Alt-tag-text-goes-here.jpeg" />
		<media:content url="http://staynalive.com/files/2010/02/Alt-tag-text-goes-here.jpeg" medium="image">
			<media:title type="html">The Ant Bully – courtesy Warner Bros. Entertainment – http://entertainment.howstuffworks.com/framed.htm?parent=movie-guide-2006.htm&amp;url=http://www2.warnerbros.com/antbully/</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F25%2Fis-google-stealing-authors-copyright-with-buzz%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/02/25/is-google-stealing-authors-copyright-with-buzz/</feedburner:origLink></item>
		<item>
		<title>Facebook to Developers: “You Decide”</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/PAqHAr4-pHA/</link>
		<comments>http://staynalive.com/articles/2010/02/24/facebook-to-developers-you-decide/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 22:05:34 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Geeky]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[choice]]></category>
		<category><![CDATA[facebook api]]></category>
		<category><![CDATA[facebook platform]]></category>
		<category><![CDATA[sandbox]]></category>
		<category><![CDATA[staging]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5843</guid>
		<description>By the time I hit publish on this 5 other bigger blogs will have probably already covered this, but this deserves some praise.  One reason I love the Facebook Platform is because they really seem to care about API developers.  They do things the &amp;#8220;right&amp;#8221; way.  For instance, they have a beta site where they [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2009/11/wiki_logo.png" ><img class="alignright size-full wp-image-3681" title="facebook platform" src="http://staynalive.com/files/2009/11/wiki_logo.png" alt="" width="124" height="155" /></a>By the time I hit publish on this 5 other bigger blogs will have probably already covered this, but this deserves some praise.  One reason I love the Facebook Platform is because they really seem to care about API developers.  They do things the &#8220;right&#8221; way.  For instance, they have a beta site where they always release new bug fixes and features before they go live on the site.  They always release new API features in &#8220;sandbox mode&#8221; before going live with them.  No other platform releases new features and updates in this manner!  Just today <a href="http://developers.facebook.com/news.php?blog=1&amp;story=363" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/developers.facebook.com');">they upped their game even more</a>, giving developers full control over this process by letting developers decide when new API features go live.</p>
<p>The service gives developers a new &#8220;Migrations&#8221; option in their application settings, enabling them to choose when things go live.  The first one of these they launched has to do with a bug they&#8217;ve fixed which formats empty JSON strings correctly.  To enable the feature you just go to your &#8220;Migrations&#8221; section for your app, and select &#8220;on&#8221;, and now all empty JSON strings will be formatted in the correct manner.  The power of all of this is that <em>you</em> get to decide when these features go live, but you can start trying them immediately!</p>
<p>Of course, all features will eventually go live, but what this shows is that Facebook is willing to keep developers aware of changes before they go live.  Facebook won&#8217;t be launching features into the wild out of the blue like many of their competitors do quite regularly.  Previously, changes would go live, and while they would often show on the beta site, developers had little notice and little time to test them before putting them into production.  These changes would break many apps the minute they went into production.</p>
<p>IMO, this small feature changes the game for many other app platforms.  NO OTHER major app platform does anything like this.  Kudos to the Facebook platform team for continuing to change the game in regards to API development.  Since the Facebook platform launched, they have always been ahead in changes like this.  I can only hope other API platforms can follow suite in giving developers more control like this.  No one likes their applications to break because of simple API changes.</p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F24%2Ffacebook-to-developers-you-decide%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F24%2Ffacebook-to-developers-you-decide%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/12jVV2K8JpQ4SdYvxOqdCngMIfM/0/da"><img src="http://feedads.g.doubleclick.net/~a/12jVV2K8JpQ4SdYvxOqdCngMIfM/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/12jVV2K8JpQ4SdYvxOqdCngMIfM/1/da"><img src="http://feedads.g.doubleclick.net/~a/12jVV2K8JpQ4SdYvxOqdCngMIfM/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=PAqHAr4-pHA:_QEe2RR3gjs:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=PAqHAr4-pHA:_QEe2RR3gjs:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=PAqHAr4-pHA:_QEe2RR3gjs:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=PAqHAr4-pHA:_QEe2RR3gjs:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=PAqHAr4-pHA:_QEe2RR3gjs:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=PAqHAr4-pHA:_QEe2RR3gjs:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=PAqHAr4-pHA:_QEe2RR3gjs:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=PAqHAr4-pHA:_QEe2RR3gjs:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/PAqHAr4-pHA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/24/facebook-to-developers-you-decide/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2009/11/wiki_logo-124x150.png" />
		<media:content url="http://staynalive.com/files/2009/11/wiki_logo.png" medium="image">
			<media:title type="html">facebook platform</media:title>
			<media:thumbnail url="http://staynalive.com/files/2009/11/wiki_logo-124x150.png" />
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F24%2Ffacebook-to-developers-you-decide%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/02/24/facebook-to-developers-you-decide/</feedburner:origLink></item>
		<item>
		<title>Speculation: Expect Something BIG in the Area of Real-Time at F8</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/aLP6yKap4RA/</link>
		<comments>http://staynalive.com/articles/2010/02/22/speculation-expect-something-big-in-the-area-of-real-time-at-f8/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 09:49:55 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[FriendFeed]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[butterfly]]></category>
		<category><![CDATA[butterfly effect]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[chrysalis]]></category>
		<category><![CDATA[f8]]></category>
		<category><![CDATA[paul buchheit]]></category>
		<category><![CDATA[real-time]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5791</guid>
		<description>I don&amp;#8217;t do speculative posts like this too often, except around Facebook&amp;#8217;s F8 developer events for the most part.  The last one I predicted was that Facebook would announce a Mobile Platform at F8 - the announcement did occur along with Facebook Connect.  The first F8 was the announcement of the Facebook API, which revolutionized [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/02/ali.jpeg" ><img class="alignright size-full wp-image-5793" title="ali" src="http://staynalive.com/files/2010/02/ali.jpeg" alt="" width="320" height="375" /></a>I don&#8217;t do speculative posts like this too often, except around Facebook&#8217;s F8 developer events for the most part.  The last one I predicted was that <a href="http://staynalive.com/articles/2008/07/06/facebook-to-launch-new-mobile-platform/" target="_blank" >Facebook would announce a Mobile Platform at F8 </a>- the announcement did occur along with Facebook Connect.  The first F8 was the announcement of the Facebook API, which revolutionized Social Development and has left players like Google scrambling to play catch up since.  Now, 2 years since the last F8, <a href="http://developers.facebook.com/news.php?blog=1&amp;story=347" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/developers.facebook.com');">the next F8 has been announced</a>, and we are all wondering what the next big announcement will be.  If it is to be in line with the last 2, and, considering they waited 2 years to have another one, they have to be announcing something game-changing.  I predict it directly involves some of the <a href="http://friendfeed.com/jessestay" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">FriendFeed</a> team and it&#8217;s directly related to real-time.</p>
<p>First of all, let me preface this with the fact that I am not receiving this data from any inside contacts at Facebook, nor have I been told anything the rest of the world doesn&#8217;t already know.  This is pure speculation &#8211; I hope it&#8217;s taken as such.  I am also certainly not a psychic.  I think if you look at some of the hints though, you can see the potential for something big, perhaps FriendFeed 3.0-like (remember, FriendFeed 2.0 was the <a href="http://blog.friendfeed.com/2009/04/whole-new-friendfeed.html" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.friendfeed.com');">advent of their real-time stream</a> you see now) about to happen at Facebook.  Here are my reasons for thinking such:</p>
<p><strong>What is Paul Buchheit Working on?</strong></p>
<p><a href="http://friendfeed.com/paul" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">Paul Buchheit</a>, one of the founders of FriendFeed, creator of Gmail, and now working at Facebook after FriendFeed was acquired, hasn&#8217;t yet made it evident exactly what he&#8217;s working on.  We know <a href="http://friendfeed.com/bret" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">Bret Taylor</a>, also a founder, is now Director of Product for Facebook, and working heavily with the Facebook APIs and the <a href="http://wiki.developers.facebook.com/index.php/Developer_Roadmap" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/wiki.developers.facebook.com');">new Roadmap</a> Facebook has laid out for developers.  We know Kevin Fox, pretty much the man behind all the design of FriendFeed, has been <a href="http://friendfeed.com/kfury/4e1e0a37/my-first-facebook-design-project-is-close-to" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">working on the new Games and Apps dashboard</a> that Facebook just launched (that you can see on the left-hand side of Facebook).</p>
<p>But what is Paul Buchheit working on?  He recently commented stating <a href="http://friendfeed.com/paul/5b941de2/no-i-am-not-working-on-anything-related-to-email" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">he is definitely not working on Facebook&#8217;s new e-mail product</a> that they have been rumored to be working on to replace their current inbox structure.  I&#8217;m not sure anyone has specifically stated exactly whether he&#8217;s working on the Facebook developer platform now or not.  He seems to be doing something big, and he&#8217;s certainly been studying Google Buzz recently if you look over his <a href="http://friendfeed.com/paul" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">FriendFeed stream</a> lately.</p>
<p><strong>Float Like a Butterfly, Sting Like a Bee</strong></p>
<p>Then there&#8217;s <a href="http://friendfeed.com/paul/498b340c/there-was-lot-of-chatter-about-future" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">that &#8220;Butterfly&#8221; post</a>.  Paul Buchheit specifically stated when <a href="http://scobleizer.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/scobleizer.com');">Robert Scoble</a>, <a href="http://techcrunchit.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/techcrunchit.com');">Steve Gillmor</a>, and others were all pressuring Facebook to make a statement on what they were going to do with FriendFeed that &#8220;the team is working on a couple of longer-term projects that will help bring FriendFeedy goodness to the larger world.&#8221;  He then continued, &#8220;Transformation is not the end. Consider this the chrysalis stage &#8212; if all goes well, a beautiful butterfly will emerge&#8221;.</p>
<p>The mystery in all this is that Facebook has not yet released anything even remotely similar to what Paul described yet.  Paul&#8217;s a <em><a href="http://deals.venturebeat.com/2010/02/18/buchheit/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/deals.venturebeat.com');">really smart guy</a></em>.  He&#8217;s not just going to work on something mediocre for Facebook &#8211; whatever it is, it has to be <em>game changing</em>.  I really believe that whatever it is will blow our minds away when it happens.  The FriendFeed team doesn&#8217;t just innovate.  They <em>revolutionize</em>.  I don&#8217;t believe they would still be at Facebook if they didn&#8217;t have that opportunity.</p>
<p><strong>Facebook&#8217;s Needs</strong></p>
<p>Then there&#8217;s the lack of any real-time APIs or architecture at Facebook.  I have to click on the page to have it refresh.  Frankly, I think that fits their current audience of 400 million+ &#8220;average Joes&#8221; well.  It doesn&#8217;t tap into the news-seeking, data-mining, and publishing audiences very well though.  That&#8217;s what Twitter does well.  It&#8217;s what FriendFeed and Buzz also do well.  All of these come with real-time APIs and real-time searches (or &#8220;track&#8221;).</p>
<p>Facebook needs a real-time interface for developers still.  It needs search.  It needs search to be real-time.  It needs a public view into all of that, supported by the powerful privacy controls Facebook already has in place.  Facebook has already built out the building blocks to launch this with their recent emphasis on encouraging users to open up their posts more and at the same time enabling them to have granularity in who sees those posts.  The next natural step is to finally open up those public posts to developers, and provide a real-time interface to it all.  With a 400 million user audience, <em>that</em> would be game-changing in the realm of real-time data.  We ain&#8217;t seen nothin&#8217; yet!</p>
<p><strong>The Lack of any Really Big Known Announcements at F8</strong></p>
<p>Lastly, we know everything else Facebook could announce at F8.  Facebook has already started <a href="http://staynalive.com/articles/2009/08/28/facebook-takes-a-page-out-of-itunes-with-credits-enabled-app-directory/" target="_blank" >rolling out credits</a> to developers, so a payment system wouldn&#8217;t be much of a &#8220;game changer&#8221; per se.  I&#8217;m sure they&#8217;ll talk a lot about it at the conference though.  Facebook has already started rolling out its <a href="http://wiki.developers.facebook.com/index.php/Ads_API_Getting_Started" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/wiki.developers.facebook.com');">Ads API</a> to developers.  They&#8217;ve already announced the desire to open up websites as virtual 3rd-party &#8220;Pages&#8221; on the web.  They&#8217;ve let us know just about everything in their roadmap, <em>except</em> the fate of FriendFeed.</p>
<p>Doesn&#8217;t this seem strange to you that Facebook and the FriendFeed team have been so mute on this in general for almost a year now?  What&#8217;s going on behind the scenes?  Even when asking the FriendFeed team about <a href="http://friendfeed.com/friendfeed-feedback/f3e72d7e/dearest-friendfeed-team-my-facebook-status" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/friendfeed.com');">plans to integrate better into Facebook</a> they have remained mute.  How cool would it be if, while everyone is ranting and raving about Google Buzz and calling FriendFeed dead, the FriendFeed team along with the incredible talent that Facebook adds to the mix have all been working on FriendFeed 3.0 behind the scenes?  What if Facebook caught wind Google was working on Buzz and bought FriendFeed <em>in response</em> to that rumor?  Will the &#8220;Butterfly&#8221; emerge at F8?  The chrysalis stage takes patience &#8211; I&#8217;m not giving up on FriendFeed yet.</p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F22%2Fspeculation-expect-something-big-in-the-area-of-real-time-at-f8%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F22%2Fspeculation-expect-something-big-in-the-area-of-real-time-at-f8%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/W8vmQw7JSeaMD0r5BWrIe8DmDtQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/W8vmQw7JSeaMD0r5BWrIe8DmDtQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/W8vmQw7JSeaMD0r5BWrIe8DmDtQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/W8vmQw7JSeaMD0r5BWrIe8DmDtQ/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=aLP6yKap4RA:W07phyplGb8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=aLP6yKap4RA:W07phyplGb8:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=aLP6yKap4RA:W07phyplGb8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=aLP6yKap4RA:W07phyplGb8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=aLP6yKap4RA:W07phyplGb8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=aLP6yKap4RA:W07phyplGb8:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=aLP6yKap4RA:W07phyplGb8:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=aLP6yKap4RA:W07phyplGb8:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/aLP6yKap4RA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/22/speculation-expect-something-big-in-the-area-of-real-time-at-f8/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/02/ali.jpeg" />
		<media:content url="http://staynalive.com/files/2010/02/ali.jpeg" medium="image">
			<media:title type="html">ali</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F22%2Fspeculation-expect-something-big-in-the-area-of-real-time-at-f8%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/02/22/speculation-expect-something-big-in-the-area-of-real-time-at-f8/</feedburner:origLink></item>
		<item>
		<title>Google Changes the Way You Read My Feeds – You Still Have no Control</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/UikwF90PxM8/</link>
		<comments>http://staynalive.com/articles/2010/02/20/google-changes-the-way-you-read-my-feeds-you-still-have-no-control/#comments</comments>
		<pubDate>Sat, 20 Feb 2010 07:34:23 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[control]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[filtering]]></category>
		<category><![CDATA[FriendFeed]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[lists]]></category>
		<category><![CDATA[monkey]]></category>
		<category><![CDATA[trapped]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5751</guid>
		<description>Louis Gray just reported a new way Google is trying to control the problem of mine and Louis&amp;#8217;s and Robert Scoble and Mashable, and more of the more active feeds and streams on Google Buzz taking over the streams of our followers.  The problem that was occuring is that for those with a lot of [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/02/letmeout2jd7.jpeg" ><img class="alignright size-full wp-image-5752" title="monkey trapped" src="http://staynalive.com/files/2010/02/letmeout2jd7.jpeg" alt="" width="378" height="257" /></a><a href="http://blog.louisgray.com/2010/02/google-buzz-reduces-power-users-bumpage.html" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.louisgray.com');">Louis Gray just reported</a> a new way <a href="http://www.google.com/buzz/googlebuzz/9WEiFaHBmwr/Making-tweaks-to-when-posts-get-bumped-back-to-the" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/www.google.com');">Google is trying to control the problem</a> of <a href="http://profiles.google.com/jessestay" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/profiles.google.com');">mine</a> and Louis&#8217;s and <a href="http://scobleizer.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/scobleizer.com');">Robert Scoble</a> and <a href="http://mashable.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/mashable.com');">Mashable</a>, and more of the more active feeds and streams on Google Buzz taking over the streams of our followers.  The problem that was occuring is that for those with a lot of followers, their posts would continue to dominate the streams of those following them because every time someone commented or liked the post, it would go right back to the top of your feed.  While I understand the problem, and agree there needs to be a fix, I argue Google is trying to fix this the wrong way.</p>
<p>The way Google decided to fix it is now they decide, based on some sort of algorithm, how often <a href="http://profiles.google.com/jessestay" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/profiles.google.com');">my feeds</a> get thrown up to the top of your stream.  This ensures no active user will ever fully dominate your stream.  However, what if we want to consume this data?  The problem is Google is the one making that choice for you, not giving you the power to make that choice yourself, and I think that&#8217;s a very wrong approach.</p>
<p>Rather than Google making that choice for us, they need to focus on lists, the way FriendFeed and Facebook do it, and the way over 400 million people are familiar with.  This is the natural flow &#8211; if someone is too noisy, you take them out of one list and put them in another.  Let us choose which list is the default.  Give us an easy way to assign people we follow into different lists.  This isn&#8217;t that difficult a solution for someone Google&#8217;s size, and gives the users absolute, full control, rather than taking it away from them to make the decision on how active their feeds are.  This needs to be their 100% focus right now to keep my attention.</p>
<p>The way Google is approaching this is wrong.  I really hope they change their focus to lists, open up the flood wall, but give us filters, privacy controls, and put the control back in the users&#8217; hands.  Don&#8217;t take our power away from us Google.</p>
<p><em>Image courtesy </em><a href="http://arbroath.blogspot.com/2008/03/let-me-out.html" onclick="javascript:urchinTracker ('/outbound/article/arbroath.blogspot.com');"><em>http://arbroath.blogspot.com/2008/03/let-me-out.html</em></a></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F20%2Fgoogle-changes-the-way-you-read-my-feeds-you-still-have-no-control%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F20%2Fgoogle-changes-the-way-you-read-my-feeds-you-still-have-no-control%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/PbX42-1n94R6FL_YPv_Y80W7mao/0/da"><img src="http://feedads.g.doubleclick.net/~a/PbX42-1n94R6FL_YPv_Y80W7mao/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/PbX42-1n94R6FL_YPv_Y80W7mao/1/da"><img src="http://feedads.g.doubleclick.net/~a/PbX42-1n94R6FL_YPv_Y80W7mao/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=UikwF90PxM8:oP4IkdhIknY:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=UikwF90PxM8:oP4IkdhIknY:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=UikwF90PxM8:oP4IkdhIknY:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=UikwF90PxM8:oP4IkdhIknY:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=UikwF90PxM8:oP4IkdhIknY:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=UikwF90PxM8:oP4IkdhIknY:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=UikwF90PxM8:oP4IkdhIknY:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=UikwF90PxM8:oP4IkdhIknY:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/UikwF90PxM8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/20/google-changes-the-way-you-read-my-feeds-you-still-have-no-control/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/02/letmeout2jd7.jpeg" />
		<media:content url="http://staynalive.com/files/2010/02/letmeout2jd7.jpeg" medium="image">
			<media:title type="html">monkey trapped</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F20%2Fgoogle-changes-the-way-you-read-my-feeds-you-still-have-no-control%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/02/20/google-changes-the-way-you-read-my-feeds-you-still-have-no-control/</feedburner:origLink></item>
		<item>
		<title>Did Google Reader Just Turn on the Firehose?</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/xoWHQaVW5ng/</link>
		<comments>http://staynalive.com/articles/2010/02/18/did-google-reader-just-turn-on-the-firehose/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 00:21:36 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[real-time web]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[firehose]]></category>
		<category><![CDATA[google reader]]></category>
		<category><![CDATA[pshb]]></category>
		<category><![CDATA[pubsub hubbub]]></category>
		<category><![CDATA[push]]></category>
		<category><![CDATA[reader]]></category>
		<category><![CDATA[realtime]]></category>
		<category><![CDATA[rss]]></category>
		<category><![CDATA[rss reader]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5720</guid>
		<description>Google&amp;#8217;s big push recently has been on enabling open, real-time technologies to publish, read, and interact with its new service Buzz.  Reader, its RSS subscription and website reading service, is one of the biggest tools to integrate with the service.  So much that my Reader contacts are now my Buzz contacts.  Until now, Google Reader, [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/02/drink-out-of-a-hose.jpeg" ><img class="alignright size-full wp-image-5721" title="firehose" src="http://staynalive.com/files/2010/02/drink-out-of-a-hose.jpeg" alt="" width="255" height="169" /></a>Google&#8217;s big push recently has been on enabling open, real-time technologies to publish, read, and interact with its new service Buzz.  <a href="http://reader.google.com" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/reader.google.com');">Reader</a>, its RSS subscription and website reading service, is one of the biggest tools to integrate with the service.  So much that my <a href="http://staynalive.com/articles/2010/02/09/google-reader-is-no-longer-an-rss-reader/" target="_blank" >Reader contacts are now my Buzz contacts</a>.  Until now, Google Reader, while when it would share your posts, it would send updates to subscribing services via Pubsub Hubbub (PSHB), it did not support the reading end of it for supported blogs that publish via PSHB.</p>
<p><a href="http://staynalive.com/articles/2010/02/18/is-googles-position-towards-default-privacy-a-good-thing/" target="_blank" >Just after my last post on Google</a> ironically, I noticed immediately after publishing people were sharing my post, something very unusual for the service, which usually takes up to an hour for my posts to show up on the site.  Going into Reader, I noticed it had immediately recognized my post.  I quickly queried a friend of mine at Google, who stated, &#8220;They can neither confirm nor deny my suspicion&#8221; (that it was launched), but I was &#8220;observant&#8221;.  Sounds like they just launched Pubsub Hubbub support.</p>
<p>Wordpress-enabled Blogs that want to be seen immediately after publishing in Google Reader just need to install <a href="http://wordpress.org/extend/plugins/pubsubhubbub/" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/wordpress.org');">Josh Fraser&#8217;s Pubsub Hubbub plugin for Wordpress</a>.  After hitting publish, your post should appear immediately afterwards in PSHB-supported clients, which, if I am correct, now includes Google Reader&#8217;s massive user base.</p>
<p>If this is true, you should see this post immediately after I hit publish in Google Reader.  Assuming I&#8217;m right (which it seems so), Robert Scoble&#8217;s concern of it taking <a href="http://scobleizer.posterous.com/why-i-dont-use-google-reader-anymore" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/scobleizer.posterous.com');">too long to get news</a> (#5) just went out the door today &#8211; he can now get this just as fast, if not faster than any service such as Twitter, FriendFeed, or Buzz, and this way, he gets to read the full content of the article.  When I hit publish on this post you will see it immediately.  You are <a href="http://staynalive.com/feed" target="_blank" >subscribed</a> to my feeds, right?</p>
<p>UPDATE: Just after hitting publish it appeared immediately in Google Reader on this post as well.  I&#8217;m 99.9% sure now that PSHB was launched on Google Reader today.</p>
<p><em>Image courtesy </em><a href="http://www.scotduke.com/getting-a-drink-out-of-a-fire-hose/" onclick="javascript:urchinTracker ('/outbound/article/www.scotduke.com');"><em>http://www.scotduke.com/getting-a-drink-out-of-a-fire-hose/</em></a></p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fdid-google-reader-just-turn-on-the-firehose%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fdid-google-reader-just-turn-on-the-firehose%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/zXGWm_QBYszc_KuC2dARNbfblwY/0/da"><img src="http://feedads.g.doubleclick.net/~a/zXGWm_QBYszc_KuC2dARNbfblwY/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/zXGWm_QBYszc_KuC2dARNbfblwY/1/da"><img src="http://feedads.g.doubleclick.net/~a/zXGWm_QBYszc_KuC2dARNbfblwY/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xoWHQaVW5ng:lbWsG1NaGV8:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xoWHQaVW5ng:lbWsG1NaGV8:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xoWHQaVW5ng:lbWsG1NaGV8:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xoWHQaVW5ng:lbWsG1NaGV8:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xoWHQaVW5ng:lbWsG1NaGV8:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xoWHQaVW5ng:lbWsG1NaGV8:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=xoWHQaVW5ng:lbWsG1NaGV8:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=xoWHQaVW5ng:lbWsG1NaGV8:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/xoWHQaVW5ng" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/18/did-google-reader-just-turn-on-the-firehose/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/02/drink-out-of-a-hose.jpeg" />
		<media:content url="http://staynalive.com/files/2010/02/drink-out-of-a-hose.jpeg" medium="image">
			<media:title type="html">firehose</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fdid-google-reader-just-turn-on-the-firehose%2F" medium="image" />
	<category domain="http://rss.financialcontent.com/stocksymbol">PSHB</category><feedburner:origLink>http://staynalive.com/articles/2010/02/18/did-google-reader-just-turn-on-the-firehose/</feedburner:origLink></item>
		<item>
		<title>Is Google’s Position Towards Default Privacy a Good Thing?</title>
		<link>http://feedproxy.google.com/~r/StayNAlive/~3/vxIBSvKO1iI/</link>
		<comments>http://staynalive.com/articles/2010/02/18/is-googles-position-towards-default-privacy-a-good-thing/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 23:37:13 +0000</pubDate>
		<dc:creator>Jesse Stay</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[buzz]]></category>
		<category><![CDATA[social]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[publicly available information]]></category>

		<guid isPermaLink="false">http://staynalive.com/?p=5713</guid>
		<description>I&amp;#8217;ve been openly critical about Google&amp;#8217;s lack of privacy in their launch of Buzz (and I argue other things as well), and its&amp;#8217; opt-in attitude towards opening up contacts and settings people previously thought were private.  That doesn&amp;#8217;t change.  However, I&amp;#8217;d like to spend some time here playing devil&amp;#8217;s advocate and share how perhaps, Google [...]</description>
			<content:encoded><![CDATA[<p><a href="http://staynalive.com/files/2010/02/privacy.jpeg" ><img class="alignright size-full wp-image-5714" title="privacy" src="http://staynalive.com/files/2010/02/privacy.jpeg" alt="" width="256" height="280" /></a>I&#8217;ve been openly critical about Google&#8217;s lack of privacy in their launch of Buzz (and I argue other things as well), and its&#8217; opt-in attitude towards opening up contacts and settings people previously thought were private.  That doesn&#8217;t change.  However, I&#8217;d like to spend some time here playing devil&#8217;s advocate and share how perhaps, Google starting with an open approach may be a good thing for Google in the long term.  Let me explain:</p>
<p>There&#8217;s no doubt that Google opening up all our data at the launch of Buzz is making people think more about Privacy.  I&#8217;ve had a post in the back of my head for quite awhile now that I was going to write on how I think Facebook could have made a mistake starting with a focus on privacy, as now people just assume that everything they put online is private, when in all actuality there is no way that will ever happen 100%.  Because of Facebook, people are getting more comfortable with posting their lives online, and while, even if Facebook remains a private environment for those people (in many cases it isn&#8217;t), they are now becoming more comfortable posting that information elsewhere, assuming it will remain private in those places as well.</p>
<p>I think Facebook could have done their users a disservice by giving them that comfort.  What if, instead of starting out private as Facebook did, they instead opened up everyone&#8217;s profile by default, and enabled them to choose what elements they want private after that?  Make people completely aware their information is 100% public, and then it is up to those people to decide what they share online, and what they would prefer stays private.  I think there would be a lot more education amongst users this way, and people would think twice before sharing things online.  Of course, Facebook wants people to share in easier ways and in a more comfortable environment to make sharing as easy as possible, so this isn&#8217;t going to happen, but it may have been even more in the right by defaulting to public on more things.  Ironically, these types of moves are what is getting Facebook a lot of flack as is, regardless of whether there are privacy controls in place that users can still turn on.</p>
<p>So perhaps Google is doing a good thing here.  Even the optimistic Louis Gray says <a href="http://blog.louisgray.com/2010/02/google-lets-fearmongers-and-unbelievers.html" target="_blank" onclick="javascript:urchinTracker ('/outbound/article/blog.louisgray.com');">we&#8217;re all wearing tin foil hats</a> by criticizing their lack of privacy.  By starting public (while I still argue turning what was previously private into a completely open environment is completely wrong, and it seems they&#8217;re backtracking to try and fix this), Google is encouraging each and every one of its hundreds of millions of users to think twice before sharing anything online.  Google is taking a risk here by making people think twice, since it makes money off of the content you share.</p>
<p>I fully predict Google will be adding more and more privacy controls as they move forward.  I agree, maybe they launched too soon before having these privacy controls in place.  One thing they may have done right though is that they are making us think twice about sharing.  They&#8217;re making each of us think about what goes online, and what stays off, and how comfortable we are with what we want public.  I think that&#8217;s a good thing, and more companies should be defaulting public, rather than private, until the general internet audience gets used to this type of environment where we know everything we share could very well be made public for the whole world to see.</p>
<p>I encourage you to step back and think about this &#8211; I agree, privacy is a good thing, but could the default to public be even better?  Are users being educated with this move?  It&#8217;s an interesting move by Google &#8211; let&#8217;s just hope they can get more privacy controls in place for users to choose from as they do it.</p>
<div class="tweetmeme_button" style="float: left; margin: 0 10px 0;"><a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fis-googles-position-towards-default-privacy-a-good-thing%2F" onclick="javascript:urchinTracker ('/outbound/article/api.tweetmeme.com');"><img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fis-googles-position-towards-default-privacy-a-good-thing%2F" height="61" width="51" /></a></div>
<p><a href="http://feedads.g.doubleclick.net/~a/cFQ1p25eLp1f2_rC1LaWImj_TcQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/cFQ1p25eLp1f2_rC1LaWImj_TcQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/cFQ1p25eLp1f2_rC1LaWImj_TcQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/cFQ1p25eLp1f2_rC1LaWImj_TcQ/1/di" border="0" ismap="true"></img></a></p><div class="feedflare">
<a href="http://feeds.feedburner.com/~ff/StayNAlive?a=vxIBSvKO1iI:Gqs5ZfyFOE0:D7DqB2pKExk"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=vxIBSvKO1iI:Gqs5ZfyFOE0:D7DqB2pKExk" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=vxIBSvKO1iI:Gqs5ZfyFOE0:yIl2AUoC8zA"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=yIl2AUoC8zA" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=vxIBSvKO1iI:Gqs5ZfyFOE0:V_sGLiPBpWU"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=vxIBSvKO1iI:Gqs5ZfyFOE0:V_sGLiPBpWU" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=vxIBSvKO1iI:Gqs5ZfyFOE0:gIN9vFwOqvQ"><img src="http://feeds.feedburner.com/~ff/StayNAlive?i=vxIBSvKO1iI:Gqs5ZfyFOE0:gIN9vFwOqvQ" border="0"></img></a> <a href="http://feeds.feedburner.com/~ff/StayNAlive?a=vxIBSvKO1iI:Gqs5ZfyFOE0:qj6IDK7rITs"><img src="http://feeds.feedburner.com/~ff/StayNAlive?d=qj6IDK7rITs" border="0"></img></a>
</div><img src="http://feeds.feedburner.com/~r/StayNAlive/~4/vxIBSvKO1iI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://staynalive.com/articles/2010/02/18/is-googles-position-towards-default-privacy-a-good-thing/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:thumbnail url="http://staynalive.com/files/2010/02/privacy.jpeg" />
		<media:content url="http://staynalive.com/files/2010/02/privacy.jpeg" medium="image">
			<media:title type="html">privacy</media:title>
		</media:content>
		<media:content url="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fstaynalive.com%2Farticles%2F2010%2F02%2F18%2Fis-googles-position-towards-default-privacy-a-good-thing%2F" medium="image" />
	<feedburner:origLink>http://staynalive.com/articles/2010/02/18/is-googles-position-towards-default-privacy-a-good-thing/</feedburner:origLink></item>
	<media:rating>nonadult</media:rating></channel>
</rss>
