that each developer must find,
analyze and implement. It's difficult. We're not doing so well.
In order to make bug-free clients we need Twitter to make the schema the same,
or (if that sausage is too expensive) document how they differ.
isaiah
http://twitter.com/isaiah
On Dec
don't have to answer, I'm just mouthing off. I'll get back to work writing a
track-term to nspredicate converter. ;-)
isaiah
http://twitter.com/isaiah
On Dec 13, 2010, at 9:30 AM, John Kalucki wrote:
> Roughly:
> If the tweet is from a following, place it in the home timelin
atuses returned as a specific
track parameter from those returned for other reasons?
2. Is there some other way to skin this cat that I'm missing?
Thanks,
Isaiah
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twit
The bonus is that it's a way to still use plain old curl for testing.
Awesome!
On Sep 13, 9:21 am, Dewald Pretorius wrote:
> They must have known that this was going to be discovered. We're
> developers. We like building, testing, and breaking stuff.
>
> Unequal applications of the rules. Happen
pport using both my own OBJ-C and on the iPhone using Aral's
X-Auth libs on GitHub.
isaiah
http://twitter.com/isaiah
On Jul 26, 2010, at 4:49 PM, Isaiah Carew wrote:
>
> Did you ever get to the bottom of this? I've been getting this same response
> from yFrog -- but all of the
Did you ever get to the bottom of this? I've been getting this same response
from yFrog -- but all of the other oAuth Echo supporting services seem to be
working just fine.
isaiah
http://twitter.com/isaiah
On Jul 20, 2010, at 4:21 PM, DWF wrote:
> Anyone else seeing this?
&g
OK, good to know. Just want to make sure it's not just me. Misery loves
company, I guess. :-P
isaiah
http://twitter.com/isaiah
On Jul 19, 2010, at 2:54 PM, Tim Davies wrote:
> Im getting the same isalah. Twitter are aware of the issue. its during
> handshake for creating new
The status page at: dev.twitter.com/status says things are all go -- but I'm
still getting 500s during token exchange.
Any updates?
isaiah
http://twitter.com/isaiah
On Jul 19, 2010, at 12:55 PM, Taylor Singletary wrote:
> Hi Isaiah,
>
> This is related to the same is
?
Is there a way to tell whether the problem is: twitter, my IP, my app, or my
accounts?
Is there something in the HTTP response tea leaves that can tell me more info?
Currently I'm getting:
Status = "500 Internal Server Error";
isaiah
http://twitter.com/isaiah
Great news. I'm crossing my fingers too.
isaiah
http://twitter.com/isaiah
On Jul 7, 2010, at 8:32 PM, Raffi Krikorian wrote:
> we are currently sitting at 100% - so 350 calls/hour on oauth, and 150
> calls/hour on basic auth. fingers crossed!
>
> On Wed, Jul 7, 2010 a
Does this mean a return to previous rate limits as well? Or are we
still getting the squeeze?
Isaiah
On Jul 7, 5:54 pm, themattharris wrote:
> Hey everyone,
>
> We've been working on the rate limit issue which has been affecting
> many of you and believe we now have it fi
John,
Do you measure the number of lockouts?
Or maybe a better question is: do you have metrics on how reducing rate limits
is impacting users?
isaiah
http://twitter.com/isaiah
On Jul 6, 2010, at 9:10 AM, John Kalucki wrote:
> These lockouts are almost certainly due to a performa
em dwarfed by this massive problem.
isaiah
http://twitter.com/isaiah
Hi John,
I appreciate the offer, and I'm excited about user steams. I attended your
talk about it at chirp.
But I'm afraid I don't have the resources to invest in experimental development.
When everything's settled and user-streams are a reality I'll joi
failures and changes combined our users are going to be
marching with pitchforks very and torches looking for heads to chop
very soon.
I'm not asking for any specific action here. Merely passing along the
anger that we see just in case you weren't aware of it.
Isaiah
uth
> >> tokens.
> >
> > and 3. Browserless environments. I'm pretty sure that was one of the initial
> > motivators way back when the crud was flying.
> >
>
> Yeah ... but I *like* having the browser involved.
>
> +1 !
>
It's so t
nt process.
isaiah
http://twitter.com/isaiah
On Apr 14, 2010, at 9:26 PM, John Kalucki wrote:
> I should have encouraged folks to understand the Streaming API first. You can
> read up on all the details here:
> http://apiwiki.twitter.com/Streaming-API-Documentation
>
> But, for a p
too. if
you'd like my thoughts on this i posted a nicer, more thought out article:
http://yourhead.tumblr.com/post/516626319/le-roi-est-mort-vive-le-roi
i'd be happy to continue to debate via email or at chirp (yes, i'm going, i'm a
glutton for punishment, shoot m
sorry for being cranky, but i just spent a year building a tweetie competitor.
you can't fault a guy for saying ouch while your knife is still sticking out of
his back, right?
isaiah
http://twitter.com/isaiah
On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote:
> I think it's great th
ath.
Good luck with that.
Anyone want a chirp ticket?
isaiah
http://twitter.com/isaiah
On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote:
> One more from me. People have been asking for specific details around
> Tweetie for Mac and I wanted to make sure we clearly message our plans
> as
It would be great if Twitter would clarify things online. I'm sure I'm not the
only one who thinks that it's time to cut losses and move on - starting with
Chirp.
Frankly I'm not sure I see much point in attending Chirp any more.
Isaiah
On Apr 9, 2010, at 8:26 P
pick as the winners on the other
platforms?
Isaiah
On Apr 9, 2010, at 7:25 PM, Tim Haines wrote:
> Dewald,
>
> I'm surprised that you failed to mention that Twitter can also advertise the
> heck out of it on Twitter.com and via tweets etc - millions for further
&g
ling, but i assure you it's not what I think at all.
you guys are whatever the opposite of a brick wall is.
i apologize, i must have a gruff tone. i'm not angry. in fact i enjoy the
back and forth that we have with the API team. but i'll see if i can't just
tone it down a notch. :-P
Isaiah
--
To unsubscribe, reply using "remove me" as the subject.
oints or new changes in a safe
way.
isaiah
http://twitter.com/isaiah
--
To unsubscribe, reply using "remove me" as the subject.
So will they be monotonically increasing? That seems to be the key
question. If they're not necessarily monotonic with respect to their
date, then it seems like it would be a pretty painful change.
Isaiah
To unsubscribe from this group, send email to
twitter-development
ads
I'd be pleased with any sort of feedback, about the code, about the app, or
just ways that it could be made more approachable for people new to the topic.
isaiah
http://twitter.com/isaiah/
http://twitter.com/kiwi-app/
Try passing in nil as the token. The access token request should be similar to
how you used to perform the request token request.
The best explanation (and they one that helped me) is from Steve Reynolds:
http://ke-we.net/7u
isaiah
http://twitter.com/isaiah
On Mar 1, 2010, at 1:26 PM
Several users are reporting missing tweets over the past 8 hours. The problem
exists even on twitter.com. One of my accounts is also affected.
Even though @kiwi_app and @isaiah follow many of the same people, the @isaiah
account is empty for the past 8 hours except for it's own tweets.
ss in your default token.
it seems to make sense to me now, it was just a leap that i didn't make on my
own.
i just thought i'd post this in case anyone else out there is stuck too.
when it's a bit more cleaned up, i'll post my results to github.
isaiah
http://twitter.com/
horized."
feel free to email for more techy details. i've got loads. ;-)
isaiah
http://twitter.com/isaiah
URL than others, or why they were
recently changed, or if/when we should change our apps, or if the old endpoints
are depreciated.
or more than likely, it probably does say all those things, i just missed it
and was hoping the list could help me locate the docs.
thanks,
isaiah
On Feb 22, 20
i'm bound to forget this in about an hour. is this old/new versioned/not
listed somewhere in the API docs?
On Feb 22, 2010, at 9:42 AM, Ryan Alford wrote:
> Yes, those are the ones I am talking about.
>
> Ryan
>
> On Mon, Feb 22, 2010 at 12:41 PM, Raffi Krikorian wrote:
> hi ryan.
>
> yup -
hi,
my name is isaiah ( @isaiah ). i'm a indie Mac/iPhone developer. my latest
creation is Kiwi, a Mac Twitter client: http://kiwi-app.net/
i do lots of other fun stuff too:
open source OAuth stuff: http://github.com/yourhead
website layout tools: http://yourhead.com/
i tried to f
so excited about xAuth. i think this is really going to change the landscape
in a big way.
can't wait to get going.
sent a message to a...@twitter.com -- that's all that's necessary to get going
right?
thanks again,
isaiah
On Feb 12, 2010, at 9:04 AM, tsmango wrote:
> Y
ke it easy. Get better man. We can wait.
isaiah
http://twitter.com/isaiah
On Feb 9, 2010, at 9:42 AM, Ryan Sarver wrote:
> Raffi, has walking pneumonia so we're giving him a few days slack time and
> we're afraid of what he would write while on meds :)
>
> On Tu
oh wow!
how do i get in on this sweet UX goodness?
is there a form for submitting bribes or is it in-person only?
isaiah
On Feb 3, 11:49 am, Raffi Krikorian wrote:
> it will be available publicly soon!
>
>
>
>
>
> On Wed, Feb 3, 2010 at 11:43 AM, Dewald Pretorius wrote:
Oh wow, oh wow, oh wow!
On Feb 3, 11:49 am, Raffi Krikorian wrote:
> it will be available publicly soon!
>
>
>
>
>
> On Wed, Feb 3, 2010 at 11:43 AM, Dewald Pretorius wrote:
> > Raffi,
>
> > Have you tried it? There is no OAuth flow. I.e., the user types in his
> > Twitter username and passwo
How so? What do you think will be the significance of chirp for desktop OAuth?
Was there an announcement that I missed?
isaiah
http://twitter.com/isaiah
On Feb 2, 2010, at 10:30 AM, M. Edward (Ed) Borasky wrote:
> Actually, we'll know the answers at Chirp or before. Chirp is the
>
ame?
We'll know the answers in June. It should be fun to watch and make for some
lively forum threads. Bring popcorn and stand clear of the flames. ;-)
isaiah
http://twitter.com/isaiah
nts will
be compromised within a year or so of implementing OAuth -- and will probably
result in a lot of user frustration. It seems like their will be ample
motivation and little to prevent them.
Only time will tell, you're free to come and laugh at me if it doesn't happen.
Bookmark this email, we'll check back in 18 months. ;-)
Isaiah
So, in simple language: Twitter's policy is that every user of every open
source client register as a new twitter application?
Or, have I misinterpreted something? And if so, could you explain further what
mean?
Thanks,
Isaiah
> what i would do is just make it clear to people
n who uses an app registers it themselves then Twitter no longer
has the ability to monitor the app as a whole, essentially crippling one of
OAuth's most compelling reasons for being.
isaiah
http://twitter.com/isaiah
On Jan 18, 2010, at 9:58 AM, ryan alford wrote:
> You are readi
So you're saying that each individual end-user of the open source app would
register with Twitter for separate Twitter Application credentials, add those
credentials to the app, and then recompile the application?
Or did I read that incorrectly?
Isaiah
YourHead Software
supp...@yourhea
acker) are not storing their Twitter
credentials without informing them..."
My personal feelings about the veracity of this statement aside, the tone is
pretty clear: you shouldn't do this.
isaiah
http://twitter.com/isaiah
On Jan 17, 2010, at 8:50 AM, eco_bach wrote:
>
> I&#
ssion
Just thought I'd post it to this discussion in case someone forgot.
isaiah
http://twitter.com/isaiah
On Jan 11, 2010, at 11:01 PM, Raffi Krikorian wrote:
> As it stands, developers who have relatively new desktop apps are
> penalized by having updates from their app say 'f
dying to start working on
them. i'm committed to releasing an open source solution to them as
soon as they come out.
i hope you're as excited as i am.
if it's unclear on exactly which changes i'm talking about. it's the
ones that you mentioned in this post:
http://
8db599f6ad98?hl=en
i'm not asking for anything new or different from what has already been
announced. i was just hoping for a bit more detail, that's all.
isaiah
On Dec 29, 2009, at 3:19 PM, Raffi Krikorian wrote:
> if your application has access to a web browser, then i would str
then, my app is limping along with basic auth without attribution.
isaiah
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 wrote:
and how 'bout that off topic question?
a non
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.
thanks,
isaiah
On Dec 29, 2009, at 1:06 PM,
different
conditions documented somewhere?
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 the
case.
Thanks,
Isai
This seems like a dramatic improvement to me. When will Twitter start rolling
out support for this, I'd like to be ready with something on github for this as
soon as it lands.
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.com
On Dec 10, 2009, at 5:22 AM,
Is there more info about this available. I'd love to know more about the "API
for browser-less apps" -- specifically:
1) Will this be appropriate for desktop clients?
2) When?
Thanks,
isaiah
http://twitter.com/isaiah
7;s important to remember this distinction when web-apps are also
being discussed. A web app is different because it does NOT run on
your machine, you can NOT shut it down, and other people will
definitely have access to the information stored there.
Isaiah
YourHead Software
eets the "as easy as basic auth" litmus test and
would level the playing field between those that must implement OAuth
today and those that are grandfathered in to basic auth.
Sounds good to me. Where do I sign up?
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.c
plement. There's a lot of open
source on web in a multitude of languages.
If you have manpower to throw around, please work on the UX first. ;-)
I'd be happy to contribute to any open source project that helps to
achieve this. Count me in.
Isaiah
Hi Ryan,
Thanks for taking the time. I really appreciate it. I'll be sure to
give my feedback.
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.com
On Oct 12, 2009, at 9:55 AM, Ryan Sarver wrote:
Isaiah,
We are definitely interested in hearing what ty
a bad idea, it sure would be nice
to get some official feedback about it.
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.com
On Oct 11, 2009, at 9:28 AM, Abraham Williams wrote:
Currently not really. Twitter might start enforcing correct
designation at some point thoug
x27;t a half-bad idea
either.
In case it wasn't already mentioned in this thread there are a couple
open source projects that implement oAuth solutions that behave in
exactly this way:
For iPhone: http://github.com/bengottlieb/Twitter-OAuth-iPhone/
For Mac OS X: http://github.com/yo
update from one functioning call to another
functioning call without users experiencing any downtime.
I understand that some changes might need to be rolled in quickly to
avert infrastructure disaster or to patch security holes, but with 2
weeks notice, I'm guessing that's not wha
her things that need
urlencoding), those seem OK too.
What am I missing?
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.com
On Jul 30, 2009, at 2:27 PM, jonat...@scribblelive wrote:
I may be the only one to be this stupid, but when I looked at my POST
request functi
flickr do it too, the
idiom is well understood. however for a desktop client this is a very
abnormal (hopefully just novile?) process -- so i think i would still
tend to disagree.
thanks again for posting.
Isaiah
YourHead Software
supp...@yourhead.com
http://www.yourhead.com
On Jul 29
my understanding,
than anything else. Right? Right?!?! ;-)
Thanks for hearing my devil's advocate argument. Don't feel compelled
to respond. I don't *need* answers, just curious, that's all.
Isaiah
however I'm not entirely sure
what corner cases might trigger the failures. If anyone has an idea
of what regressions to run, I'd appreciate any info. Thanks.
Isaiah
Thank you for your prompt reply Isaiah,
No worries. Glad to help out.
Thank you also for the offer of emailing you directly, but I think
your code is also precious for other newbie like me who want to know
more about this OAuth thing :)
It wasn't so easy to figure out a nice way
;ve considered adding the pin code, but it seemed to further
complicate an already challenging UI without adding any value.
If you have any other issues with the example code, please feel free
to email me directly. I'd be happy to help out.
Isaiah
YourHead Software
supp...@yourhead.com
http
yep, just me,
thanks,
isaiah
p.s. subject changed to protect the on-topic folks. @isaiah for
more. ;-)
On Jul 1, 2009, at 12:27 PM, Neil Ellis wrote:
On a completely separate note, your website is stunning, did you
design it yourself? If not may I ask who were your designers.
All
ripts, inline css, fluid width, etc.
Maybe it already exists and I'm doing something wrong. Feel free to
point me in the right direction too. ;-)
Isaiah
On Jul 1, 2009, at 7:50 AM, Matt Sanford wrote:
Hi Arnaud,
That option during application creation is really more trouble
Just curious if anyone knows if the new Birdfeed ipone app that's just
been released today uses OAuth 1.0a "Pin" flow, the other OAuth flow,
or basic auth. Anyone know?
Isaiah
it could brake apps using in-app-web-view until a new version can be
> shipped. In theory someone who never reinstalls OSes or applications
> could use an application for years with only performing the jump to
> browser dance once.
Adding a serious deficiency to the first-run experience when compared
to the currently entrenched players of any product is a sure fire way
to garantee failure.
I think the prudent choice would be to do basic auth and switch when
the entrenched players are forced to switch too. At least then it's
an even playing field.
Isaiah
69 matches
Mail list logo
