[twitter-dev] Re: Can't get followers ids from users with lots of followers
Provide a cursor to get back the results in 5000 user chunks. Read http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-friends%C2%A0ids for more details. On Apr 22, 11:18 pm, RTuosto wrote: > I get a twitter over capacity when I do something like this: > > http://api.twitter.com/1/followers/ids.xml?screen_name=britneyspears > > But if I do it with my own account which only has a few followers it > works as normal. > > How do I avoid this error? > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] users lookup - user missing
The userid for elliottng appears to be 4696. How did you get the 8467 value? ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 9:52 PM, stumm wrote: > I'm doing a call on users lookup and for some reason it's saying IDs > do not exist (for IDs I'd gotten from tweets that I got by doing a > search). For example when looking up the user elliottng (who from a > quick glance doesn't look like spam). The call I'm making is: > http://api.twitter.com/1/users/lookup.json?user_id=8467 > > Strangely if I do the call with the users screen name, it seems to > work. > http://api.twitter.com/1/users/lookup.json?screen_name=elliottng > > Why are these users not showing up when searched by user ID? > > Thanks, > --Christopher > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
[twitter-dev] users lookup - user missing
I'm doing a call on users lookup and for some reason it's saying IDs do not exist (for IDs I'd gotten from tweets that I got by doing a search). For example when looking up the user elliottng (who from a quick glance doesn't look like spam). The call I'm making is: http://api.twitter.com/1/users/lookup.json?user_id=8467 Strangely if I do the call with the users screen name, it seems to work. http://api.twitter.com/1/users/lookup.json?screen_name=elliottng Why are these users not showing up when searched by user ID? Thanks, --Christopher -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: 401 Unauthorized with oauth gem
I found out that my app switched from read-write to read only. I didn't get any email about that. Bummer. -Fabio. On Fri, Apr 23, 2010 at 12:17 AM, Spiceee wrote: > > Did anything change in the API (couldn't find anything in the API > changelog) that would make all new users who are associating their Twitter > acounts to my app get a 401 on status update? All accounts up to a few days > ago are still working, newer ones get 401 using absolutely the same codebase > and the oauth gem (Ruby) version 0.3.6. Kinda hard to debug. > > Cheers, > > -Fabio. > > -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Mad about lists and cursors... please help
This issue has been fixed. Let me know if it recurs, and I sincerely apologize for the delay Sent from mobile device On Apr 22, 2010, at 9:33 AM, Mark McBride wrote: Please stop bumping this thread. We're aware of the issue and its criticality, and are getting a fix out as soon as possible. ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 3:30 AM, fdelpozo wrote: Please fix this issue soon, We need it. On 20 abr, 17:16, Mark McBride wrote: It hasn't been deployed as far as I know, but it should be out this week. Sent from mobile device On Apr 20, 2010, at 4:38 AM, Zach wrote: I don't know if this fix for next_cursor always being zero has been deployed or not, but I'm still seeing this bug. A fix for this would be really awesome. On Apr 17, 12:04 pm, Mark McBride wrote: Yes. A fix has been identified, and should be deployed in a few days Sent from mobile device On Apr 17, 2010, at 7:08 AM, Zach wrote: It's 10 days later and next_cursor on http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-member ... is still always 0, even when the user is being followed by far more than 20lists. This is completely broken and prevents 3rd party apps from discovering allliststhat follow a given user. Has anyone at Twitter even looked into this? On Apr 7, 3:43 pm, Mark McBride wrote: Eugene, we're aware of the issue and will take a look at it today. ---Mark http://twitter.com/mccv On Wed, Apr 7, 2010 at 11:09 AM, eugene.man...@gmail.com < eugene.man...@gmail.com> wrote: I posted this issue to @twitterapi twice, but they ignored it. Dear API group, please address this question. Thank you! On Apr 6, 9:45 am, Spraycode wrote: Has anyone been able to solve this issue? This is still crippling us. Thanks! On Apr 2, 5:25 am, luisfigo wrote: Having the same problem... Triedhttp://api.twitter.com/1/avinashkaushik/lists/ memberships.xml and get 0 forcursor. This guy is followed by ton oflistsin fact Below is the snapshot of the end result I got... This is screwing up our app right now... . http://a1.twimg.com/profile_background_images/79104366/twitter_backgr ... false false false false false 3208 en false 0 0 On Apr 1, 6:00 pm, Diego Rin Martin wrote: I think it's a API bug, even in the twitter page the paginator doesn't work as expected, sometimes appears, sometines not, and when appears it makes in a random manner. i'm gettingcursor0 from API, using int or string representation, the bug is in the API that sends thecursor0 randomly. regards, diego. On Thu, Apr 1, 2010 at 2:38 AM, jmathai wrote: Are you sure you're using the string representation of the cursor instead of the int? The API'scursorexceeds PHP's max integer value (generally). jmathai ~ $ php -r '$x = json_decode (1); echo $x; echo "\n"; var_dump ($x===1); var_dump($x===1.111E+52);' 1.111E+52 bool(false) bool(true) jmathai ~ $ php -r '$x = 1; echo $x; echo "\n"; var_dump ($x===1); var_dump($x===1.111E+52);' 1.111E+52 bool(true) bool(false) On Mar 31, 2:03 am, Diego Rin Martín wrote: Hi there, this is my first post to this group, i'm a spanish developer dealing with twitter api surprises, excuse my poor english, i'will do my best to comunicate nicest. So, to the problem, I'm trying to retrieve thelistsfor a user, via list/membershipsget method, and passingcursoras parameter, I'm having got random results, I explain myself, sometimes I made a request (for user edans, that have a huge amount of pages to paginate) and I get one page, I passcursor-1 and I getcursor0, sometimes I get one page, I passcursor-1 i getcursor 1331431515904087602, then I pass it and I get 0, sometimes I get a random number of pages, but never, never, be able to retrieve the total amount of pages. I use php twitter-async classes to comunicate with API, I thought that it could be the cause of the problem, but using direct curl (via php5- curl extension) calls I'm having the same issues. Same using json or xml. I'm always getting 200 responses, so the call finish in a correct way. any clue? I'm turning mad. Thanks in advance. diego. -- To unsubscribe, reply using "remove me" as the subject.
[twitter-dev] Can't get followers ids from users with lots of followers
I get a twitter over capacity when I do something like this: http://api.twitter.com/1/followers/ids.xml?screen_name=britneyspears But if I do it with my own account which only has a few followers it works as normal. How do I avoid this error? -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Public Timeline Frozen
Taylor, I have a sample from my log. It's not very detailed, but at least you can see that it's happening at random times. I am waiting a full minute before hitting the timeline, so it's not that. Let me know your thoughts. 4/22/2010 7:22:21 PM~Duplicate Message ID: 12667336000 4/22/2010 7:28:16 PM~Duplicate Message ID: 12667634000 4/22/2010 7:29:18 PM~Duplicate Message ID: 12667683000 4/22/2010 7:37:20 PM~Duplicate Message ID: 12668102000 4/22/2010 7:41:17 PM~Duplicate Message ID: 12668312000 -Matt On Apr 21, 1:53 pm, mattarnold1977 wrote: > Taylor, > > That's odd then because I'm seeing duplicate status id messages in my > log. I'll have to dig deeper to see which ID is being repeated to > give you an example. > > -Matt > > On Apr 21, 10:45 am, Taylor Singletary > wrote: > > > > > It has not happened yet. > > > The most recent parts of the discussion are in this > > thread:http://groups.google.com/group/twitter-development-talk/browse_thread... > > > Thanks, > > Taylor > > > On Tue, Apr 20, 2010 at 6:20 PM, mattarnold1977 > > wrote: > > > > Taylor, > > > > I just remembered that you were planning to change the generation of > > > status ids. Has that already occurred? If so, where is the > > > documentation on that again? > > > > -Matt > > > > On Apr 20, 10:14 am, Taylor Singletary > > > wrote: > > > > Hi Matt, > > > > > I'm not able to see the issue at the moment -- can you provide some more > > > > details like examples of duplicate status ids? The public_timeline > > > endpoint > > > > is cached for 60 seconds, so it will remain stagnant if you're > > > > requesting > > > it > > > > more often than that. > > > > > Taylor Singletary > > > > Developer Advocate, Twitterhttp://twitter.com/episod > > > > > On Tue, Apr 20, 2010 at 4:44 AM, mattarnold1977 > > > > wrote: > > > > > > It looks like the public timeline api is reporting the same statuses > > > > > over-and-over again. This started sometime yesterday (4/19) and > > > > > continues today. Is anyone else experiencing this issue? > > > > > > Thanks, > > > > > Matt > > > > > > -- > > > > > Subscription settings: > > > > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: search.twitter.com/trends* is moving to api.twitter.com/1/trends*
Hi Taylor I also see that http://api.twitter.com/1/search.format also works, is this also going to be removed at the same time? Richard On Apr 22, 11:27 pm, Taylor Singletary wrote: > Hi Developers, > > In the interests of bringing more consistency to your Twitter developer > experience, you can *now* access the "trends" API endpoints at alternate, > versioned addresses under the api.twitter.com domain. > > In the past, you've been accessing trends resources at search.twitter.com: > http://search.twitter.com/trends.json > http://search.twitter.com/trends/current.json > http://search.twitter.com/trends/daily.json > http://search.twitter.com/trends/weekly.json > > But now you can access the corresponding endpoints with the same payloads > at: > http://api.twitter.com/1/trends.json > http://api.twitter.com/1/trends/current.json > http://api.twitter.com/1/trends/daily.json > http://api.twitter.com/1/trends/weekly.json > > *We'll be keeping the search.twitter.com endpoints available until on or > around July 1st, 2010. After that date, you should use the new versioned > endpoints exclusively.* > * > * > Documentation resources will be updated with these changes soon. > * > * > Thanks everyone! > * > * > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] search.twitter.com/trends* is moving to api.twitter.com/1/trends*
Hi Developers, In the interests of bringing more consistency to your Twitter developer experience, you can *now* access the "trends" API endpoints at alternate, versioned addresses under the api.twitter.com domain. In the past, you've been accessing trends resources at search.twitter.com: http://search.twitter.com/trends.json http://search.twitter.com/trends/current.json http://search.twitter.com/trends/daily.json http://search.twitter.com/trends/weekly.json But now you can access the corresponding endpoints with the same payloads at: http://api.twitter.com/1/trends.json http://api.twitter.com/1/trends/current.json http://api.twitter.com/1/trends/daily.json http://api.twitter.com/1/trends/weekly.json *We'll be keeping the search.twitter.com endpoints available until on or around July 1st, 2010. After that date, you should use the new versioned endpoints exclusively.* * * Documentation resources will be updated with these changes soon. * * Thanks everyone! * * Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] stream api query with both track and follow
Small correction: follow is full fidelity and will never be limited. Statuses delivered because of a match on track or locations will count against the same limit. ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 1:57 PM, Mark McBride wrote: > This is the correct interpretation. The track limiting is against the > total number of messages delivered to your stream, which means follow > + track + locations all count against the limit. > > ---Mark > > http://twitter.com/mccv > > > > On Thu, Apr 22, 2010 at 1:54 PM, Dima Brodsky wrote: >> Hi >> I have a question as to the behaviour when one specifies both a 'track' >> parameter and a 'follow' parameter. From my understanding from the wiki: >> >> statuses/filter >> >> Returns public statuses that match one or more filter predicates. At least >> one predicate parameter, follow, locations, or track must be specified. >> Multiple parameters may be specified which allows most clients to use a >> single connection to the Streaming API. Placing long parameters in the URL >> may cause the request to be rejected for excessive URL length. Use a POST >> request header parameter to avoid long URLs. >> >> Is that the parameters are treated as an 'or' clause and thus I would get >> everything, minus the usual limits, for a particular track predicate and >> everything for all the users I am following. Is this the correct >> interpretation. >> >> Also, if I was just following a track query and then I add a follow query, >> will the number of results in my track query go down because some amount is >> used up by the follow, or are the limits individually placed on track and on >> follow. >> >> Thanks! >> >> ttyl >> >> Dima >> > -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: users/lookup issues
thanks, works in the browser now, however the corrected oAuth call does not work and gives me a 401. Is there trick to getting this method to work with oAuth? I noticed someone else was having problems with it. As I said before every other api method call works except this one. for example this works in the browser but not via oauth - http://api.twitter.com/1/users/lookup.json?screen_name=JAIMEALGUERSUAR,rubarrichello,The_Real_JB,karunchandhok,realTimoGlock,lucasdigrassi,NickHeidfeld,NicoHulkenberg,H_Kovalainen,vitalypetrovru,nico_rosberg,BSenna,AussieGrit I am using EPITwitter so if anyone has come across this issue with that library or php before I would love some help to solve the issue if its not an api one. Kind Regards Darre On Apr 22, 9:36 pm, Taylor Singletary wrote: > Hi Ninjamonk, > > Slight error in the docs that I'll get fixed right now -- try this instead: > > http://api.twitter.com/1/users/lookup.json?screen_name=dougw,raffi > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > > > On Thu, Apr 22, 2010 at 1:33 PM, Ninjamonk wrote: > > Hi, I am using oauth and EPItwitter and I cannot get a decent response > > from users/lookup. I keep on getting "401 Unauthorized" when with the > > same instance I can get any other method to work fine. > > > I tried navigating in the browser to > > >http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=d... > > and that is giving me a 404 > > > I am not sure if I am fighting an api problem or an issue with > > EPITwitter. > > > Kind Regards > > > Darren > > > -- > > Subscription settings: > >http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] stream api query with both track and follow
This is the correct interpretation. The track limiting is against the total number of messages delivered to your stream, which means follow + track + locations all count against the limit. ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 1:54 PM, Dima Brodsky wrote: > Hi > I have a question as to the behaviour when one specifies both a 'track' > parameter and a 'follow' parameter. From my understanding from the wiki: > > statuses/filter > > Returns public statuses that match one or more filter predicates. At least > one predicate parameter, follow, locations, or track must be specified. > Multiple parameters may be specified which allows most clients to use a > single connection to the Streaming API. Placing long parameters in the URL > may cause the request to be rejected for excessive URL length. Use a POST > request header parameter to avoid long URLs. > > Is that the parameters are treated as an 'or' clause and thus I would get > everything, minus the usual limits, for a particular track predicate and > everything for all the users I am following. Is this the correct > interpretation. > > Also, if I was just following a track query and then I add a follow query, > will the number of results in my track query go down because some amount is > used up by the follow, or are the limits individually placed on track and on > follow. > > Thanks! > > ttyl > > Dima > -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] stream api query with both track and follow
Hi I have a question as to the behaviour when one specifies both a 'track' parameter and a 'follow' parameter. From my understanding from the wiki: statuses/filter Returns public statuses that match one or more filter predicates. At least one predicate parameter, follow, locations, or track must be specified. Multiple parameters may be specified which allows most clients to use a single connection to the Streaming API. Placing long parameters in the URL may cause the request to be rejected for excessive URL length. Use a POST request header parameter to avoid long URLs. Is that the parameters are treated as an 'or' clause and thus I would get everything, minus the usual limits, for a particular track predicate and everything for all the users I am following. Is this the correct interpretation. Also, if I was just following a track query and then I add a follow query, will the number of results in my track query go down because some amount is used up by the follow, or are the limits individually placed on track and on follow. Thanks! ttyl Dima -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Deleted status still in JSON, not in XML
Has anyone seen this behavior before? Is this a once in a lifetime
event? I (still) haven't found any mention of this anywhere.
Ricky
On Apr 20, 2:47 pm, Ricky wrote:
> I've had a bug submitted by a user of the Twitterizer .NET library,
> and it appears to be a possible bug with the Twitter API.
>
> After destroying a status, the /users/show/screen_name.json result
> still contained the destroyed status, while the /users/show/
> screen_name.xml results (correctly, I think) contains the previous
> status.
>
> Below is the example, both from the user "ronneylovely". The status
> "wow" has been deleted.
>
> Thanks in advance for any insight or attention you give,
> Ricky
>
> JSON (api.twitter.com/1/users/show/ronneylovely.json):
> {"favourites_count":1,"created_at":"Thu Apr 15 15:23:35 +
> 2010","profile_sidebar_fill_color":"e0ff92","description":null,"contributor
> s_enabled":false,"time_zone":null,"status":
> {"in_reply_to_status_id":null,"created_at":"Mon Apr 19 22:05:12 +
> 2010","in_reply_to_user_id":null,"truncated":false,"source":"web","favorite
> d":false,"id":
> 12478411850,"in_reply_to_screen_name":null,"text":"wow"},"following":false,
> "geo_enabled":false,"profile_sidebar_border_color":"87bc44","url":null,"ver
> ified":false,"profile_background_color":"9ae4e8","location":null,"profile_b
> ackground_image_url":"http://
> s.twimg.com/a/1271213136/images/themes/theme1/
> bg.png","profile_text_color":"00","followers_count":
> 0,"protected":false,"profile_image_url":"http://s.twimg.com/a/
> 1271213136/images/
> default_profile_3_normal.png","notifications":false,"profile_background_til
> e":false,"name":"ronneylovely","friends_count":
> 4,"profile_link_color":"ff","screen_name":"ronneylovely","id":
> 133348295,"lang":"en","statuses_count":2,"utc_offset":null}
>
> XML (api.twitter.com/1/users/show/ronneylovely.xml):
>
> 133348295
> ronneylovely
> ronneylovely
>
>
> http://s.twimg.com/a/1271725794/images/
> default_profile_3_normal.png
>
> false
> 0
> 9ae4e8
> 00
> ff
> e0ff92
> 87bc44
> 4
> Thu Apr 15 15:23:35 + 2010
> 1
>
>
> http://s.twimg.com/a/1271725794/images/
> themes/theme1/bg.png
> false
>
> false
> false
>
> 1
> en
> false
>
> Thu Apr 15 15:25:38 + 2010
> 12228846134
> testing this thing
> web
> false
>
>
> false
>
>
>
>
>
>
>
>
> --
> Subscription
> settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] users/lookup issues
Hi Ninjamonk, Slight error in the docs that I'll get fixed right now -- try this instead: http://api.twitter.com/1/users/lookup.json?screen_name=dougw,raffi Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 1:33 PM, Ninjamonk wrote: > Hi, I am using oauth and EPItwitter and I cannot get a decent response > from users/lookup. I keep on getting "401 Unauthorized" when with the > same instance I can get any other method to work fine. > > I tried navigating in the browser to > > http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=dougw,raffi > and that is giving me a 404 > > I am not sure if I am fighting an api problem or an issue with > EPITwitter. > > Kind Regards > > Darren > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
[twitter-dev] users/lookup issues
Hi, I am using oauth and EPItwitter and I cannot get a decent response from users/lookup. I keep on getting "401 Unauthorized" when with the same instance I can get any other method to work fine. I tried navigating in the browser to http://api.twitter.com/1/users/lookup.json?screen_names=screen_name=dougw,raffi and that is giving me a 404 I am not sure if I am fighting an api problem or an issue with EPITwitter. Kind Regards Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Stream API - determining access level
You'll receive an HTTP error code if you go to high. The current limits are documented in the wiki. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Apr 22, 2010 at 12:08 PM, Dima Brodsky wrote: > Hey, > Quick question, is there any programatic way to determine the access level > one has to the streaming api, in particular I want to find out my follow > limit for the status filter. > Thanks! > ttyl > Dima > -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Introduce yourself!
Hey all- My name is Clint, I'm a web and Cocoa developer from Missouri, and I've recently released my first beta app called Faces. Faces manages your profile pics across your various Twitter accounts. You can keep a collection of images for your profile pics and upload them to any of your Twitter accounts with a simple drag and drop. Here's a link to an announcement post which has a link to download the app for those interested: http://ctshryock.com/2010/04/introducting-facesapp-beta.html Faces is still a beta but largely complete. Any feedback is welcome at supp...@scary-robot.com Thanks +Clint -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Stream API - determining access level
Hey, Quick question, is there any programatic way to determine the access level one has to the streaming api, in particular I want to find out my follow limit for the status filter. Thanks! ttyl Dima -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Mad about lists and cursors... please help
Please stop bumping this thread. We're aware of the issue and its criticality, and are getting a fix out as soon as possible. ---Mark http://twitter.com/mccv On Thu, Apr 22, 2010 at 3:30 AM, fdelpozo wrote: > Please fix this issue soon, We need it. > > On 20 abr, 17:16, Mark McBride wrote: >> It hasn't been deployed as far as I know, but it should be out this >> week. >> >> Sent from mobile device >> >> On Apr 20, 2010, at 4:38 AM, Zach wrote: >> >> > I don't know if this fix for next_cursor always being zero has been >> > deployed or not, but I'm still seeing this bug. A fix for this would >> > be really awesome. >> >> > On Apr 17, 12:04 pm, Mark McBride wrote: >> >> Yes. A fix has been identified, and should be deployed in a few days >> >> >> Sent from mobile device >> >> >> On Apr 17, 2010, at 7:08 AM, Zach wrote: >> >> >>> It's 10 days later and next_cursor on >> >>>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-member >> >>> ... >> >>> is still always 0, even when the user is being followed by far more >> >>> than 20lists. This is completely broken and prevents 3rd party >> >>> apps >> >>> from discovering allliststhat follow a given user. >> >> >>> Has anyone at Twitter even looked into this? >> >> >>> On Apr 7, 3:43 pm, Mark McBride wrote: >> Eugene, we're aware of the issue and will take a look at it today. >> >> ---Mark >> >> http://twitter.com/mccv >> >> On Wed, Apr 7, 2010 at 11:09 AM, eugene.man...@gmail.com < >> >> eugene.man...@gmail.com> wrote: >> > I posted this issue to @twitterapi twice, but they ignored it. >> >> > Dear API group, please address this question. >> >> > Thank you! >> >> > On Apr 6, 9:45 am, Spraycode wrote: >> >> Has anyone been able to solve this issue? This is still >> >> crippling us. >> >> >> Thanks! >> >> >> On Apr 2, 5:25 am, luisfigo wrote: >> >> >>> Having the same problem... >> >> >>> Triedhttp://api.twitter.com/1/avinashkaushik/lists/ >> >>> memberships.xml >> >>> and get 0 forcursor. This guy is followed by ton oflistsin >> >>> fact >> >> >>> Below is the snapshot of the end result I got... This is >> >>> screwing up >> >>> our app right now... >> >> >>> . >> >>> >> >http://a1.twimg.com/profile_background_images/79104366/twitter_backgr >> > ... >> >>> >> >>> false >> >>> false >> >>> false >> >>> false >> >>> false >> >>> 3208 >> >>> en >> >>> false >> >>> >> >>> >> >>> >> >>> 0 >> >>> 0 >> >>> >> >> >>> On Apr 1, 6:00 pm, Diego Rin Martin wrote: >> >> I think it's a API bug, even in the twitter page the paginator >> > doesn't work >> as expected, sometimes >> appears, sometines not, and when appears it makes in a random >> manner. >> >> i'm gettingcursor0 from API, using int or string >> representation, >> > the bug >> is in the API that sends >> thecursor0 randomly. >> >> regards, diego. >> >> On Thu, Apr 1, 2010 at 2:38 AM, jmathai >> wrote: >> > Are you sure you're using the string representation of the >> > cursor >> > instead of the int? The API'scursorexceeds PHP's max integer >> > value >> > (generally). >> >> > jmathai ~ $ php -r '$x = >> > json_decode >> > (1); >> > echo $x; echo "\n"; >> >> > var_dump >> > ($x===1); >> > var_dump($x===1.111E+52);' >> > 1.111E+52 >> > bool(false) >> > bool(true) >> >> > jmathai ~ $ php -r '$x = >> > 1; echo >> > $x; >> > echo >> > "\n"; >> >> > var_dump >> > ($x===1); >> > var_dump($x===1.111E+52);' >> > 1.111E+52 >> > bool(true) >> > bool(false) >> >> > On Mar 31, 2:03 am, Diego Rin Martín > > m> wrote: >> >> Hi there, >> >> >> this is my first post to this group, i'm a spanish developer >> > dealing >> >> with twitter api surprises, excuse my poor english, i'will do >> >> my >> > best >> >> to comunicate nicest. >> >> >> So, to the problem, I'm trying to retrieve thelistsfor a >> >> user, >> > via >> >> list/membershipsget method, and passingcursoras parameter, >> >> I'm >> >> having got random results, I explain myself, sometimes I >> >> made a >> >> request (for user edans, that have a huge amount of pages to >> > paginate) >> >> and I get one page, I passcursor-1 and I getcursor0, >> >
Re: [twitter-dev] Count Total Number of Times a Term Has Been Searched
At this time there is no such API. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Thu, Apr 22, 2010 at 7:21 AM, Byron Cobb wrote: > I've previously found a post asking a similar question, but it was > dated September last year and had no answer. > > Is there any way to count the number (int) of times a search phrase > has been made through search.twitter.com or even the number of times a > term has been mentioned in a status. > > I don't want to return the tweets themselves, just the number. > > Regards, > Byron Cobb. > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
[twitter-dev] Count Total Number of Times a Term Has Been Searched
I've previously found a post asking a similar question, but it was dated September last year and had no answer. Is there any way to count the number (int) of times a search phrase has been made through search.twitter.com or even the number of times a term has been mentioned in a status. I don't want to return the tweets themselves, just the number. Regards, Byron Cobb. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Anybody else seeing "Unable to locate you. Try again" ??
On 04/18/2010 09:44 PM, M. Edward (Ed) Borasky wrote: > Well, it seems we have enough "does work" and "doesn't work" cases to > justify me taking some Wireshark traces and trying to debug my usage, > especially if Firefox 3.6.3 is still working on wireless in Windows and > failing in wireless on openSUSE 11.2. What should I be looking for in > the traces? > > On 04/18/2010 07:07 PM, Abraham Williams wrote: >> Chrome for OSX and Linux doesn't support Gears and never will so until >> Twitter supports the HTML5 Geo spec... >> >> 2010/4/18 Raffi Krikorian >> >>> i use safari + gears on OS X and it works for me. i think its only very >>> recent that chromium under OS X supports it. >>> >>> >>> On Sun, Apr 18, 2010 at 6:57 PM, Abraham Williams <4bra...@gmail.com>wrote: >>> Location used to work on the Windows beta of Chrome but stopped a week or two ago for me. It has never worked on my Mac though. Abraham On Sat, Apr 17, 2010 at 18:59, M. Edward (Ed) Borasky wrote: > On my Linux (openSUSE 11.2 with some of the advanced repositories) the > message "Unable to locate you. Try again" is showing up, and my tweets > aren't getting geotagged. Firefox 3.6.3, Google Chrome 5.0.375.9 dev and > Seamonkey 2.0.4 all do this, and it happens for both wired and wireless > connections. > > I'm pretty sure it's somewhere in the Linux stack beneath the browser - > the one time I booted one machine up in Windows, it worked in Firefox > 3.6.3 with a wireless connection. And it used to work on Linux with > Firefox. I haven't tried any other distros or rolling back to Firefox > 3.5. I might try a Lucid Lynx LiveCD just to see what happens, but I'd > rather get openSUSE to work, since I'm not planning to switch distros > just to get my tweets tagged. ;-) > > Is anyone else seeing this? The Firefox demo at > http://www.mozilla.com/en-US/firefox/geolocation/#geo-demo works! > Anything else I should be looking at? I can grab Wireshark traces but > don't know what to look for. > -- > M. Edward (Ed) Borasky > borasky-research.net/m-edward-ed-borasky > > "A mathematician is a device for turning coffee into theorems." ~ Paul > Erdős > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en > -- Abraham Williams | Developer for hire | http://abrah.am PoseurTech Labs | Projects | http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. >>> >>> >>> >>> -- >>> Raffi Krikorian >>> Twitter Platform Team >>> http://twitter.com/raffi >>> >> >> >> > > It seems the error message has changed. It used to say "Unable to locate you" and now says, "Unable to contact Twitter location service." So - there seems to be at least one request-response pair from me to Twitter I should be able to find in a trace. Twitter - is this something on your end? I can filter a Wireshark trace on IP addresses and send it to you. -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky "A mathematician is a device for turning coffee into theorems." ~ Paul Erdős
Re: [twitter-dev] Server-2-Server & User Streams
We truly and sincerely want support this use case as soon as we possibly can. To do so is a big win for everyone. If we can hack something together, even at considerable expense, we will do so. There isn't a clear path, as our options are limited due to authentication, privacy, capacity and logistics issues. We'll continue to game out various acceleration possibilities as we get user streams ready to launch over the next several months. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Thu, Apr 22, 2010 at 7:25 AM, Darren Bounds (Cliqset) wrote: > Hello! > > While it has been documented that the Twitter User Streams API is > designed predominantly for server-2-client interactions, I'm wondering > how Twitter feels about a service provider (like Cliqset) attempting > to behave within the bounds of a typical User Streams usage pattern. > > At a high level what I mean by 'behave' is that the Cliqset website > would exhibit the behavior of a desktop application, establishing > connectivity to the User Stream only when Twitter user was active > within the application. The only caveat would be the need for multiple > authenticated connections from 1 or more hosts. > > Is this something that would be frowned upon by Twitter or can we > explore this further? > > Thanks, > > Darren > > > -- > Subscription settings: > http://groups.google.com/group/twitter-development-talk/subscribe?hl=en >
[twitter-dev] Server-2-Server & User Streams
Hello! While it has been documented that the Twitter User Streams API is designed predominantly for server-2-client interactions, I'm wondering how Twitter feels about a service provider (like Cliqset) attempting to behave within the bounds of a typical User Streams usage pattern. At a high level what I mean by 'behave' is that the Cliqset website would exhibit the behavior of a desktop application, establishing connectivity to the User Stream only when Twitter user was active within the application. The only caveat would be the need for multiple authenticated connections from 1 or more hosts. Is this something that would be frowned upon by Twitter or can we explore this further? Thanks, Darren -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Mad about lists and cursors... please help
Please fix this issue soon, We need it. On 20 abr, 17:16, Mark McBride wrote: > It hasn't been deployed as far as I know, but it should be out this > week. > > Sent from mobile device > > On Apr 20, 2010, at 4:38 AM, Zach wrote: > > > I don't know if this fix for next_cursor always being zero has been > > deployed or not, but I'm still seeing this bug. A fix for this would > > be really awesome. > > > On Apr 17, 12:04 pm, Mark McBride wrote: > >> Yes. A fix has been identified, and should be deployed in a few days > > >> Sent from mobile device > > >> On Apr 17, 2010, at 7:08 AM, Zach wrote: > > >>> It's 10 days later and next_cursor on > >>>http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-GET-list-member > >>> ... > >>> is still always 0, even when the user is being followed by far more > >>> than 20lists. This is completely broken and prevents 3rd party > >>> apps > >>> from discovering allliststhat follow a given user. > > >>> Has anyone at Twitter even looked into this? > > >>> On Apr 7, 3:43 pm, Mark McBride wrote: > Eugene, we're aware of the issue and will take a look at it today. > > ---Mark > > http://twitter.com/mccv > > On Wed, Apr 7, 2010 at 11:09 AM, eugene.man...@gmail.com < > > eugene.man...@gmail.com> wrote: > > I posted this issue to @twitterapi twice, but they ignored it. > > > Dear API group, please address this question. > > > Thank you! > > > On Apr 6, 9:45 am, Spraycode wrote: > >> Has anyone been able to solve this issue? This is still > >> crippling us. > > >> Thanks! > > >> On Apr 2, 5:25 am, luisfigo wrote: > > >>> Having the same problem... > > >>> Triedhttp://api.twitter.com/1/avinashkaushik/lists/ > >>> memberships.xml > >>> and get 0 forcursor. This guy is followed by ton oflistsin > >>> fact > > >>> Below is the snapshot of the end result I got... This is > >>> screwing up > >>> our app right now... > > >>> . > >>> > >http://a1.twimg.com/profile_background_images/79104366/twitter_backgr > > ... > >>> > >>> false > >>> false > >>> false > >>> false > >>> false > >>> 3208 > >>> en > >>> false > >>> > >>> > >>> > >>> 0 > >>> 0 > >>> > > >>> On Apr 1, 6:00 pm, Diego Rin Martin wrote: > > I think it's a API bug, even in the twitter page the paginator > > doesn't work > as expected, sometimes > appears, sometines not, and when appears it makes in a random > manner. > > i'm gettingcursor0 from API, using int or string > representation, > > the bug > is in the API that sends > thecursor0 randomly. > > regards, diego. > > On Thu, Apr 1, 2010 at 2:38 AM, jmathai > wrote: > > Are you sure you're using the string representation of the > > cursor > > instead of the int? The API'scursorexceeds PHP's max integer > > value > > (generally). > > > jmathai ~ $ php -r '$x = > > json_decode > > (1); > > echo $x; echo "\n"; > > > var_dump > > ($x===1); > > var_dump($x===1.111E+52);' > > 1.111E+52 > > bool(false) > > bool(true) > > > jmathai ~ $ php -r '$x = > > 1; echo > > $x; > > echo > > "\n"; > > > var_dump > > ($x===1); > > var_dump($x===1.111E+52);' > > 1.111E+52 > > bool(true) > > bool(false) > > > On Mar 31, 2:03 am, Diego Rin Martín > m> wrote: > >> Hi there, > > >> this is my first post to this group, i'm a spanish developer > > dealing > >> with twitter api surprises, excuse my poor english, i'will do > >> my > > best > >> to comunicate nicest. > > >> So, to the problem, I'm trying to retrieve thelistsfor a > >> user, > > via > >> list/membershipsget method, and passingcursoras parameter, > >> I'm > >> having got random results, I explain myself, sometimes I > >> made a > >> request (for user edans, that have a huge amount of pages to > > paginate) > >> and I get one page, I passcursor-1 and I getcursor0, > > sometimes I > >> get one page, I passcursor-1 i getcursor > >> 1331431515904087602, > > then > >> I pass it and I get 0, sometimes I get a random number of > >> pages, > > but > >> never, never, be able to retrieve the total amount of pages. > > >> I use php twitter-async classes to comunicate with API, I > >>
[twitter-dev] Symbian^4 Social Networking Integration
Hi everyone, I'm James, I work at the Symbian Foundation. I thought you might be interested to hear to about an open source project to create a common social networking integration point for developers in Symbian^4, which will be finished in August this year. The "Social Mobile Framework" will ultimately create two things: - a plug-in interface, so that social networks can be plugged in as the data source for features in all the native apps. For example, a twitter plug-in could bring twitter updates to your home screen or contacts status feeds, a flickr plug-in could get the image gallery uploading and browsing your flickr collections, etc. - access to these plug-ins to all third party app developers from a common interface. Like I said, It's open source, so here are some resources. - Project Wiki: http://developer.symbian.org/wiki/index.php/Social_Mobile_Framework - Mailing List: http://developer.symbian.org/mailman/listinfo/socialmobilefw-dev - Mercurial: http://developer.symbian.org/oss/FCL/sf/incubator/socialmobilefw/ - If you run doxygen over the code, you'll get the interface specs. I'm looking into getting prebuilt docs on the project page asap. What do we need? - Developer opinions and review. If you look at mercurial repo, you'll see it's still early days and there's still time to shape the interfaces to make them do what you need for your apps. Join the mailing list, offer opinions, etc. - Code contribution and testing is more than welcome, probably more relevant later though. A team of developers at Sasken are contributing the framework to Symbian, lead by Chandradeep Gandhi. They're on the mailing list linked above. Thanks and all the best! James Aley. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Announcing Twurl: OAuth-enabled curl for the Twitter API
Hi, I installed RubyGems and did this sudo gem i twurl --sourcehttp://rubygems.org Then tried to use twurl but it gives a error : twurl: command not found Please tell me what am I missing ? Also, how do we use twurl with PHP ? cURL can be used with the PHP built in functions. Kartik On Apr 21, 12:13 am, Marcel Molina wrote: > We've announced that come June 2010, Basic Auth will no longer be supported > via the Twitter API. All authenticated requests will be moving to OAuth > (either version 1.0a or the emerging 2.0 spec). There are many benefits from > this change. Aside from the obvious security improvements, having all > requests be signed with OAuth gives us far better visibility into our > traffic and allows us many more tools for controlling and limiting abuse. > When we know and trust the origin of our traffic we can loosen the reigns a > lot and trust by default. We've already made a move in this direction by > automatically increasing rate limits for requests signed with OAuth made to > the new versioned api.twitter.com host. > > One of the often cited virtues of the Twitter API is its simplicity. All you > have to do to poke around at the API is curl, for > example,http://api.twitter.com/1/users/noradio.xmland you're off and running. > When > you require that OAuth be added to the mix, you risk losing the simplicity > and low barrier to entry that curl affords you. We want to preserve this > simplicity. So we've provided two tools to let you poke around at the API > without having to fuss with all the extraneous details of OAuth. For those > who want the ease of the web, we've already included an API console in our > new developer portal athttp://dev.twitter.com/console. And now today we're > glad to make available the Twurl command line utility as open source > software: > > http://github.com/marcel/twurl > > If you already have RubyGems (http://rubygems.org/), you can install it with > the gem command: > > sudo gem i twurl --sourcehttp://rubygems.org > > If you don't have RubyGems but you have Rake (http://rake.rubyforge.org/), > you can install it "from source". Check out the INSTALL file > (http://github.com/marcel/twurl/blob/master/INSTALL). > > Once you've got it installed, start off by checking out the README > (http://github.com/marcel/twurl/blob/master/README) (you can always get the > README by running 'twurl -T'): > > +---+ > | Twurl | > +---+ > > Twurl is like curl, but tailored specifically for the Twitter API. > It knows how to grant an access token to a client application for > a specified user and then sign all requests with that access token. > > It also provides other development and debugging conveniences such > as defining aliases for common requests, as well as support for > multiple access tokens to easily switch between different client > applications and Twitter accounts. > > +-+ > | Getting Started | > +-+ > > The first thing you have to do is register an OAuth application > to get a consumer key and secret. > > http://dev.twitter.com/apps/new > > When you have your consumer key and its secret you authorize > your Twitter account to make API requests with your consumer key > and secret. > > % twurl authorize --consumer-key the_key \ > --consumer-secret the_secret > > This will return an URL that you should open up in your browser. > Authenticate to Twitter, and then enter the returned PIN back into > the terminal. Assuming all that works well, you will beauthorized > to make requests with the API. Twurl will tell you as much. > > If your consumer application has xAuth enabled, then you can use > a variant of the above > > % twurl authorize -u username -p password \ > --consumer-key the_key \ > --consumer-secret the_secret > > And, again assuming your username, password, key and secret is > correct, will authorize you in one step. > > +-+ > | Making Requests | > +-+ > > The simplest request just requires that you specify the path you > want to request. > > % twurl /1/statuses/home_timeline.xml > > Similar to curl, a GET request is performed by default. > > You can implicitly perform a POST request by passing the -d option, > which specifies POST parameters. > > % twurl -d 'status=Testing twurl' /1/statuses/update.xml > > You can explicitly specify what request method to perform with > the -X (or --request-method) option. > > % twurl -X DELETE /1/statuses/destroy/123456.xml > > +--+ > | Creating aliases | > +--+ > > % twurl alias h /1/statuses/home_timeline.xml > > You can then use "h" in place of the full path. > > % twurl h > > Paths that require additional options such as request parameters for example > can > be used with aliases the same as with full explicit paths, just as you might > expect. > > % twurl alias tweet /1/statuses/update.xml > % twurl tweet -d "
