Sorry for a slightly gaming subject line, but I've just worked out
that the 'since_id' parameter is worthless in the mentions api call.
It may also be the case in every other API call - but let me explain.
The only time that I can think that you need to use the since_id param
is if you want to
Actually, I posted this and pretty much all of the code over here:
http://code.google.com/p/twitter-api/issues/detail?id=629colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
I just learned about such place, but yeah~.
Thanks!
On May 29, 9:54 am,
but thats not a real solution..
a setting shd be introduced that allows a user to enable/disable reverse
geocode for tweets...
On Thu, May 28, 2009 at 12:06 PM, Chris Latko ch...@latko.org wrote:
You could use Yahoo GeoPlanet to try to make sense of some of that
garbage:
Is it safe and appropriate to include consumer key and secret in OSS
desktop applications? That will make them publicly available on the
Internet.
This, of course, would allow anyone to copy the credentials and use
them in a different application. As long as Twitter tracks and deals
with abuse
Let's say I have a update with more then 140 characters.
Twitters webfrontend will cut the status and add ... which
points to
http://twitter.com/userename/status/xxx
where I can see the complete update.
Twittelator, ..., ... and my own client only show the three dots
without
and
Hey, I ended up posting all of this stuff here:
http://code.google.com/p/twitter-api/issues/detail?id=629colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
This page also has the code I have written
Alright, here's what I got sent:
1. The error
On Apr 28, 4:56 am, Mike Lewis mikelikes...@gmail.com wrote:
It doesn't allow you to sethttp://localhost/orhttp://127.0.0.1as
acallbackURL. This is rather frustrating because I don't want to have
to make a fake host and make all my developers make the same fake host
on their respective
Hey, I went ahead and installed the stuff you pointed me to and came
out with this:
I think I got a valid request token, navigate your www client to:
https://twitter.com/oauth/authorize?oauth_token=xeyrI4NFyMFIXXl0FnpBHpBDzhRxgep93JZ1SOGjHg
Once you finish authorizing, hit ENTER or INTERRUPT to
Hey there,
I was wondering what my options are for doing ID - name resolution. I
want to track changes to a user's social graph, and when changes
occur, resolve those follow(ing/er) IDs back to names.
I can easily make multiple GETs to users/show for small sets of
changes (and I'm caching
Nevermind, jmathai helped me out. Turns out I needed to add the $data
information to the signature string and also double encode the
spaces.
Thanks for your help!
On Apr 14, 10:52 pm, Dimebrain daniel.cre...@gmail.com wrote:
Hi Matt,
Thanks for replying. I had already tried the approach of
Wanted to add, I tried this with http (instead of https) and got the
same thing.
On May 30, 12:14 pm, AlfredN alfr...@gmail.com wrote:
Hey, I went ahead and installed the stuff you pointed me to and came
out with this:
I think I got a valid request token, navigate your www client
On 5/30/09 3:46 PM, David W wrote:
[... David asks about bulk resolving of Twitter user IDs to screen_name ...]
I don't know what the Twitter TOS says, but I've got a sizable cache of
(reasonably fresh) Twitter user data thanks to Twitter Karma.
Would it be a Twitter TOS violation for me
On May 30, 11:28 pm, Dossy Shiobara do...@panoptic.com wrote:
On 5/30/09 3:46 PM, David W wrote:
[... David asks about bulk resolving of Twitter user IDs to screen_name ...]
I don't know what the Twitter TOS says, but I've got a sizable cache of
(reasonably fresh) Twitter user data
Hey Dossy,
This sounds awesome, and I'd be very tempted, however I've come up
with a solution which should cater for any size of user account.
Right now when I periodically (~24 hours) note a set of changes to the
social graph, I create an entry in a (persistent) ring buffer
recording the new
I think current trending topics Twitter provided is for all the tweets
which means is for English tweets, we can't know what's hot in a
special language, so, it would be nice if Twitter API can provide
trending topics in languages. What do you think?
On 5/30/09 7:06 PM, David M. Wilson wrote:
In comment to your TOS question: Twitter as a company seem a whole lot
more liberal (and realistic) when it comes to their data. I think I
may have even read this somewhere semiofficial in the past. Profile
information itself is also available to the
We also have a sizable cache of this data (around 4 million users)
that we are already using in an API format internally at Twitturly. If
Twitter approves it, we can add it to our publicly available API.
Currently it allows conversion from both ID to username and username
to ID one at a time, and
17 matches
Mail list logo
