<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>manton / xauthtooauth</title>
    <description>Tweets from the collection xAuth to OAuth on tweetlibrary.com.</description>
    <link>http://tweetlibrary.com/manton/xauthtooauth</link>
    <item>
      <title>manton</title>
      <link>http://twitter.com/manton/statuses/73500550972448768</link>
      <description>@gruber That's the question. It will be difficult for Twitter to argue that TweetDeck is "part of the service".</description>
      <pubDate>Wed, 25 May 2011 21:27:51 +0000</pubDate>
      <guid>http://twitter.com/manton/statuses/73500550972448768</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/73498984886435840</link>
      <description>@gruber Of course not. Why on earth would Twitter subject their users to such a thing?</description>
      <pubDate>Wed, 25 May 2011 21:21:38 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/73498984886435840</guid>
    </item>
    <item>
      <title>gruber</title>
      <link>http://twitter.com/gruber/statuses/73498361185054721</link>
      <description>Will TweetDeck have to use OAuth?</description>
      <pubDate>Wed, 25 May 2011 21:19:09 +0000</pubDate>
      <guid>http://twitter.com/gruber/statuses/73498361185054721</guid>
    </item>
    <item>
      <title>timhaines</title>
      <link>http://twitter.com/timhaines/statuses/73447918467694593</link>
      <description>I think I can hear the @TweetDeck engineers in Europe rejoicing that they don't need to integrate the OAuth authentication workflow now.</description>
      <pubDate>Wed, 25 May 2011 17:58:43 +0000</pubDate>
      <guid>http://twitter.com/timhaines/statuses/73447918467694593</guid>
    </item>
    <item>
      <title>manton</title>
      <link>http://twitter.com/manton/statuses/73142444350386178</link>
      <description>@SteveStreza I seriously considered removing DMs, but that only hurts customers. Just a bad deal all around.</description>
      <pubDate>Tue, 24 May 2011 21:44:52 +0000</pubDate>
      <guid>http://twitter.com/manton/statuses/73142444350386178</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/73140487246188545</link>
      <description>@manton I'm prepared to code for OAuth when/if needed. But if there's going to be grandfathering, I want in ;)</description>
      <pubDate>Tue, 24 May 2011 21:37:05 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/73140487246188545</guid>
    </item>
    <item>
      <title>SteveStreza</title>
      <link>http://twitter.com/SteveStreza/statuses/73139890019254272</link>
      <description>I wonder if any Twitter clients will have the stones to remove DMs from their app, instead of removing xAuth.</description>
      <pubDate>Tue, 24 May 2011 21:34:43 +0000</pubDate>
      <guid>http://twitter.com/SteveStreza/statuses/73139890019254272</guid>
    </item>
    <item>
      <title>manton</title>
      <link>http://twitter.com/manton/statuses/73135333327376384</link>
      <description>@danielpunkass Glad you got xAuth, but I wonder if you'll save time by coding to OAuth now anyway. Twitter has no love for legacy.</description>
      <pubDate>Tue, 24 May 2011 21:16:36 +0000</pubDate>
      <guid>http://twitter.com/manton/statuses/73135333327376384</guid>
    </item>
    <item>
      <title>gedeon</title>
      <link>http://twitter.com/gedeon/statuses/73057824086827008</link>
      <description>This is what Twitter's authentication change brings to 3rd party clients - http://dl.dropbox.com/u/2320369/oauth.mov</description>
      <pubDate>Tue, 24 May 2011 16:08:37 +0000</pubDate>
      <guid>http://twitter.com/gedeon/statuses/73057824086827008</guid>
    </item>
    <item>
      <title>BigZaphod</title>
      <link>http://twitter.com/BigZaphod/statuses/72709340074749952</link>
      <description>Can't wait for Twitter to start pimping their own apps on the OAuth sign in page.</description>
      <pubDate>Mon, 23 May 2011 17:03:52 +0000</pubDate>
      <guid>http://twitter.com/BigZaphod/statuses/72709340074749952</guid>
    </item>
    <item>
      <title>rno</title>
      <link>http://twitter.com/rno/statuses/71312421897248769</link>
      <description>Just created an FAQ page for our Application Permission Model. Will keep updating it as long as questions come. http://t.co/1TZXN80</description>
      <pubDate>Thu, 19 May 2011 20:33:00 +0000</pubDate>
      <guid>http://twitter.com/rno/statuses/71312421897248769</guid>
    </item>
    <item>
      <title>themattharris</title>
      <link>http://twitter.com/themattharris/statuses/71308790896660480</link>
      <description>I've just posted a few more answers to questions about the new permission level http://t.co/28WeLX6</description>
      <pubDate>Thu, 19 May 2011 20:18:35 +0000</pubDate>
      <guid>http://twitter.com/themattharris/statuses/71308790896660480</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/71294420267450368</link>
      <description>@themattharris That leaves me with one option: the use a built-in browser, pretend to be a web app, and sniff the connections.</description>
      <pubDate>Thu, 19 May 2011 19:21:29 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/71294420267450368</guid>
    </item>
    <item>
      <title>stevenf</title>
      <link>http://twitter.com/stevenf/statuses/71269546295701504</link>
      <description>You guys, I thought "they own the platform they can do whatever they want" was the new mantra for the post-app-store world.</description>
      <pubDate>Thu, 19 May 2011 17:42:38 +0000</pubDate>
      <guid>http://twitter.com/stevenf/statuses/71269546295701504</guid>
    </item>
    <item>
      <title>gruber</title>
      <link>http://twitter.com/gruber/statuses/71264768320745472</link>
      <description>Is there a single developer of a native Twitter client app who is happy about the forced switch to OAuth?</description>
      <pubDate>Thu, 19 May 2011 17:23:39 +0000</pubDate>
      <guid>http://twitter.com/gruber/statuses/71264768320745472</guid>
    </item>
    <item>
      <title>CraigGrannell</title>
      <link>http://twitter.com/CraigGrannell/statuses/71255531049857024</link>
      <description>By me: Twitter inflicts further dev pain, featuring special guest star @mattgemmell http://t.co/AZh289e</description>
      <pubDate>Thu, 19 May 2011 16:46:57 +0000</pubDate>
      <guid>http://twitter.com/CraigGrannell/statuses/71255531049857024</guid>
    </item>
    <item>
      <title>dannygreg</title>
      <link>http://twitter.com/dannygreg/statuses/71255284697403392</link>
      <description>So it seems @twitterapi have decided that the horrific user experience of OAuth is acceptable. To think I thought they saw sense with xAuth!</description>
      <pubDate>Thu, 19 May 2011 16:45:58 +0000</pubDate>
      <guid>http://twitter.com/dannygreg/statuses/71255284697403392</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/71252586963025920</link>
      <description>@SteveStreza @tapbot_paul Thanks Steve! Nice to know that you can get the account info from the token body (SSToken) — that's a biggie!</description>
      <pubDate>Thu, 19 May 2011 16:35:15 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/71252586963025920</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71252334113599488</link>
      <description>@marcoarment #3 things change, true. but some changes are better than others.
i think Twitter has many alternatives that are better.</description>
      <pubDate>Thu, 19 May 2011 16:34:14 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71252334113599488</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71252324085010432</link>
      <description>@marcoarment #2 no one is saying that they *cannot*, they are saying they *should not* 
these changes will make Twitter worse for customers.</description>
      <pubDate>Thu, 19 May 2011 16:34:12 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71252324085010432</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71252316543660032</link>
      <description>@marcoarment #1 you're just wrong. every app that shows DMs will have to change to at least remove the UI or add OAuth. it's a big deal.</description>
      <pubDate>Thu, 19 May 2011 16:34:10 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71252316543660032</guid>
    </item>
    <item>
      <title>manton</title>
      <link>http://twitter.com/manton/statuses/71247651496136705</link>
      <description>@marcoarment The problem with your point 2 is that it can be used to justify many terrible ideas. "Because we can" is not good enough.</description>
      <pubDate>Thu, 19 May 2011 16:15:38 +0000</pubDate>
      <guid>http://twitter.com/manton/statuses/71247651496136705</guid>
    </item>
    <item>
      <title>gedeon</title>
      <link>http://twitter.com/gedeon/statuses/71245339054702592</link>
      <description>Just signed up for identi.ca. You should in no way anything into this incredibly random happenstance - http://identi.ca/gedeon</description>
      <pubDate>Thu, 19 May 2011 16:06:27 +0000</pubDate>
      <guid>http://twitter.com/gedeon/statuses/71245339054702592</guid>
    </item>
    <item>
      <title>SteveStreza</title>
      <link>http://twitter.com/SteveStreza/statuses/71245129205293056</link>
      <description>@chockenberry @tapbot_paul https://github.com/amazingsyco/oauthery</description>
      <pubDate>Thu, 19 May 2011 16:05:37 +0000</pubDate>
      <guid>http://twitter.com/SteveStreza/statuses/71245129205293056</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/71244486675677185</link>
      <description>@tapbot_paul @jasoncosta Agreed. Sample code that's not web-based would be very helpful. Would help everyone understand the problem…</description>
      <pubDate>Thu, 19 May 2011 16:03:03 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/71244486675677185</guid>
    </item>
    <item>
      <title>PenLlawen</title>
      <link>http://twitter.com/PenLlawen/statuses/71244107019849729</link>
      <description>If you watch it backwards, Twitter's API is a remake of A Christmas Carol; a bitter control freak wins friends by becoming helpful and kind.</description>
      <pubDate>Thu, 19 May 2011 16:01:33 +0000</pubDate>
      <guid>http://twitter.com/PenLlawen/statuses/71244107019849729</guid>
    </item>
    <item>
      <title>tapbot_paul</title>
      <link>http://twitter.com/tapbot_paul/statuses/71242853162033152</link>
      <description>@jasoncosta here's something that'd help. Sample iPhone code that shows the proper way to do an oAuth flow and can handle multiple users.</description>
      <pubDate>Thu, 19 May 2011 15:56:34 +0000</pubDate>
      <guid>http://twitter.com/tapbot_paul/statuses/71242853162033152</guid>
    </item>
    <item>
      <title>Lessien</title>
      <link>http://twitter.com/Lessien/statuses/71242125030858752</link>
      <description>Finding it hard not to see Twitter's API policy changes as an attempt to kneecap Uber Media. Smaller developers are collateral damage.</description>
      <pubDate>Thu, 19 May 2011 15:53:40 +0000</pubDate>
      <guid>http://twitter.com/Lessien/statuses/71242125030858752</guid>
    </item>
    <item>
      <title>marcoarment</title>
      <link>http://twitter.com/marcoarment/statuses/71241014039416832</link>
      <description>Devil's advocate on Twitter's DM-OAuth change: http://t.co/3AshGLU</description>
      <pubDate>Thu, 19 May 2011 15:49:15 +0000</pubDate>
      <guid>http://twitter.com/marcoarment/statuses/71241014039416832</guid>
    </item>
    <item>
      <title>justinw</title>
      <link>http://twitter.com/justinw/statuses/71236655272566785</link>
      <description>I'd actually respect Twitter slightly more if they just came out and shut off API access rather than inconveniencing devs to force them out.</description>
      <pubDate>Thu, 19 May 2011 15:31:56 +0000</pubDate>
      <guid>http://twitter.com/justinw/statuses/71236655272566785</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/71230729442435073</link>
      <description>@jmwolfinbarger They should take a page from Machiavelli and deliver all their bad news at once. "No more 3rd party Twitter apps."</description>
      <pubDate>Thu, 19 May 2011 15:08:23 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/71230729442435073</guid>
    </item>
    <item>
      <title>jmwolfinbarger</title>
      <link>http://twitter.com/jmwolfinbarger/statuses/71229852849676288</link>
      <description>@danielpunkass My impression is they're not interested in winning the PR war. They've made a decision and are prepared to weather the storm.</description>
      <pubDate>Thu, 19 May 2011 15:04:54 +0000</pubDate>
      <guid>http://twitter.com/jmwolfinbarger/statuses/71229852849676288</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/71229445087825920</link>
      <description>Talking down to outrage loses the PR war.</description>
      <pubDate>Thu, 19 May 2011 15:03:17 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/71229445087825920</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/71228694118678528</link>
      <description>Twitter's @rsarver has studied the Jedi mind trick, but hasn't perfected it. These apps are not apps. They're services! http://t.co/FOLWt96</description>
      <pubDate>Thu, 19 May 2011 15:00:18 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/71228694118678528</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71228672664797185</link>
      <description>Macworld says I'm melancholy
http://tumblr.com/xip2l8xhj2

snif.</description>
      <pubDate>Thu, 19 May 2011 15:00:13 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71228672664797185</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71218713306738688</link>
      <description>As usual, @gruber nails it.
http://tumblr.com/xip2l8jj1l</description>
      <pubDate>Thu, 19 May 2011 14:20:39 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71218713306738688</guid>
    </item>
    <item>
      <title>tapbot_paul</title>
      <link>http://twitter.com/tapbot_paul/statuses/71203940733165568</link>
      <description>Today would be a very good day for Google to announce a Micro Blogging service.</description>
      <pubDate>Thu, 19 May 2011 13:21:57 +0000</pubDate>
      <guid>http://twitter.com/tapbot_paul/statuses/71203940733165568</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/71200531032457216</link>
      <description>@violasong Thank you! Great to hear from somebody who is well versed in developing a Twitter client :)</description>
      <pubDate>Thu, 19 May 2011 13:08:24 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/71200531032457216</guid>
    </item>
    <item>
      <title>mattgemmell</title>
      <link>http://twitter.com/mattgemmell/statuses/71147728880680960</link>
      <description>Proposed hashtag for impending Twitter client updating deadline: #authpocalypse.</description>
      <pubDate>Thu, 19 May 2011 09:38:35 +0000</pubDate>
      <guid>http://twitter.com/mattgemmell/statuses/71147728880680960</guid>
    </item>
    <item>
      <title>mattgemmell</title>
      <link>http://twitter.com/mattgemmell/statuses/71146819685588992</link>
      <description>Next up from Ryan Sarver: third-party Twitter clients must request auth tokens by mail, enclosing a prepaid envelope.</description>
      <pubDate>Thu, 19 May 2011 09:34:58 +0000</pubDate>
      <guid>http://twitter.com/mattgemmell/statuses/71146819685588992</guid>
    </item>
    <item>
      <title>mattgemmell</title>
      <link>http://twitter.com/mattgemmell/statuses/71146053688238080</link>
      <description>Official Coffee Times commence. Today's theme: Man, can Twitter do _anything_ right anymore?</description>
      <pubDate>Thu, 19 May 2011 09:31:55 +0000</pubDate>
      <guid>http://twitter.com/mattgemmell/statuses/71146053688238080</guid>
    </item>
    <item>
      <title>violasong</title>
      <link>http://twitter.com/violasong/statuses/71106423823671296</link>
      <description>@danielpunkass Great write-up! I sure hope someone at Twitter is considering your solutions.</description>
      <pubDate>Thu, 19 May 2011 06:54:27 +0000</pubDate>
      <guid>http://twitter.com/violasong/statuses/71106423823671296</guid>
    </item>
    <item>
      <title>damon</title>
      <link>http://twitter.com/damon/statuses/71085180374368256</link>
      <description>This just makes me angry http://daringfireball.net/2011/05/twitter_shit_sandwich ; https://twitter.com/#!/rsarver/status/70917459078680577</description>
      <pubDate>Thu, 19 May 2011 05:30:02 +0000</pubDate>
      <guid>http://twitter.com/damon/statuses/71085180374368256</guid>
    </item>
    <item>
      <title>danielpunkass</title>
      <link>http://twitter.com/danielpunkass/statuses/71065071610109952</link>
      <description>I discovered I have more than 140 characters of opinion about Twitter's actions today: http://t.co/NsbilwK</description>
      <pubDate>Thu, 19 May 2011 04:10:08 +0000</pubDate>
      <guid>http://twitter.com/danielpunkass/statuses/71065071610109952</guid>
    </item>
    <item>
      <title>peternlewis</title>
      <link>http://twitter.com/peternlewis/statuses/71053706359091200</link>
      <description>Really waiting for someone to knock Twitter off its perch. I mean, developers would support a twitter alternative in a hearty beat currently</description>
      <pubDate>Thu, 19 May 2011 03:24:58 +0000</pubDate>
      <guid>http://twitter.com/peternlewis/statuses/71053706359091200</guid>
    </item>
    <item>
      <title>daringfireball</title>
      <link>http://twitter.com/daringfireball/statuses/71029839016103936</link>
      <description>Translation From Weasel-Speak to English of the Key Question in Twitter’s FAQ for Developers Regarding Their New Policy f… http://df4.us/hnb</description>
      <pubDate>Thu, 19 May 2011 01:50:07 +0000</pubDate>
      <guid>http://twitter.com/daringfireball/statuses/71029839016103936</guid>
    </item>
    <item>
      <title>manton</title>
      <link>http://twitter.com/manton/statuses/71027616571850752</link>
      <description>Distracted today, finally caught up on Twitter's announcement that they will break DMs in every Mac/iOS client... except their own. Furious.</description>
      <pubDate>Thu, 19 May 2011 01:41:18 +0000</pubDate>
      <guid>http://twitter.com/manton/statuses/71027616571850752</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/71021306849665024</link>
      <description>when @al3x left twitter we wrote that he was crazy; we regret the error.</description>
      <pubDate>Thu, 19 May 2011 01:16:13 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/71021306849665024</guid>
    </item>
    <item>
      <title>SteveStreza</title>
      <link>http://twitter.com/SteveStreza/statuses/71019111563530240</link>
      <description>Kind of want to write more about the #DMpocalypse. Maybe I should change the name of my blog to "Dumb Shit @TwitterAPI Does".</description>
      <pubDate>Thu, 19 May 2011 01:07:30 +0000</pubDate>
      <guid>http://twitter.com/SteveStreza/statuses/71019111563530240</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/71010055167803393</link>
      <description>we've been listening to feedback and are going to extend the transition timeline by two weeks to June 14th. more here: http://t.co/gh5FSGD</description>
      <pubDate>Thu, 19 May 2011 00:31:31 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/71010055167803393</guid>
    </item>
    <item>
      <title>daringfireball</title>
      <link>http://twitter.com/daringfireball/statuses/70963141906935808</link>
      <description>★ Twitter’s Shit Sandwich: http://df4.us/hn8</description>
      <pubDate>Wed, 18 May 2011 21:25:06 +0000</pubDate>
      <guid>http://twitter.com/daringfireball/statuses/70963141906935808</guid>
    </item>
    <item>
      <title>jsnell</title>
      <link>http://twitter.com/jsnell/statuses/70960145164808192</link>
      <description>@rsarver Would be nice if you could provide some mechanism that allows clients to connect without forcing them into a web view.</description>
      <pubDate>Wed, 18 May 2011 21:13:11 +0000</pubDate>
      <guid>http://twitter.com/jsnell/statuses/70960145164808192</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/70951413517271041</link>
      <description>@jasoncosta @tapbot_paul Can you help get us through the Apple review queues in less than two weeks, too? :-)</description>
      <pubDate>Wed, 18 May 2011 20:38:29 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/70951413517271041</guid>
    </item>
    <item>
      <title>zorn</title>
      <link>http://twitter.com/zorn/statuses/70948328443088896</link>
      <description>It's particularly frustrating that the official twitter apps will be getting special treatment. Thats some grade A bullshit. cc/ @rsarver</description>
      <pubDate>Wed, 18 May 2011 20:26:14 +0000</pubDate>
      <guid>http://twitter.com/zorn/statuses/70948328443088896</guid>
    </item>
    <item>
      <title>jasoncosta</title>
      <link>http://twitter.com/jasoncosta/statuses/70947249630347264</link>
      <description>@tapbot_paul we're available to help with the transition to web flow if an app wants DM access.</description>
      <pubDate>Wed, 18 May 2011 20:21:57 +0000</pubDate>
      <guid>http://twitter.com/jasoncosta/statuses/70947249630347264</guid>
    </item>
    <item>
      <title>jsnell</title>
      <link>http://twitter.com/jsnell/statuses/70923239035113472</link>
      <description>@chockenberry @gruber Okay, it's clear from further @rsarver tweets that Twitter is committed to bad startup UI for all 3rd party apps.</description>
      <pubDate>Wed, 18 May 2011 18:46:32 +0000</pubDate>
      <guid>http://twitter.com/jsnell/statuses/70923239035113472</guid>
    </item>
    <item>
      <title>rcw3</title>
      <link>http://twitter.com/rcw3/statuses/70922856472649728</link>
      <description>@chockenberry The logic that @rsarver is using to defend the continued attack by Twitter on 3rd party devs is pretty disgusting</description>
      <pubDate>Wed, 18 May 2011 18:45:01 +0000</pubDate>
      <guid>http://twitter.com/rcw3/statuses/70922856472649728</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70921428899336192</link>
      <description>@abraham offered by the service provider. users grant us that permission and store their password with us. not the same as a 3rd party</description>
      <pubDate>Wed, 18 May 2011 18:39:20 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70921428899336192</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70920755419942912</link>
      <description>@chockenberry I disagree. I'd love feedback on how we to improve the usability while still giving users clarity on what they are granting</description>
      <pubDate>Wed, 18 May 2011 18:36:40 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70920755419942912</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70920322236420097</link>
      <description>@gruber OAuth is for 3rd parties who need access to the service provider. we are the service provider</description>
      <pubDate>Wed, 18 May 2011 18:34:57 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70920322236420097</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/70920196541517824</link>
      <description>@rsarver A traditional OAuth flow in your apps makes as much sense as it does in ours. Hurts usability, ask Loren: http://bit.ly/JfCoH</description>
      <pubDate>Wed, 18 May 2011 18:34:27 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/70920196541517824</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70919598727376896</link>
      <description>@chockenberry it is level for all 3rd party developers. Not sure how it maks sense that a user would see an OAuth flow for Tw4iPhone</description>
      <pubDate>Wed, 18 May 2011 18:32:04 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70919598727376896</guid>
    </item>
    <item>
      <title>chockenberry</title>
      <link>http://twitter.com/chockenberry/statuses/70919306795429888</link>
      <description>@rsarver So you're confirming that the playing field isn't level for third party developers?</description>
      <pubDate>Wed, 18 May 2011 18:30:55 +0000</pubDate>
      <guid>http://twitter.com/chockenberry/statuses/70919306795429888</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70917459078680577</link>
      <description>@chockenberry twitter apps are part of the "service", not 3rd party apps asking for permission to access an account</description>
      <pubDate>Wed, 18 May 2011 18:23:34 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70917459078680577</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70915392905805824</link>
      <description>@orian not sure that's a comparison. the team isn't sitting around. we have a small team that needs to prioritize. I know you do the same</description>
      <pubDate>Wed, 18 May 2011 18:15:21 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70915392905805824</guid>
    </item>
    <item>
      <title>stevestreza</title>
      <link>http://twitter.com/stevestreza/statuses/70915377630150656</link>
      <description>At #devnestSF, less than a week ago, I specifically asked about more granular permissions around DMs. @rsarver said nothing about it.</description>
      <pubDate>Wed, 18 May 2011 18:15:18 +0000</pubDate>
      <guid>http://twitter.com/stevestreza/statuses/70915377630150656</guid>
    </item>
    <item>
      <title>orian</title>
      <link>http://twitter.com/orian/statuses/70915120062140417</link>
      <description>@rsarver I'm really glad to see Twitter wanting to move quicker w things, but it takes 6m - 1yr for Twitter to fix documentation errors</description>
      <pubDate>Wed, 18 May 2011 18:14:16 +0000</pubDate>
      <guid>http://twitter.com/orian/statuses/70915120062140417</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70914945696530432</link>
      <description>@orian we feel it's important to have a short window for a change in permissions models. obviously we're not doing it on a whim :)</description>
      <pubDate>Wed, 18 May 2011 18:13:35 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70914945696530432</guid>
    </item>
    <item>
      <title>orian</title>
      <link>http://twitter.com/orian/statuses/70914658168614912</link>
      <description>@rsarver my question is what is the rush? Seems like you're creating a lot of developer anxiety on whim, for what benefit?</description>
      <pubDate>Wed, 18 May 2011 18:12:26 +0000</pubDate>
      <guid>http://twitter.com/orian/statuses/70914658168614912</guid>
    </item>
    <item>
      <title>timhaines</title>
      <link>http://twitter.com/timhaines/statuses/70914103174119424</link>
      <description>@rsarver "Permissions changes need to be done as quickly as we can" is BS when it's been the status quo for years.</description>
      <pubDate>Wed, 18 May 2011 18:10:14 +0000</pubDate>
      <guid>http://twitter.com/timhaines/statuses/70914103174119424</guid>
    </item>
    <item>
      <title>isaiah</title>
      <link>http://twitter.com/isaiah/statuses/70905804852695040</link>
      <description>@rsarver - are you guys serious about this xAuth DM thing? won't that be a support nightmare for you guys (and us 3rd party guys too)?</description>
      <pubDate>Wed, 18 May 2011 17:37:15 +0000</pubDate>
      <guid>http://twitter.com/isaiah/statuses/70905804852695040</guid>
    </item>
    <item>
      <title>funkatron</title>
      <link>http://twitter.com/funkatron/statuses/70903683348570112</link>
      <description>@rsarver You make me regret ever helping your service and other devs back in 2007. It's an embarassment.</description>
      <pubDate>Wed, 18 May 2011 17:28:50 +0000</pubDate>
      <guid>http://twitter.com/funkatron/statuses/70903683348570112</guid>
    </item>
    <item>
      <title>funkatron</title>
      <link>http://twitter.com/funkatron/statuses/70903436719308801</link>
      <description>@rsarver remember when you told me how important it was that 3rd party devs felt respected? How do you think we feel now, Ryan?</description>
      <pubDate>Wed, 18 May 2011 17:27:51 +0000</pubDate>
      <guid>http://twitter.com/funkatron/statuses/70903436719308801</guid>
    </item>
    <item>
      <title>funkatron</title>
      <link>http://twitter.com/funkatron/statuses/70903312559521792</link>
      <description>@rsarver cool, I'm glad you're admitting it isn't a level playing field, and you're actively trying to kill us off.</description>
      <pubDate>Wed, 18 May 2011 17:27:21 +0000</pubDate>
      <guid>http://twitter.com/funkatron/statuses/70903312559521792</guid>
    </item>
    <item>
      <title>tapbot_paul</title>
      <link>http://twitter.com/tapbot_paul/statuses/70900244514213888</link>
      <description>@jasoncosta @themattharris I'd really ask you guys to re-consider not allowing xAuth apps to access DMs. This will break tons of clients.</description>
      <pubDate>Wed, 18 May 2011 17:15:10 +0000</pubDate>
      <guid>http://twitter.com/tapbot_paul/statuses/70900244514213888</guid>
    </item>
    <item>
      <title>rsarver</title>
      <link>http://twitter.com/rsarver/statuses/70898050855477248</link>
      <description>OAuth update around DM access: "Mission: Permission" http://t.co/DqMg7CC via @twitter</description>
      <pubDate>Wed, 18 May 2011 17:06:27 +0000</pubDate>
      <guid>http://twitter.com/rsarver/statuses/70898050855477248</guid>
    </item>
  </channel>
</rss>

