i don't mean to be rude, but it sure feels like there is a large gap
between the PR announcement a couple weeks ago and the reality on the
ground. i'm trying to be patient in letting the info trickle down. i
guess i'll ask again in a couple weeks?
<hmmm hmm hmmm>
until then, my app is limping along with basic auth without attribution.
On Dec 29, 2009, at 1:30 PM, Raffi Krikorian wrote:
i don't know. sorry that i forgot to address your question.
On Tue, Dec 29, 2009 at 1:18 PM, Isaiah Carew <isa...@mac.com> wrote:
and how 'bout that off topic question?
a non-silent-treatment sort of answer would be really great -- even
if it's "i can't tell you" or "i don't know" or "that's on a need to
know basis and you don't need to know." or "you want the truth, you
can't handle the truth!" or whatever.
my biggest concern is that it won't come before the deprecation of
oAuth -- and I'll have to implement a pin bases solution in the
interim, then rip that out, then implement the new flow if/when it's
finally included in the twitter api. if that's the case, then i'm
going to need to budget some more $$ for this effort.
i'm just looking at what sort of effort and money i'm going to have
to spend on this in the next six months.
On Dec 29, 2009, at 1:06 PM, Raffi Krikorian wrote:
Also, off topic:
Any news on when we can expect the new oAuth with username/password
flow to make its way into the API? If you can't let me know, or
you don't know, I understand, but it would be good to hear whatever
Twitter Platform Team