rsarver
OAuth update around DM access: "Mission: Permission" http://t.co/DqMg7CC via @twitter
May 18, 2011, 5:06 PM | Reply | Retweet | Favorite
tapbot_paul
@jasoncosta @themattharris I'd really ask you guys to re-consider not allowing xAuth apps to access DMs. This will break tons of clients.
May 18, 2011, 5:15 PM | Reply | Retweet | Favorite
funkatron
@rsarver cool, I'm glad you're admitting it isn't a level playing field, and you're actively trying to kill us off.
May 18, 2011, 5:27 PM | Reply | Retweet | Favorite
funkatron
@rsarver remember when you told me how important it was that 3rd party devs felt respected? How do you think we feel now, Ryan?
May 18, 2011, 5:27 PM | Reply | Retweet | Favorite
funkatron
@rsarver You make me regret ever helping your service and other devs back in 2007. It's an embarassment.
May 18, 2011, 5:28 PM | Reply | Retweet | Favorite
isaiah
@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)?
May 18, 2011, 5:37 PM | Reply | Retweet | Favorite
timhaines
@rsarver "Permissions changes need to be done as quickly as we can" is BS when it's been the status quo for years.
May 18, 2011, 6:10 PM | Reply | Retweet | Favorite
orian
@rsarver my question is what is the rush? Seems like you're creating a lot of developer anxiety on whim, for what benefit?
May 18, 2011, 6:12 PM | Reply | Retweet | Favorite
rsarver
@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 :)
May 18, 2011, 6:13 PM | Reply | Retweet | Favorite
orian
@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
May 18, 2011, 6:14 PM | Reply | Retweet | Favorite
stevestreza
At #devnestSF, less than a week ago, I specifically asked about more granular permissions around DMs. @rsarver said nothing about it.
May 18, 2011, 6:15 PM | Reply | Retweet | Favorite
rsarver
@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
May 18, 2011, 6:15 PM | Reply | Retweet | Favorite
rsarver
@chockenberry twitter apps are part of the "service", not 3rd party apps asking for permission to access an account
May 18, 2011, 6:23 PM | Reply | Retweet | Favorite
chockenberry
@rsarver So you're confirming that the playing field isn't level for third party developers?
May 18, 2011, 6:30 PM | Reply | Retweet | Favorite
rsarver
@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
May 18, 2011, 6:32 PM | Reply | Retweet | Favorite
chockenberry
@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
May 18, 2011, 6:34 PM | Reply | Retweet | Favorite
rsarver
@gruber OAuth is for 3rd parties who need access to the service provider. we are the service provider
May 18, 2011, 6:34 PM | Reply | Retweet | Favorite
rsarver
@chockenberry I disagree. I'd love feedback on how we to improve the usability while still giving users clarity on what they are granting
May 18, 2011, 6:36 PM | Reply | Retweet | Favorite
rsarver
@abraham offered by the service provider. users grant us that permission and store their password with us. not the same as a 3rd party
May 18, 2011, 6:39 PM | Reply | Retweet | Favorite
rcw3
@chockenberry The logic that @rsarver is using to defend the continued attack by Twitter on 3rd party devs is pretty disgusting
May 18, 2011, 6:45 PM | Reply | Retweet | Favorite
jsnell
@chockenberry @gruber Okay, it's clear from further @rsarver tweets that Twitter is committed to bad startup UI for all 3rd party apps.
May 18, 2011, 6:46 PM | Reply | Retweet | Favorite
jasoncosta
@tapbot_paul we're available to help with the transition to web flow if an app wants DM access.
May 18, 2011, 8:21 PM | Reply | Retweet | Favorite
zorn
It's particularly frustrating that the official twitter apps will be getting special treatment. Thats some grade A bullshit. cc/ @rsarver
May 18, 2011, 8:26 PM | Reply | Retweet | Favorite
chockenberry
@jasoncosta @tapbot_paul Can you help get us through the Apple review queues in less than two weeks, too? :-)
May 18, 2011, 8:38 PM | Reply | Retweet | Favorite
jsnell
@rsarver Would be nice if you could provide some mechanism that allows clients to connect without forcing them into a web view.
May 18, 2011, 9:13 PM | Reply | Retweet | Favorite
rsarver
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
May 19, 2011, 12:31 AM | Reply | Retweet | Favorite
SteveStreza
Kind of want to write more about the #DMpocalypse. Maybe I should change the name of my blog to "Dumb Shit @TwitterAPI Does".
May 19, 2011, 1:07 AM | Reply | Retweet | Favorite
isaiah
when @al3x left twitter we wrote that he was crazy; we regret the error.
May 19, 2011, 1:16 AM | Reply | Retweet | Favorite
manton
Distracted today, finally caught up on Twitter's announcement that they will break DMs in every Mac/iOS client... except their own. Furious.
May 19, 2011, 1:41 AM | Reply | Retweet | Favorite
daringfireball
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
May 19, 2011, 1:50 AM | Reply | Retweet | Favorite
peternlewis
Really waiting for someone to knock Twitter off its perch. I mean, developers would support a twitter alternative in a hearty beat currently
May 19, 2011, 3:24 AM | Reply | Retweet | Favorite
danielpunkass
I discovered I have more than 140 characters of opinion about Twitter's actions today: http://t.co/NsbilwK
May 19, 2011, 4:10 AM | Reply | Retweet | Favorite
violasong
@danielpunkass Great write-up! I sure hope someone at Twitter is considering your solutions.
May 19, 2011, 6:54 AM | Reply | Retweet | Favorite
mattgemmell
Official Coffee Times commence. Today's theme: Man, can Twitter do _anything_ right anymore?
May 19, 2011, 9:31 AM | Reply | Retweet | Favorite
mattgemmell
Next up from Ryan Sarver: third-party Twitter clients must request auth tokens by mail, enclosing a prepaid envelope.
May 19, 2011, 9:34 AM | Reply | Retweet | Favorite
mattgemmell
Proposed hashtag for impending Twitter client updating deadline: #authpocalypse.
May 19, 2011, 9:38 AM | Reply | Retweet | Favorite
danielpunkass
@violasong Thank you! Great to hear from somebody who is well versed in developing a Twitter client :)
May 19, 2011, 1:08 PM | Reply | Retweet | Favorite
tapbot_paul
Today would be a very good day for Google to announce a Micro Blogging service.
May 19, 2011, 1:21 PM | Reply | Retweet | Favorite
danielpunkass
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
May 19, 2011, 3:00 PM | Reply | Retweet | Favorite
danielpunkass
Talking down to outrage loses the PR war.
May 19, 2011, 3:03 PM | Reply | Retweet | Favorite
jmwolfinbarger
@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.
May 19, 2011, 3:04 PM | Reply | Retweet | Favorite
danielpunkass
@jmwolfinbarger They should take a page from Machiavelli and deliver all their bad news at once. "No more 3rd party Twitter apps."
May 19, 2011, 3:08 PM | Reply | Retweet | Favorite
justinw
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.
May 19, 2011, 3:31 PM | Reply | Retweet | Favorite
marcoarment
Devil's advocate on Twitter's DM-OAuth change: http://t.co/3AshGLU
May 19, 2011, 3:49 PM | Reply | Retweet | Favorite
Lessien
Finding it hard not to see Twitter's API policy changes as an attempt to kneecap Uber Media. Smaller developers are collateral damage.
May 19, 2011, 3:53 PM | Reply | Retweet | Favorite
tapbot_paul
@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.
May 19, 2011, 3:56 PM | Reply | Retweet | Favorite
PenLlawen
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.
May 19, 2011, 4:01 PM | Reply | Retweet | Favorite
chockenberry
@tapbot_paul @jasoncosta Agreed. Sample code that's not web-based would be very helpful. Would help everyone understand the problem…
May 19, 2011, 4:03 PM | Reply | Retweet | Favorite
gedeon
Just signed up for identi.ca. You should in no way anything into this incredibly random happenstance - http://identi.ca/gedeon
May 19, 2011, 4:06 PM | Reply | Retweet | Favorite
manton
@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.
May 19, 2011, 4:15 PM | Reply | Retweet | Favorite
isaiah
@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.
May 19, 2011, 4:34 PM | Reply | Retweet | Favorite
isaiah
@marcoarment #2 no one is saying that they *cannot*, they are saying they *should not* these changes will make Twitter worse for customers.
May 19, 2011, 4:34 PM | Reply | Retweet | Favorite
isaiah
@marcoarment #3 things change, true. but some changes are better than others. i think Twitter has many alternatives that are better.
May 19, 2011, 4:34 PM | Reply | Retweet | Favorite
chockenberry
@SteveStreza @tapbot_paul Thanks Steve! Nice to know that you can get the account info from the token body (SSToken) — that's a biggie!
May 19, 2011, 4:35 PM | Reply | Retweet | Favorite
dannygreg
So it seems @twitterapi have decided that the horrific user experience of OAuth is acceptable. To think I thought they saw sense with xAuth!
May 19, 2011, 4:45 PM | Reply | Retweet | Favorite
CraigGrannell
By me: Twitter inflicts further dev pain, featuring special guest star @mattgemmell http://t.co/AZh289e
May 19, 2011, 4:46 PM | Reply | Retweet | Favorite
gruber
Is there a single developer of a native Twitter client app who is happy about the forced switch to OAuth?
May 19, 2011, 5:23 PM | Reply | Retweet | Favorite
stevenf
You guys, I thought "they own the platform they can do whatever they want" was the new mantra for the post-app-store world.
May 19, 2011, 5:42 PM | Reply | Retweet | Favorite
chockenberry
@themattharris That leaves me with one option: the use a built-in browser, pretend to be a web app, and sniff the connections.
May 19, 2011, 7:21 PM | Reply | Retweet | Favorite
themattharris
I've just posted a few more answers to questions about the new permission level http://t.co/28WeLX6
May 19, 2011, 8:18 PM | Reply | Retweet | Favorite
rno
Just created an FAQ page for our Application Permission Model. Will keep updating it as long as questions come. http://t.co/1TZXN80
May 19, 2011, 8:33 PM | Reply | Retweet | Favorite
BigZaphod
Can't wait for Twitter to start pimping their own apps on the OAuth sign in page.
May 23, 2011, 5:03 PM | Reply | Retweet | Favorite
gedeon
This is what Twitter's authentication change brings to 3rd party clients - http://dl.dropbox.com/u/2320369/oauth.mov
May 24, 2011, 4:08 PM | Reply | Retweet | Favorite
manton
@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.
May 24, 2011, 9:16 PM | Reply | Retweet | Favorite
SteveStreza
I wonder if any Twitter clients will have the stones to remove DMs from their app, instead of removing xAuth.
May 24, 2011, 9:34 PM | Reply | Retweet | Favorite
danielpunkass
@manton I'm prepared to code for OAuth when/if needed. But if there's going to be grandfathering, I want in ;)
May 24, 2011, 9:37 PM | Reply | Retweet | Favorite
manton
@SteveStreza I seriously considered removing DMs, but that only hurts customers. Just a bad deal all around.
May 24, 2011, 9:44 PM | Reply | Retweet | Favorite
timhaines
I think I can hear the @TweetDeck engineers in Europe rejoicing that they don't need to integrate the OAuth authentication workflow now.
May 25, 2011, 5:58 PM | Reply | Retweet | Favorite
gruber
Will TweetDeck have to use OAuth?
May 25, 2011, 9:19 PM | Reply | Retweet | Favorite
danielpunkass
@gruber Of course not. Why on earth would Twitter subject their users to such a thing?
May 25, 2011, 9:21 PM | Reply | Retweet | Favorite
manton
@gruber That's the question. It will be difficult for Twitter to argue that TweetDeck is "part of the service".
May 25, 2011, 9:27 PM | Reply | Retweet | Favorite

xAuth to OAuth

76 tweets

Published by Manton Reece (@manton)