[twitter-dev] Re: Recent API changes and new fields
Hi Matt Zac Bowling > Is there a time line for the streaming API getting these changes? Information like retweet_count, followers_count and friends_count are very volatile and change all the time. would be nice receive this kind of notification when any of these fields are changed. but I guess you woudn't build something like this. Arian On 24 ago, 21:38, Matt Harris wrote: > Hey Zac, > > The Streaming API already has these fields included. > > Matt > > > > On Tue, Aug 24, 2010 at 9:38 AM, Zac Bowling 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 > > 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 the counts were turned off and have remained off. This is > >> because of some bugs we found in the way the value was calculated. > >> I'll let you know when we have this resolved. > > >> 2) Will thesefieldsshow up in the Search and Streaming API? > >> Thefieldsare already in the Streaming API but be aware the > >> 'retweeted' field is not meaningful here. This is because the streamed > >> status knows nothing of the connected user. > >> The search API does not include this information. > > >> 3) How do I know if the feature is turned off? > >> Tweets will contain a retweeted_count if available. If the service is > >> not enabled newer Tweets will likely be missing their retweeted_count. > >> The safest thing to do is code to handle missing values. If they are > >> present use them, if they are not, treat them the same as when the > >> field didn't exist. This way your code works when the retweeted_count > >> is both enabled and disabled. > > >> 4) When was the feature turned on? > >> The service was rolled out the week beginning Aug 16th > > >> Hope that answers your questions, > >> Matt > > >> On Sat, Aug 21, 2010 at 4:33 PM, Joe wrote: > >>> will we see this in both search and stream API? > > >>> On Aug 20, 6:45 pm, Matt Harris wrote: > >>>> Hey everyone, > > >>>> This week we rolled out a couple ofnewdatafieldsfor the status and user > >>>> objects. For a while it has been difficult for you to get the number of > >>>> lists a user is listed in, or the number of times a Tweet has been > >>>> retweeted. You were also finding it hard to know if the user had > >>>> retweeted > >>>> the status themselves or not. The feature requests you filed and the > >>>> messages on the developer mailing list showed this is a pain point for > >>>> many > >>>> of you as it uses up many of your hourly API requests. > > >>>> Thesefieldsare live now and many of you have already seen them in our API > >>>> responses. We intended to tell you about these changes before they were > >>>> live, and in the future for things like this we will, but this time > >>>> around > >>>> our system for doing that didn't work. The good news is we know what went > >>>> wrong and have made the necessary improvements needed to ensure you are > >>>> notified before the changes happen. > > >>>> The recent changes which have been made affect the user and status > >>>> objects. > >>>> In both cases we have addedfields: > > >>>> To the user object: > >>>> --- > > >>>> listed_count > >>>> represents the number of public lists a user is listed in. This field is > >>>> an > >>>> integer. As this is anewfield it is possible some users will not have a > >>>> listed_count value yet. > > >>>> follow_request_sent > >>>> representing whether the user you are authenticating as has requested to > >>>> follow the user you are viewing. This will be false unless the friendship > >>>> request is pending. The field is a boolean and will be true or false. > > >>>> To the status object: > >>>> - > >>>> retweet_count > >>>> represents the number of times a status has been retweeted using the > >>>> Twitter > >>>> retweet action. This field is an integer. There will not be a value for > &g
[twitter-dev] search api - since date format
hi guys, I have a question about search api about 'until' parameter to be more exactly according to documentation until is "Optional. Returns tweets generated before the given date. Date should be formatted as -MM- DD. example: http://search.twitter.com/search.json?until=2010-03-28"; I need to know if its possible to set datetime, for example http://search.twitter.com/search.json?until=2010-09-08-19:00"; or something like this. according to doc date should be formatted as -MM-DD, but I need inform time, if its possible what would be the string format in this case? is it possible? or how could I get a similar result? Arian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: search api - since date format
here is my problem I need to catch some tweets since yesterday 20pm until this morning 8am. the problem is that there is more than 1500 tweets that I need, and according to search api docs, I can get a max of roughly 1500 tweets per search query. [...] rpp The number of tweets to return per page, up to a max of 100. http://search.twitter.com/search.json?rpp=100 page The page number (starting at 1) to return, up to a max of roughly 1500 results (based on rpp * page). http://search.twitter.com/search.json?page=10 [...] from http://dev.twitter.com/doc/get/search i'm struggling to build a query where I can get my tweets since yesterday night. any idea? Arian On 9 set, 12:23, Taylor Singletary wrote: > Hi Arian, > > A date string really is the only valid format for this function. If you want > to cut the search off by certain times of day, you're best off > post-processing your results for that kind of resolution. > > Thanks, > Taylor > > > > On Thu, Sep 9, 2010 at 8:15 AM, arian wrote: > > hi guys, I have a question about search api > > about 'until' parameter to be more exactly > > > according to documentation until is "Optional. Returns tweets > > generated before the given date. Date should be formatted as -MM- > > DD. > > example:http://search.twitter.com/search.json?until=2010-03-28"; > > > I need to know if its possible to set datetime, for example > >http://search.twitter.com/search.json?until=2010-09-08-19:00"; or > > something like this. > > > according to doc date should be formatted as -MM-DD, but I need > > inform time, if its possible what would be the string format in this > > case? > > > is it possible? or how could I get a similar result? > > > Arian > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker: > >http://code.google.com/p/twitter-api/issues/list > > Change your membership to this group: > >http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] [search api] is it possible to search replies from a certain status_id?
hi guys, I need monitor replies from certain status. I would like to use search api, but according to search api doc it's impossible. I only ask you to know for sure. for example, I would like to be able ask for search api for replies from a status providing in_reply_to_status_id value. the only way I found is to ask for user timeline and check manually the in_reply_to_status_id attribute. is it the better way? tks in advance Arian
[twitter-dev] Re: is it possible to search replies from a certain status_id?
in fact tks tsmango Arian On 21 jul, 14:06, tsmango wrote: > Unfortunately, there isn't a single API method that allows this. > > From the FAQ:http://dev.twitter.com/pages/api_faq#replies > > Q: How do I get all replies to a particular status? > A: For now, there's not a great way to do this. We've heard the > requests, though, and we'll be providing a solution for it before too > long. > > On Jul 21, 8:15 am, arian wrote: > > > > > hi guys, > > I need monitor replies from certain status. > > I would like to use search api, but according to search api doc it's > > impossible. > > I only ask you to know for sure. > > > for example, I would like to be able ask for search api for replies > > from a status providing in_reply_to_status_id value. > > > the only way I found is to ask for user timeline and check manually > > the in_reply_to_status_id attribute. > > is it the better way? > > > tks in advance > > Arian
[twitter-dev] Re: Can I use the Twitter API to get tweets for a specific user and timeframe?
Unfortunately, no. see this thread http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a7802a981c2aedee/15f9705c14e7b96f?lnk=gst&q=arian#15f9705c14e7b96f Arian On 16 ago, 01:45, Ben H wrote: > I've been doing some research into using the Twitter API, and I'm not > sure if I'm understanding it correctly. I want to get tweets from a > specific user for a specific time-frame. From what I can tell, using > the search function to specify a date range doesn't work because only > the last 7 days are kept. I could just get the tweets and work out the > date range with JavaScript, but the documentation states the the max > you can get is 200 tweets, so if the tweets from the date range I want > aren't in the last 200 I can't do it. > > Is there anyway I can do this?
[twitter-dev] Re: Recent API changes and new fields
Status.retweet_count!!! this is perfect!!! this is exactly what I need. it makes my life easier. But, I'm testing it right now and I can't find a status where "retweet_count" is not blank. 1. There will not be a value for this field when the feature is turned off -- how should I know if the feature is turned off or not? 2. the Tweet was created before we added retweet_count support. -- when exactly this feature was enabled? I'm trying with fresh tweets but they are all blank yet. Arian On 20 ago, 19:45, Matt Harris wrote: > Hey everyone, > > This week we rolled out a couple of new data fields for the status and user > objects. For a while it has been difficult for you to get the number of > lists a user is listed in, or the number of times a Tweet has been > retweeted. You were also finding it hard to know if the user had retweeted > the status themselves or not. The feature requests you filed and the > messages on the developer mailing list showed this is a pain point for many > of you as it uses up many of your hourly API requests. > > These fields are live now and many of you have already seen them in our API > responses. We intended to tell you about these changes before they were > live, and in the future for things like this we will, but this time around > our system for doing that didn't work. The good news is we know what went > wrong and have made the necessary improvements needed to ensure you are > notified before the changes happen. > > The recent changes which have been made affect the user and status objects. > In both cases we have added fields: > > To the user object: > --- > > listed_count > represents the number of public lists a user is listed in. This field is an > integer. As this is a new field it is possible some users will not have a > listed_count value yet. > > follow_request_sent > representing whether the user you are authenticating as has requested to > follow the user you are viewing. This will be false unless the friendship > request is pending. The field is a boolean and will be true or false. > > To the status object: > - > retweet_count > represents the number of times a status has been retweeted using the Twitter > retweet action. This field is an integer. There will not be a value for this > field when the feature is turned off, or the Tweet was created before we > added retweet_count support. > > retweeted > represents whether the user you are authenticating as has retweeted this > status or not. The field is a boolean and can be true or false. > > Changes to existing methods > -- > users/show > When requesting data for suspended users the user/show used to return an > HTTP 404 status code - it now returns HTTP 403. > > This change is in response to number of users who were asking if there was a > way to know if a user they were getting data for had been deleted or was > instead suspended. The change means the API agrees with the twitter.com in > that we confirm a user exists, but that you may not see their information > because they are suspended. > > If you call /users/show on a suspended user the API response will include > the error message "User has been suspended." > > Please remember we sometimes turn features off to maintain site stability. > We recommend you always check a field exists before attempting to use it and > be prepared for the value to be empty. This will help ensure your code stays > stable if we have to turn features off. We'll also be adding this > information to the main API documentation soon. > > Best, > > Matt Harris > Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi Ryan.
I´m having the same problem with the statuses/update using the php
library provided by Twitter, name as : Twitter-async, as said eco_bach
i verified my signatures and i receive information back on verify
credentials (and no 'incorrect signature' error), it´s really rare
what it´s happening couse some times it works and some times apeear
when a do a ¨$connection->post('statuses/update', array('status' =>
$statusStr))¨ the misterious message ¨incorrect signatures¨ as
response. I dont know what to do, becouse i´m following all the stuffs
that are described on the Twitter-async API. It began to happen the
last Tuesday 26th.
My regards.
Arian
On 27 ene, 00:30, ryan alford wrote:
> It is still a POST, you just don't write the post data to the request. That
> post data is now in the query string where Twitter is expecting it.
>
> Ryan
>
> Sent from my DROID
>
> On Jan 26, 2010 4:32 PM, "eco_bach" wrote:
>
> Hi Ryan
> Changed to 'GET' and it seems I still get the Incorrect signature.
> error
>
> And the second time I try to update status, I also get 'This method
> requires a POST.' error.
