And as an addition to what D. Smith said: you're probably storing your
users' token and token_secret somewhere. So if you do have a tokens
are present, you know they have granted access before. Also, you can
check the message in the headers. Twitter sends a 401 when access has
been revoked, and
Hey everyone,
I've updated the Tweet Button docs today with information which I hope
will answer a number of your questions. In particular the example
about using a short URL with the parameter data-counturl should help
those of you whose counts are staying at 0.
Hi Guys
I'm also seeing this and forwarded on some markup for the
home_timeline to you, Matt.
It's easier to spot in XML, where Twitter are returning the following
between status objects:
nil-classes type=array/
e.g. (objects hidden using code folding)
status
status
nil-classes type=array/
Hi there,
I have got my IP and a/c white-listed, until now I was working on account
which was giving proper rate-limit, now I am trying to move from account
to IP, but IP just showing rate-limit 150 requests/hr. (just doubt: working
on sub domain of IP , will it be a cause? )
I just want to
I verified the same behavior with twurl
~ twurl -d screen_name=$NAME /1/friendships/destroy.json
-c.
On Mon, Aug 23, 2010 at 4:12 PM, funkyboy cesareroc...@gmail.com wrote:
Hello,
I am playing with the api.
When I unfollow somebody (friendships/destroy) the info returned is
incorrect,
Just a quick update to point any Twitter folks reading this thread to
issue #1823 on the bug tracker
http://code.google.com/p/twitter-api/issues/detail?id=1823
Cheers!
-N
On Aug 24, 10:42 am, Nik Fletcher nik.fletc...@gmail.com wrote:
Hi Guys
I'm also seeing this and forwarded on some
Hello,
Many users of some client apps are still in trouble because of null
results in home_timeline.
You can check usernames in trouble by searching famous twitter app
names.
Did you change the api specific? Or do you have any plan to fix this?
Thanks,
emmettoc
On 8月24日, 午後3:41, Matt Harris
I'll try to make this part clearer in the docs soon. I made the mistake of
not including guidelines that one's actual sent POST body should always
conform to application/x-www-form-urlencoded and that the values you pass
into an OAuth signature base string algorithm are to have already been
http://twitter.com/twitterapi/status/22002256380
-N
--
Nik Fletcher
@nikf
On Aug 24, 9:49 am, emmettoc creepyman2...@gmail.com wrote:
Hello,
Many users of some client apps are still in trouble because of null
results in home_timeline.
You can check usernames in trouble by searching famous
Basic auth is going away. Read about it here:
http://dev.twitter.com/pages/basic_auth_shutdown
After Aug 31, you won't be able to use your login and password to access the
API from any IP address.
Your IP-based whitelisting will continue to be valid for unauthenticated and
OAuth-authenticated
Hey everyone,
Thanks for your patience and for sharing the erroneous responses.
We're working on this and will have a fix rolled out soon.
Best,
Matt
On Tue, Aug 24, 2010 at 7:25 AM, Nik Fletcher nik.fletc...@gmail.com wrote:
http://twitter.com/twitterapi/status/22002256380
-N
--
Nik
Is it possible to make a widget for my website that will allow users
to follow me without leaving my website?
If so what method would I use.
E
Hi E,
Your best probably is the somewhat-frictionless Follow Button, part of the
@Anywhere arm of the platform. http://dev.twitter.com/anywhere/begin
It does involve a very smooth, frictionless pop-up authorization, but
requires very little coding and is less heavy than the standard
Hi Matt,
Thank you very much for the fast response.
I don't know how to post the screenshots on this group.
So I'll email you directly the images.
thanks.
On Aug 24, 2:45 am, Matt Harris thematthar...@twitter.com wrote:
Hi,
It sounds like the language is being detected successfully as some of
There is a known issue related to JSON timelines containing null elements,
which has crippled some clients. We'll have a fix for this deployed today as
soon as we can.
As for your mentions not showing on your web page -- can you share any
status ids that you think should be there that aren't?
Matt:
Not sure what you want me to pick up in the documentation. I must be
missing something.
When I read the page on daily POST limits [http://support.twitter.com/
forums/10711/entries/15364] I see:
quote
Current Twitter Limits
The current technical limits for accounts are:
Direct Messages:
Is there a time line for the streaming API getting these changes?
Zac Bowling
On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris thematthar...@twitter.com wrote:
Hey everyone,
Thanks for the questions. I'll try and answer them all in this message.
1) are the counts turned on?
This weekend
I would like to use the search API to pass in a bunch of usernames to
get tweets - basically getting tweets from a group of usernames rather
than manually trying to create a list everytime:
http://search.twitter.com/search.json?q=from:al3x+OR+from:twitterapiz+OR+from:mashable
Does anyone know
Hi Taylor,
I am missing all mentions since July 31. This has been the case for at
least a week, probably more.
On Aug 24, 8:17 am, Taylor Singletary taylorsinglet...@twitter.com
wrote:
There is a known issue related to JSON timelines containing null elements,
which has crippled some clients.
Hi Quy,
Queries are limited 140 URL encoded characters.
[1] http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
On Tue, Aug 24, 2010 at 10:00 AM, Quy quyten...@gmail.com wrote:
I would like to use the search API to pass in a bunch of usernames to
get tweets - basically getting
Matt, I've been using data-counturl from the start and still seeing 0
counts.
Here is the source for the button on
http://blog.snowballfactory.com/2010/08/15/tweet-button-with-shortening-for-wordpress/
which is showing 0 tweets:
a href=http://twitter.com/share; class=twitter-share-button data-
Hey Jimbo,
I can understand your confusion. Each of the APIs handles things
differently and their different approaches can make things like this
hard to work out. I've answered your questions inline.
A) Search API: Keyword Search
--
All retweets
Hey guys -
I'm curious as to know whether there's any problems with the search
API?
I'm curling from a PHP script, and it keeps timing out with 'couldn't
connect to host' errors when my URL is a search (eg:
http://search.twitter.com/search.atom?q=test). Interestingly, if I
curl either of the
There are no known issues with search and running your query works for me.
Hey Ben,
The Search API does not use authentication and is rate limited
differently to the 150 IP requests allowed on the REST API.
If you are rate limited on the Search API we would return an error
telling you rather than
Hi Jonathan,
The count we use is completely separate to search so no inference
should be drawn from there. As well as that the search index is only 5
or so days now so anything Tweeted before then won't be found.
When counting URLs we count the final destination of a shortURL so it
doesn't matter
Hey Zac,
The Streaming API already has these fields included.
Matt
On Tue, Aug 24, 2010 at 9:38 AM, Zac Bowling zbowl...@gmail.com wrote:
Is there a time line for the streaming API getting these changes?
Zac Bowling
On Mon, Aug 23, 2010 at 11:40 PM, Matt Harris thematthar...@twitter.com
Using oAuth I am making the following call:
POST /1/userid/3968155/subscribers.json
where userid is the user whose oAuth tokens are in use and 3968155 is
the id of the list i'm trying to subscribe to
Twitter returns a stock 404 result
I've even tried it with the slug id of the list, same
Try screen_name instead of userid. I'm not certain but it rings a bell. Not
that it shouldn't work with id, of course.
On Tue, Aug 24, 2010 at 8:49 PM, bear bea...@gmail.com wrote:
Using oAuth I am making the following call:
POST /1/userid/3968155/subscribers.json
where userid is the user
Hi Dave,
Thanks for the reply, and i'm sorry the documentation didn't answer
your question.
OAuth does have a rate limit of 350 REST API requests per hour which
applies mainly to GET requests. This API rate limit is separate to the
limits you found on the support pages. In fact, the limits on
I agree this isn't clear in the docs so i'll get onto updating them.
The structure for this URL is:
POST /1/:user/:list_id/subscribers.{format}
where:
:user is the user_id or screen_name of the user who owns the list
:list_id is the ID or slug for the list owned by :user. This isn't
necessarily
Ah, canonicalization. Thanks Matt.
As you probably know, those URL parameters (other than awesm=) are
standard Google Analytics tracking parameters. So, it's something that
should probably be handled better by the counter code. But at least we
now know the root cause.
Thanks,
-jonathan
On Aug
Hi Rushikesh,
OAuth replaces Basic Auth as the way to authenticate with the Twitter
API. If you application didn't require a users password before you
won't need it now. In this situation you will probably find this
document helpful:
http://dev.twitter.com/pages/oauth_single_token
If, on the
I have three iPhone apps that use OAuth to communicate with Twitter.
They have been working well for several months but recently when
trying to set-up authentication and exchange the various OAuth tokens
using Safari on the iPhone, Safari brings up a page from Twitter that
says:
Something is
Matt, thanks for the quick response.
After an evening of trying to figure out what's going on, it appears
to be working again. I guess the problem must have been on my side.
Thank you so much for replying so quickly though, and for the
explanation on rates and error messages!
Many thanks,
ben
Hi Kevin,
Thanks for raising this query. We have a fix on it's way out tonight
or tomorrow morning for this.
Also, whilst this isn't related to the issue you are experiencing I
recommended updating your URL to point to our API.
All requests for the API should be directed to
On Aug 24, 9:27 pm, Matt Harris thematthar...@twitter.com wrote:
I agree this isn't clear in the docs so i'll get onto updating them.
The structure for this URL is:
POST /1/:user/:list_id/subscribers.{format}
where:
:user is the user_id or screen_name of the user who owns the list
36 matches
Mail list logo
