<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in Twitter and OAuth, interesting brew (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/twitter_and_oauth_interesting_brew_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 21 Apr 2009 13:36:22 -0000</lastBuildDate><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8490870</link><description>&lt;p&gt;Dave, great analogy from the PC platforms wars of the eighties (for those who were active in IT at that time, it is a superb analogy!). Makes me think of all the different flavors of UNIX, and how one had to port applications to them so that you could really earn money with those applications.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeroen de Miranda</dc:creator><pubDate>Tue, 21 Apr 2009 13:36:22 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8481664</link><description>&lt;p&gt;i hope disqus is going to add twitter oath to its login options along with FB connect. i can't wait for that.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fredwilson</dc:creator><pubDate>Tue, 21 Apr 2009 06:58:52 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8478567</link><description>&lt;p&gt;any and all of the above. Talk to you tomorrow.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">stevegillmor</dc:creator><pubDate>Tue, 21 Apr 2009 01:37:17 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8475488</link><description>&lt;p&gt;Okay maybe I'll write more about it in the next few days.&lt;/p&gt;&lt;p&gt;I don't know what conclusions you've drawn, I do know that Kevin's&lt;br&gt;conclusions were very far from what I'm thinking of.&lt;/p&gt;&lt;p&gt;You haven't given me very much to go by.&lt;/p&gt;&lt;p&gt;I have written about this before, which is why I only skimmed the surface in&lt;br&gt;this post.&lt;/p&gt;&lt;p&gt;Maybe we should have a phone talk. Maybe do a podcast about this.&lt;/p&gt;&lt;p&gt;Whatever...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 20 Apr 2009 22:36:45 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8474594</link><description>&lt;p&gt;of course. however I am not understanding your opinion Dave. Is it that the benefits you cite outweigh the concern others have about creating the need for large monitization models that may inhibit innovation of the type you've previously favored?&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">stevegillmor</dc:creator><pubDate>Mon, 20 Apr 2009 22:16:25 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8473279</link><description>&lt;p&gt;I answered that question in reply to your first comment here. Let's not go&lt;br&gt;round in circles. You're entitled to your opinion Kevin, and of course I am&lt;br&gt;entitled to mine.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 20 Apr 2009 21:11:30 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8473191</link><description>&lt;p&gt;Clearly we're confusing each other. Why does Twitter need to compete with companies in the 'large blob of data' storage business (your point 2). &lt;br&gt;Why not just use S3 for a general one, one of the ones I mentioned for specific ones, or something like Leah's &lt;a href="http://baconfile.com" rel="nofollow noopener" target="_blank" title="http://baconfile.com"&gt;http://baconfile.com&lt;/a&gt; ?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kevinmarks</dc:creator><pubDate>Mon, 20 Apr 2009 21:08:05 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8472628</link><description>&lt;p&gt;Kevin, I'm saying what I said -- not what you say I said. You even have *me*&lt;br&gt;confused! :-)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 20 Apr 2009 20:42:30 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8472470</link><description>&lt;p&gt;Dave, I'm arguing for the enclosure model you championed with podcasting, where the feed has an external link to the media, not including it inline like email. You seem to be arguing the opposite. &lt;br&gt;Are you really saying we should store photos and videos and audio only in a twitter-provided silo, adn not be able to use Flickr in Twitter the way you have been doing?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kevinmarks</dc:creator><pubDate>Mon, 20 Apr 2009 20:35:25 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8471392</link><description>&lt;p&gt;That's good to hear. It would help simplify things for developers and give&lt;br&gt;more choice to users.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 20 Apr 2009 19:47:26 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8469270</link><description>&lt;p&gt;What's funny is that Facebook's proprietary delegated-auth system (fbauth) is almost identical to OAuth, so it *should* be super-trivial for them to support OAuth alongside fbauth as a way to access all of their APIs. And, IMO, it would be a great bang-for-the-buck developer and PR win for them, with no downside risk (since it's just replacing an existing component with a more standard and functionally equivalent version). Seems like some fb engineer that gets inspired should just hack this up over the weekend or something...any takers? :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joseph Smarr</dc:creator><pubDate>Mon, 20 Apr 2009 18:29:41 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8462980</link><description>&lt;p&gt;Because the power comes from all apps operating on the same data set.&lt;/p&gt;&lt;p&gt;Of course Twitter's data would live in this space. And it would be possible&lt;br&gt;to hang data off their objects: tweets, users, relationships, the calendar,&lt;br&gt;profiles, etc.&lt;/p&gt;&lt;p&gt;It's the same reason apps in the Lotus space stored data in spreadsheet&lt;br&gt;cells, and apps in the dBASE space stored them in tables.&lt;/p&gt;&lt;p&gt;Twitter defines a data space. That's where developers want to work.&lt;/p&gt;&lt;p&gt;Your company could blow through this one too Kevin.&lt;/p&gt;&lt;p&gt;BTW, we never agree on these things, and that's okay with me. Let's try all&lt;br&gt;approaches. I'm just a wise-ass and think I've been down this road before,&lt;br&gt;many times. I could be wrong. If you're fairminded you have to admit that's&lt;br&gt;possible for you too. Imho. YMMV.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Mon, 20 Apr 2009 14:44:39 -0000</pubDate></item><item><title>Re: Twitter and OAuth, interesting brew (Scripting News)</title><link>http://www.scripting.com/stories/2009/04/20/twitterAndOauthInteresting.html#comment-8462416</link><description>&lt;p&gt;Why should the storage and the event stream come from the same provider? FB does that now for photos and videos; Twitter doesn't need to, could use Flickr/Picasa/Smugmug/twitpic and YouTube/Vimeo/blip/qik or whomever else offers the easy storage, as happens now. A Tweetree-like default UX that shows the media links better may be the answer&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kevinmarks</dc:creator><pubDate>Mon, 20 Apr 2009 14:26:40 -0000</pubDate></item></channel></rss>