<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Terrell Russell: This Old Network &#187; oauth</title>
	<atom:link href="http://weblog.terrellrussell.com/tag/oauth/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.terrellrussell.com</link>
	<description>Ideas on interconnections, identity, and information from all sides.</description>
	<lastBuildDate>Thu, 22 Dec 2011 15:31:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>All My Hosted Stuff with Dynamic Sharing</title>
		<link>http://weblog.terrellrussell.com/2008/12/all-my-hosted-stuff-with-dynamic-sharing/</link>
		<comments>http://weblog.terrellrussell.com/2008/12/all-my-hosted-stuff-with-dynamic-sharing/#comments</comments>
		<pubDate>Sun, 14 Dec 2008 00:41:58 +0000</pubDate>
		<dc:creator>Terrell Russell</dc:creator>
				<category><![CDATA[Default]]></category>
		<category><![CDATA[allmystuff]]></category>
		<category><![CDATA[dynamic]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[irods]]></category>
		<category><![CDATA[oauth]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[procmail]]></category>
		<category><![CDATA[rules]]></category>
		<category><![CDATA[rules engine]]></category>
		<category><![CDATA[rulesets]]></category>
		<category><![CDATA[sharing]]></category>

		<guid isPermaLink="false">http://weblog.terrellrussell.com/?p=121</guid>
		<description><![CDATA[In the near future, we&#8217;ll all be able to host our own data. A few years ago it was very hard to do so, but possible, because nearly all the stuff being hosted was simple text with an occasional image or graphic. Then, our bandwidth increased and digital media creation tools were delivered into the [...]]]></description>
			<content:encoded><![CDATA[<p>In the near future, we&#8217;ll all be able to host our own data.</p>
<p>A few years ago it was very hard to do so, but possible, because nearly all the stuff being hosted was simple text with an occasional image or graphic.  Then, our bandwidth increased and digital media creation tools were delivered into the hands of &#8216;the rest of us&#8217;.  We quickly outstripped our ability to host and manage all our content and a market for hosted applications was born.  It hit its stride with Web 2.0.</p>
<p>The boom created a fantastic amount of opportunity.  It also stripped us of control.  While we were distracted by all the shiny new toys being offered over AJAX, we forgot that owning our own stuff was important.</p>
<p>Today, we&#8217;re back to the time when most of the people on the web were seeing it through the AOL lens.  Our data lives in silos and some of these silos even claim that your stuff is actually their stuff (have YOU read the <a href="http://www.facebook.com/terms.php">Facebook Terms of Use</a>?).</p>
<blockquote><p>When you post User Content to the Site, you authorize and direct us to make such copies thereof as we deem necessary in order to facilitate the posting and storage of the User Content on the Site. By posting User Content to any part of the Site, you automatically grant, and you represent and warrant that you have the right to grant, to the Company an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to use, copy, publicly perform, publicly display, reformat, translate, excerpt (in whole or in part) and distribute such User Content for any purpose, commercial, advertising, or otherwise, on or in connection with the Site or the promotion thereof, to prepare derivative works of, or incorporate into other works, such User Content, and to grant and authorize sublicenses of the foregoing. You may remove your User Content from the Site at any time. If you choose to remove your User Content, the license granted above will automatically expire, however you acknowledge that the Company may retain archived copies of your User Content. Facebook does not assert any ownership over your User Content; rather, as between us and you, subject to the rights granted to us in these Terms, you retain full ownership of all of your User Content and any intellectual property rights or other proprietary rights associated with your User Content.
</p></blockquote>
<p>We need to swing the pendulum back the other way.  We need to be able to host ALL our own stuff, or at least, be the proxy whereby we manage access to all our own stuff (even if it&#8217;s hosted on a vetted, corporate-backed network in a large datacenter somewhere in the &#8216;cloud&#8217;).</p>
<p>When you come to see my pictures, you come through <a href="http://gallery.terrellrussell.com">gallery.terrellrussell.com</a> &#8211; but the images could actually be served from Flickr via API.  And if/when I change that arrangement and move to smugmug.com via API, you&#8217;d still access them through gallery.terrellrussell.com.</p>
<p><img src="http://weblog.terrellrussell.com/wp-content/uploads/2008/12/terrellrussell_via_oauth.png" alt="terrellrussell_via_oauth" title="terrellrussell_via_oauth" width="512" height="700" class="aligncenter size-full wp-image-181" /></p>
<p>I want dynamic sharing.  I want to be able to put all my bits in one place (for sanity, for ease of backup, etc.) but I want some control over how those bits are shared with others (if at all).</p>
<p>I want dynamic privacy based on a set of rules.  These rules can be simple.  These rules can be complex.  There can be sets of rules that seem to cover 80% of the people 80% of the time.  The flexibility in a system like that would be paramount &#8211; how we deal with that flexibility is a different problem to be solved.</p>
<p>I want sharing rulesets that determine which stuff is visible and which stuff isn&#8217;t.  I want to have rulesets that determine this visibility by viewer, type of data (pictures/video/status), viewer tags, tags on the data, reputation from a third party, time of day, time passed since the creation of the stuff&#8230;  Let it be whatever &#8211; that&#8217;s the point.  A rules engine that can handle arbitrary rules and apply them on the fly.</p>
<p><strong>The graphic above is a first attempt at drawing what I want.  People will come to get stuff from me (or send stuff to me).  Their request will be processed through a set of rules I&#8217;ve put in place, identified as coming from a person/device I know, and then filtered through whatever authorizations that person/device has been granted.  If they are then allowed to see or receive what they&#8217;ve requested, I&#8217;ll send it to them.<br />
</strong></p>
<p>This has to be done with open source tools and protocols and we&#8217;ve already got two of them in the wild.  <a href="http://openid.net/">OpenID</a> for authentication and <a href="http://oauth.net/">OAuth</a> for authorization.  Additionally, we have <a href="http://www.hueniverse.com/hueniverse/2008/03/putting-xrds-si.html">XRDS-Simple</a> for service discovery.  We need an Open SharingRulesEngine (OShaRE?).</p>
<p>I want to have a full audit of how my stuff is getting accessed.  I want the ability to drill down and figure out what&#8217;s going on.  Not that I&#8217;ll use it very often &#8211; but I want to know that I can.</p>
<p>I want to be in control of who sees my content.  If you see a photo I took, embedded somewhere else, I&#8217;d like to know that happened.  I&#8217;d like to have a feel for where the edge of my &#8216;influence&#8217; lies and how it&#8217;s interacting with the rest of the world.</p>
<p>We&#8217;ve seen rules engines and rulesets and recipes before.  They exist for <a href="http://en.wikipedia.org/wiki/Business_rules_engine">business</a> and <a href="http://lipas.uwasa.fi/~ts/info/proctips.html">email (procmail)</a> and <a href="https://www.irods.org/index.php/Rule_Engine">distributed archival infrastructure (iRODS)</a>.  Help me build one for granting access to my stuff!</p>
<p>This could all be a pipe dream.  I&#8217;m not convinced one way or the other (the current sticking point is the realization that the gatekeeper software has to know about every piece of content I create/store&#8230;  complex&#8230; but doable&#8230;).  But I do know that if the option for individuals to host their own identity and their own content is available, the market for innovation will move that much faster.  And that&#8217;s almost always a good thing.</p>
<p>Whaddya say?  2 years for basic infrastructure that can do this?  5-7 years before it&#8217;s polished and anyone is using it but me?</p>
]]></content:encoded>
			<wfw:commentRss>http://weblog.terrellrussell.com/2008/12/all-my-hosted-stuff-with-dynamic-sharing/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>IIW, OpenLifeBits, and Facebook&#8217;s Beacon</title>
		<link>http://weblog.terrellrussell.com/2007/12/iiw-openlifebits-and-facebooks-beacon/</link>
		<comments>http://weblog.terrellrussell.com/2007/12/iiw-openlifebits-and-facebooks-beacon/#comments</comments>
		<pubDate>Wed, 19 Dec 2007 22:08:27 +0000</pubDate>
		<dc:creator>Terrell Russell</dc:creator>
				<category><![CDATA[Default]]></category>
		<category><![CDATA[beacon]]></category>
		<category><![CDATA[claimID]]></category>
		<category><![CDATA[dataportability]]></category>
		<category><![CDATA[iiw2007b]]></category>
		<category><![CDATA[oauth]]></category>
		<category><![CDATA[openlifebits]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[reputation]]></category>

		<guid isPermaLink="false">http://weblog.terrellrussell.com/2007/12/iiw-openlifebits-and-facebooks-beacon/</guid>
		<description><![CDATA[So, two weeks on, I write up my thoughts on my trip to IIW2007B at the Computer History Museum in Mountain View. As I wrote over at claimID, we had an incredible few days. There was a new energy in the air this time as interoperability was assumed and a focus on services began to [...]]]></description>
			<content:encoded><![CDATA[<p>So, two weeks on, I write up my thoughts on my trip to <a href="http://iiw.idcommons.net/index.php/Iiw2007b">IIW2007B</a> at the Computer History Museum in Mountain View.</p>
<p><a href="http://blog.claimid.com/2007/12/openid-20-and-oauth-10-announced-at-iiw2007b/">As I wrote over at claimID</a>, we had an incredible few days.  There was a new energy in the air this time as interoperability was assumed and a focus on services began to take centerstage.  There was a lot of talk about <a href="http://blogs.zdnet.com/BTL/?p=7244">Reputation</a>, <a href="http://openid.net/2007/12/05/openid-2_0-final-ly/">OpenID 2.0</a>, and <a href="http://blog.oauth.net/2007/12/04/oauth-core-10-specification-released-at-internet-identity-workshop/">OAuth 1.0</a>.  We&#8217;ve got the pieces now to begin building compelling applications and services.  The business models will be appearing in May at the next conference.</p>
<p>We even had an <a href="http://twitter.com/gwachob/statuses/470475632">impromptu OAuth party</a> on Tuesday night in honor of the <a href="http://www.hueniverse.com/hueniverse/2007/12/its-here-oauth.html">spec being released</a>.  <a href="http://josephsmarr.com/">Smarr</a>/<a href="http://www.davidrecordon.com/">Recordon</a>/<a href="http://blog.wachob.com/">Wachob</a>/<a href="http://www.hueniverse.com/">Hammer-Lahav</a>/<a href="http://factoryjoe.com/blog/">Messina</a> and myself.</p>
<p>I ran a session on Tuesday morning on <a href="http://weblog.terrellrussell.com/2007/11/openlifebits-for-your-digital-stuff/">OpenLifeBits</a> (thanks to <a href="http://journals.aol.com/panzerjohn/abstractioneer">John Panzer</a> for the <a href="http://iiw.idcommons.net/index.php/OpenLife_Bits">wiki notes</a>) &#8211; and had some excellent feedback as well as discussion around what we should be building to house/manage our personal information.  How do we define these bits and who owns this content?  Is the information we have housed in the corporate silos our own?  If someone else is involved in the creation of a particular piece of data &#8211; do we both own it?  Do we own it jointly with the company as well?  A friend request on Facebook &#8211; who&#8217;s is that to share?  Mine?  Hers?  Facebook&#8217;s?  Legally, today, it&#8217;s Facebook&#8217;s.</p>
<p>I&#8217;ll take credit here for two quotes captured on the wiki:</p>
<blockquote><p>&#8220;Stalkers were on MySpace, now Facebook _is_ the stalker.&#8221;</p></blockquote>
<p>A little over the top &#8211; but definitely something I feel strongly about.  We&#8217;re seeing individuals post more and more personal information into corporate repositories willingly and without due consideration for where their information is visible and/or to be used under the terms of service.</p>
<p><a href="http://www.zephoria.org/thoughts/archives/2007/12/11/facebooks_optou.html">I see Beacon as part of a greater slippery slope</a> &#8211; we&#8217;ll all be living, publicly documented, without recourse.</p>
<blockquote><p>&#8220;It&#8217;s a good thing that a bad thing became public&#8221; &#8212; on FB Beacon.</p></blockquote>
<p>I feel strongly that Beacon is only the first public-facing version of what these large corporations have been doing for years.  It is completely naive to think that companies will give away their services for free to the consumer without trying to leverage what they learn through statistics and demographics to make money.  They have to have a bottom line, or they go out of business.  Free or not, this stuff costs money to run.</p>
<p>When Facebook shows the public what is possible with their data, at first we squirm and yell, then we realize that we like more targeted information &#8211; it becomes less about SPAM and more about information we actually wanted.</p>
<p>The tricky part lies in where that fuzzy line of &#8216;worth it&#8217; is drawn.  Is it worth it for me to give my information to a company so I can get a free burger or $5 off my next box of detergent?  For most consumers, the answer is clearly yes &#8211; or we wouldn&#8217;t continue to see these types of offers.</p>
<p><a href="http://shift6.net/2007/12/06/respecting-digital-privacy/">A quote from Alison Black</a>:</p>
<blockquote><p>Getting inside people’s decision-making, to inject caution before commitment is likely to be extremely difficult (even with well-understood hazards, such as smoking and alcohol, health educators have difficulty getting their message across). But given that there is a likelihood that many people will continue to act humanly and, therefore, incautiously, there is an opportunity for companies to commit openly to respectful data handling. It may cramp their style for trading data in the future, but as more companies commit themselves to rigorous standards, those that don’t will stand out. Maybe this contrast could pique people’s consciousness just enough for them to ask ‘whatever they’re offering, do I want to hand my data over to them?’</p></blockquote>
<p>When things like Facebook Beacon force us to realize what is happening behind the scenes, we&#8217;re more likely to have informed opinions in the future (which is a good thing).  That said, I&#8217;m not holding my breath for when we&#8217;ll see all these companies go with opt-in as their default.  In today&#8217;s market, it just doesn&#8217;t pay nearly as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblog.terrellrussell.com/2007/12/iiw-openlifebits-and-facebooks-beacon/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

