Uploading the same file to Twitter twice in a row results in 2 unique
URLs. For example:
http://a3.twimg.com/profile_background_images/63273103/avatar-200.png
http://a3.twimg.com/profile_background_images/63273237/avatar-200.png
So after you upload the background image save the URL and either do
It seems like twitter.com handles favoriting and retweeting well so
there seems to be some discrepancy between what twitter.com uses and
the API.
+1
Retweets_by_others (statuses/retweeted_to_me) includes the retweets by you
and your friends. If you retweet a original status from
The profile background image URL of this user shows up in the API, but
it doesn't show up on their profile page. What’s happening?
profile page:
http://twitter.com/dirk100
API:
http://www.twitter.com/users/show.xml?screen_name=dirk100
background image URL in API:
All that aside, the other problem would be exposing your secret key.
I am sure you can imagine how terribly bad that can end up...
On Dec 30, 10:57 pm, Hari hariharanwebm...@gmail.com wrote:
Is it a case of same origin
policyhttp://en.wikipedia.org/wiki/Same_origin_policy
On Dec 10, 8:27
Hi,
I am using statuses/friends call to get the list of user's friend's
screen names. These screen names are stored by the system. I am
maintaining the last stored screen name, so that it can be used as
offset from which new screen names can be listed.For ex: today I
stored 250 screen names,
I'm just starting out on writing a simple C++ library that integrates
with the Twitter API. As this is in the early stages I don't really
want to be integrating with the live twitter environment -
1) I may be sending over a load of broken requests while I work out
that I'm doing
2) The status
Hey everyone,
I just released a tool for Mac OS X called OAuthery. It allows you to
manually obtain an access token using the PIN-based workflow. This is
especially useful if you're using OAuth in a script or a bot. You
enter your consumer key and consumer secret, and the system will
obtain a
No test version of twitter. The best way is to create a test account and
protect it's updates to keep it off search. Request account/ip white-listing
where necessary. You may get rate limited but it's good to understand your
limits you can work inside during testing (rate limits reset every hour).
It's been four weeks since I originally asked this question. Is there
any chance at all it will be answered in the near future?
The time it takes to get a simple straight answer is mind-boggling.
On Dec 22 2009, 11:14 am, Duane Roelands duane.roela...@gmail.com
wrote:
Hopefully, I haven't
I believe that this is a known issue which the Twitter team are working on.
There are messages in this group about the issue - a search should give you
some more info.
All the best,
Tom
On Thu, Dec 31, 2009 at 12:03 PM, srikanthsombha...@gmail.com
srikanthsombha...@gmail.com wrote:
Hi,
I
Hi all,
I was feeling a little clever after working on some Twitter API stuff
but then thought oh! I'd better think about Twitters rate
limiting...and then that's where my brain started to melt!
A few bits of info: my web app needs people to authenticate (OAUTH)
and, from then on, the app
We're talking about lawyers here Duane. Straight forward is not a
term that they understand.
On 1/1/2010 2:31 PM, Duane Roelands wrote:
It's been four weeks since I originally asked this question. Is there
any chance at all it will be answered in the near future?
The time it takes to get a
My experience with rate limiting shows that each authenticated request
is counted against that user's limit on your IP. So, you get 20,000
requests per IP, per user, per hour assuming all your requests are
authenticated. Any unauthenticated requests go towards the 20,000
request limit per IP, per
For the first use case, following many users' timelines, you should be
using the follow method on the Streaming API. Currently you cannot get
protected and low quality user statuses this way, but you can get the
vast majority of tweets this way. Until we support these corner cases,
you can fall
Hello,
I tend to use many test accounts while developing. When I hit a rate
limit I just switch.
There is a sandbox in the works from what twitter has been telling
us. So hopefully
that will make life a little easier for testing with the API.
Josh
http://code.google.com/p/twitter-api/issues/detail?id=1277
On Fri, Jan 1, 2010 at 16:02, Thomas Woolway tswool...@gmail.com wrote:
I believe that this is a known issue which the Twitter team are working on.
There are messages in this group about the issue - a search should give you
some more
'Retweet by others' includes both (this is seen in web not in api) i.e if
you retweet a friend's original retweet from 'Retweet by others' tab (in
web) it appears in both 'Retweets by Me' (statuses/retweeted_by_me) and
'Retweet by others' (in web). You can undo this retweet in both tabs.(you
17 matches
Mail list logo
