Thanks much!
On Thu, Dec 4, 2008 at 22:12, Kazuho Okui <[EMAIL PROTECTED]> wrote:
> I attached another example which is a result of curl. it contains a
> request/response headers and a JSON content.
>
> I hope this will help to find the issue.
>
> Thanks,
> Kazuho
>
> On Thu, Dec 4, 2008 at 1:21
No, just use the count (200) parameter if you want all tweets since
"that" id.
--
Swap
On Dec 4, 12:40 am, Trevor Turk <[EMAIL PROTECTED]> wrote:
> On Dec 3, 11:39 am, Swap <[EMAIL PROTECTED]> wrote:
>
> > There was a small change. They fixed a bug with since_id where it
> > would set it as 0 if
Well, that works then! Thank you.
On Dec 4, 4:43 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Actually, we're just pushing out changes today that excise suspended
> users from API responses. Sorry for the confusion there.
>
>
>
>
>
> On Thu, Dec 4, 2008 at 12:32, Greg Schoen <[EMAIL PROTECTED]>
On Dec 4, 8:32 pm, "Chad Etzel" <[EMAIL PROTECTED]> wrote:
> Not really an elegant solution/implementation, but I could imagine that the
> database query needed to the equivalent on the back-end servers would not
> exactly be trivial either.
Yeah.
I imagine the search functionality is actually do
You mean you want to convert Twitter's Timezone list to match PHP's
timezones? This would have to be done by a pre-generated list or array
that would have to be matched to and converted. It shouldn't be too
hard?
- James Hartig
I'll admit, I'm curious about this myself. Another example is authenticating to
pull a user's friends feed. With the exception of protected users, why not
allow that public information to be pulled out via the API?
-Original Message-
From: Amir Michail <[EMAIL PROTECTED]>
Date: Thu, 4 D
On Dec 4, 3:46 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Yup!
>
But why?
Is this done to encourage more people to sign up?
Amir
>
>
> On Thu, Dec 4, 2008 at 12:39, Chad Etzel <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Dec 4, 2008 at 3:30 PM, Amir Michail <[EMAIL PROTECTED]> wrote:
>
> >> On
Actually, we're just pushing out changes today that excise suspended
users from API responses. Sorry for the confusion there.
On Thu, Dec 4, 2008 at 12:32, Greg Schoen <[EMAIL PROTECTED]> wrote:
>
> Is it possible to poll the API for a user's suspended status?
>
> I am pulling up the show.xml fo
Is it possible to poll the API for a user's suspended status?
I am pulling up the show.xml for a suspended user, and nothing on that
page leads me to believe that the account has been suspended. The xml
document would have you believe that nothing is wrong with the
account, that everything is liv
I agree, this is a great change.
On Dec 3, 11:07 pm, "dean.j.robinson" <[EMAIL PROTECTED]>
wrote:
> "return the representation of the authenticated user"
>
> does that mean that the response will be the same as if we
> calledhttp://twitter.com/users/show/id.format for the authenticated user?
>
Yup!
On Thu, Dec 4, 2008 at 12:39, Chad Etzel <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, Dec 4, 2008 at 3:30 PM, Amir Michail <[EMAIL PROTECTED]> wrote:
>>
>> On Nov 21, 6:41 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
>> > Please see the documentation
>> > athttp://apiwiki.twitter.com/REST+API+Doc
On Thu, Dec 4, 2008 at 3:30 PM, Amir Michail <[EMAIL PROTECTED]> wrote:
>
> On Nov 21, 6:41 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> > Please see the documentation athttp://
> apiwiki.twitter.com/REST+API+Documentation. You need to
> > provide HTTP Basic Auth credentials when requesting thef
On Dec 4, 12:44 pm, Matthew <[EMAIL PROTECTED]> wrote:
> You could implement this in the following way.
>
> 1. get all the follows of "techcrunch"
> 2. search for the keyword you want, saying "from: username1 OR
> username2 OR ... usernameN"
Unfortunately that sort of query can be very slow even
Not to mention that the query for the search API is limited to 140
characters (or it was the last time I checked). So you'd need to split up
your query and then thread the results by timestamp afterward (if time is of
concern for your app...).
Not really an elegant solution/implementation, but I c
On Nov 21, 6:41 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Please see the documentation
> athttp://apiwiki.twitter.com/REST+API+Documentation. You need to
> provide HTTP Basic Auth credentials when requesting thefollowersof
> another user.
>
But why?
Amir
>
>
> On Fri, Nov 21, 2008 at 15:3
Yes, that's exactly what it means. Glad it helps!
On Wed, Dec 3, 2008 at 21:07, dean.j.robinson <[EMAIL PROTECTED]> wrote:
>
> "return the representation of the authenticated user"
>
> does that mean that the response will be the same as if we called
> http://twitter.com/users/show/id.format f
If you could please provide example request/response output that would
help us track this down. Apologies for the inconsistency.
On Wed, Dec 3, 2008 at 17:28, Kazuho Okui <[EMAIL PROTECTED]> wrote:
>
> Today, I suddenly received a JSON value which favorited value is null
> instead of bool.
>
> h
Yup, until some other under-the-hood stuff changes, we can't really
hand out a user's archive in a single request/response in a timely and
database-friendly fashion. You'll still have to page through to get a
user's full archive, but with effectively non-existent rate limits,
this should be much
Hi Alex,
Thanks for the updates - one of the things I noticed is that the
"archive" API method was marked as wontfix. I was wondering what this
means for the future of accessing our Twitter history?
Is this just something where we won't be able to export it in one
shot, but still have access to
You could implement this in the following way.
1. get all the follows of "techcrunch"
2. search for the keyword you want, saying "from: username1 OR
username2 OR ... usernameN"
an example
http://search.twitter.com/search?q=github+from%3Alebreeze+OR+matthewrudy
shows all the tweets about github
You've probably hit the rate limit. Check out the informative error
message returned in the response body.
On Thu, Dec 4, 2008 at 06:40, mattyp <[EMAIL PROTECTED]> wrote:
>
> Can anyone verify that the following works?
> http://twitter.com/friendships/create/bob.json?follow=true
>
> I just get a
We do limit the number of updates a client can send over a period time
to prevent spammers. That time period may change, and the number of
updates one can post is much higher than most uses would dictate, but
if you really need to be posting that frequently, please apply for
whitelisting to lift t
The main thing that's changing with the new release of the API is the
URL scheme. We're cleaning things up, moving things around, making
the whole thing more RESTful. I'll confer with @mzsanford and see
about sharing our proposed set of URLs/methods.
Generally, though, we're still the same serv
On Dec 4, 5:23 am, "dean.j.robinson" <[EMAIL PROTECTED]>
wrote:
> According to the api docs you can pass an email address to the user/
> show method, I would assume that if a user didn't exist you'd get back
> a 404, which should allow you to determine whether or not the user
> exists.
>
> eg: ht
Can anyone verify that the following works?
http://twitter.com/friendships/create/bob.json?follow=true
I just get a HTTP 400 Bad Request
Thanks.
In twitter_process() comment out
curl_setopt($ch, CURLOPT_NOBODY, 0);
curl_setopt($ch, CURLOPT_HEADER, 0);
Also, change
curl_setopt ($ch, CURLOPT_POST, true);
to
curl_setopt ($ch, CURLOPT_POST, 1);
There is a problem because you are sending (if !empty($post_data)) the
HTTP Method HEA
I am trying to find a map or association between the time_zone value
returned in the users/show response to PHP's Timezone constants
(http://www.php.net/manual/en/timezones.php).
Is such a mapping supplied by the Twitter API or some other 3rd party
API or PHP Class?
Thanks in advance for any hel
Today, I've increased the time interval to two minutes, and so far, I
think it's working without problems with posting.
I've just set the interval to 1 minute, do you think it will give me
posting problems?
On Dec 2, 10:13 pm, maximz2005 <[EMAIL PROTECTED]> wrote:
> So if I increased this time i
28 matches
Mail list logo
