[twitter-dev] Re: Suggestion: Ability to just search amongst a user's friends
Ideally this could all be done in the search query. Append who:everybody, who:friends, or who:self (I believe FriendFeed does something like this) to the query and it only searches the specified people. This way no API changes are needed. Only backend infrastructure to handle the new query terms. Jesse On Tue, Oct 27, 2009 at 11:02 PM, Shannon Clark shannon.cl...@gmail.comwrote: On a related point as a Twitter user with far more than 3200 tweets any chance that the following two features might also be considered: 1. Search your OWN tweets? (ideally all not just the most recent 3200 - both DM's tweets - possibly including DM's recieved as well as sent) 2. Retrieve, perhaps download, all of your own tweets in a standard, structured format ideally including the URL's for each tweet. And a third thought any possibility of adding an info feature to show backlinks? (akin to how bit.ly does this) both for a Twitter profile and for individual tweets? Perhaps also for search urls? Shannon Sent from my iPhone On Oct 27, 2009, at 9:02 PM, Chad Etzel c...@twitter.com wrote: This is something that we're considering internally. I'll bring it up again, though. -Chad On Tue, Oct 27, 2009 at 11:33 PM, Jesse Stay jesses...@gmail.com jesses...@gmail.com wrote: I have a project in which it would be tremendously easier if I could just specify a search to take place amongst a particular user's Twitter friends, instead of across the entire site. Is there a way to do this currently? If not, is this something the team could consider? I can make it work by comparing the full results to a list of friends, but that seems like unnecessary work. Thanks, Jesse
[twitter-dev] Does a 404 *always* mean a deleted tweet?
Hi there, I'd like to start deleting tweets that have been removed from twitter. I'm a little hesitant though, as I don't want to delete tweets accidentally that haven't really been deleted. I've noticed a couple of occasional odd things with false 404s when retrieving favorites, so I'm unsure whether I should trust the 404's from a user or tweet fetch. Does anyone know of any circumstances whereby a 404 might be returned for one of these calls when the tweet isn't actually deleted? Perhaps one scenario is when a user is temporarily suspended, and they're later unsuspended. Or - some kind of occasional error in Twitter's API. Any discussion appreciated, Tim.
[twitter-dev] Re: To find out ids directly that both in (follower/ids) and ( friends/ids ) ?
I don't think you can do this directly with the API. I've just used http://uk2.php.net/array_diff in the past On Oct 28, 3:38 am, Chi-Shun Chen andrewchen...@gmail.com wrote: Hi all. I had a question, take a example for show what i want: if someone's Followers/ids = A,B,C,D,E,G Friends/ids = D,F,G are there a API that can get result Xxxx/ids= D,G directly? Its easy to call two apis and calculate by myself when two list are small. but it become inconvenient when one list is huge,(such as 7000 ids + 10 ids ) thanks. Andrew
[twitter-dev] Automated Tweets
Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? Greg
[twitter-dev] Re: Automated Tweets
There was some talk recently about Twitter blocking consecutive tweets that are identical. With some of the reasoning that duplicate tweets are a violation of the terms of service. Paul 2009/10/28 Greg gregory.av...@gmail.com Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? Greg
[twitter-dev] Re: Automated Tweets
Twitter recently implemented logic to stop the ability of duplicate tweets. I can't remember if it was ever released what the time period is. On Oct 28, 2009, at 7:24 AM, Greg gregory.av...@gmail.com wrote: Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? Greg
[twitter-dev] Re: Automated Tweets
Hello, On Wed, Oct 28, 2009 at 6:23 PM, Greg gregory.av...@gmail.com wrote: Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? I also develop an application that sends tweets taken from plaintext. So far, I found experiences that twitter doesn't allow consecutive tweets that are identical. DWI
[twitter-dev] Re: No Cursor Data Returned
I think it could be the OAuth classs now because of a recent error but it does not seem to work when I put it in an array either. Furthermore this is the class that Twitter directly links to from the API Wiki under PHP examples... If it is this buggy (if in fact it does not work even as an array option) it really should not be posted there as it's a giant headache. From what I can see from the limited documentation the array() only holds post args for when you make an API call that requires POST fields and values but I will do some more testing with it. On Oct 27, 8:01 pm, Dave Briccetti da...@davebsoft.com wrote: I also recommend using Wireshark, tcpdump or the like to get an authoritative picture of what’s happening. And if there is indeed a bug, the output serves as clear proof.
[twitter-dev] Re: No Cursor Data Returned
I did try putting it in the array but only did one more quick test. I will have to try it again. I am pretty sure from the limited amount of documentation that the array holds post values for when you make a POST api call. If the OAuth class is this buggy (given that the array is the issue and I fix it later) this class really should not be posted on the Twitter API wiki as the main PHP OAuth example. More testing for now... On Oct 27, 8:01 pm, Dave Briccetti da...@davebsoft.com wrote: I also recommend using Wireshark, tcpdump or the like to get an authoritative picture of what’s happening. And if there is indeed a bug, the output serves as clear proof.
[twitter-dev] Re: Twitter Consumer Key issues
Just login to your own account an create an application... it takes like 30 seconds then just copy the 2 new key files into your settings or wherever they are defined. On Oct 27, 3:45 pm, chris7878 mitchell.ch...@gmail.com wrote: I hired a developer to create a twiter application for me. This developer did not complete the job, adn gave up about half way through. He was able to obtain a twitter consumer and secret key, and i now need to login to change a setting, however i do not know what twitter account or login was used to create the key. Is there anywhere or any way i can find this information? Any help is greatly appreciated mitchell.chris at gmail.com Thanks
[twitter-dev] user+password
and why do we need user name+password just for reading something from the public list? E.g. just read members id's, read statuses etc. Why it is password protected?
[twitter-dev] Re: user+password
You are not required. I just used this API method without credentials. http://twitter.com/statuses/user_timeline/[InsertScreenNameHere].xml No credentials needed. Some API methods do required you to be authenticated, but some do not. You can view the methods at http://apiwiki.twitter.com/Twitter-API-Documentation and it will tell you if you have to be authenticated to do the method. Ryan On Wed, Oct 28, 2009 at 3:17 PM, Abava dnam...@gmail.com wrote: and why do we need user name+password just for reading something from the public list? E.g. just read members id's, read statuses etc. Why it is password protected?
[twitter-dev] Re: Posting non-English Characters using OAuth
What encoding function to use for posting non-english characters ?? i am using urlencode but it is not posting non-english characters to twitter On Oct 27, 2:15 pm, Kalpesh kalp.meh...@gmail.com wrote: Hi Mageuzi, can you please shed more light what you exactly did? I am trying to post non-ascii status through api and it shows incorrect signature. ascii characters are posted successfully. On Sep 20, 1:55 am, Mageuzi mage...@gmail.com wrote: Thanks for the response, Brian :) After a bit more debugging and research, I found the problem. In hindsight it's obvious, but I was putting too much faith into how the characters were being encoded. That %65E5%672C%72AC was completely incorrect, and instead the individual bytes needed to be encoded and sent to twitter. Once I changed the oAuth code to do that, it's working flawlessly. Thanks again for your response! On Sep 18, 2:59 pm, Brian Smith br...@briansmith.org wrote: Mageuzi wrote: I'm sorry for posting a follow up so soon, but I spent another few hours trying to debug this again last night, and still without success. It seems to be encoding the characters properly (%65E5%672C %72AC in this case), and so I assume it is generating the signature properly. After all, it works perfectly fine with English characters. So any guidance would be much appreciated, I'm running out of things to check. Thank you again in advance. It probably isn't generating the signature properly. Try using a different library to post the same message and likely you will find that they are calculating the signature differently. Calculating bad signatures for non-ASCII characters is probably the most common bug in OAuth libraries, because the authors often test with ASCII characters but not non-ASCII characters. If the library you are using has a mechanism for you to get the signature base string, use that mechanism to retrieve it and post it here. Also, try using a different OAuth library. がんばってください! - Brian
[twitter-dev] Re: Posting non-English Characters using OAuth
What encoding function to use for posting non-english characters ?? i am using urlencode but it is not posting non-english characters to twitter Are you properly encoding the characters as UTF-8? That should occur before you URL-encode your payload. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- The gift of death metal does not smile on the good looking. -- S.B. #141 ---
[twitter-dev] Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Not getting direct message emails
For some reason we're no longer getting emails when a user sends though a direct message. This is happening on a number of accounts. Is anyone else having this problem?
[twitter-dev] Re: Not getting direct message emails
Im not as well. On Wed, Oct 28, 2009 at 9:42 AM, Dale Cook petesa...@gmail.com wrote: For some reason we're no longer getting emails when a user sends though a direct message. This is happening on a number of accounts. Is anyone else having this problem?
[twitter-dev] Re: Not getting direct message emails
This is a known issue being worked on presently. Thanks, -Chad On Wed, Oct 28, 2009 at 12:42 PM, Dale Cook petesa...@gmail.com wrote: For some reason we're no longer getting emails when a user sends though a direct message. This is happening on a number of accounts. Is anyone else having this problem?
[twitter-dev] Re: [twitter-api-announce] Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Marcel, Great changes. A couple of questions: - How long can a list description be? - A title can only be 15 chars - will that remain unchanged? - Will there be a little overlap where memberships and subscribers will still work while people migrate to followers/following? It would be awesome if there was a way to retrieve all member ids and a separate call for subscriber ids - cursored if necessary. Also, filed an edge case bug around list error messages a couple of days ago. http://code.google.com/p/twitter-api/issues/detail?id=1145sort=-openedcolspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component Cheers, Tim. On Oct 29, 9:00 am, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: OAuth in popup, does not work when auto close
On Oct 26, 9:34 pm, Chris Babcock cbabc...@kolonelpanic.org wrote:
I authenticate with twitter oauth using apopupfrom my site. When the
authentication is done, twitter redirects the user to my site again.
The user then has my site both in the original browser window, and in
thepopup.
One way of formulating your problem would be How can I avoid having two
windows open? The simplest answer would be, Don't open a second
window.
I want to close thepopupautomatically, so the user don't have to. I
do this with the following:
?php if (strlen($_GET['oauth_token']) 0) { echo scriptself.close
()/script; } ?
The problem is that when using the above code, the authentication
don't seem to work. When trying to tweet I get this:
/statuses/update.xml Could not authenticate you.
When I don't use the above code, and thereby force the user to close
thepopupmanually if he don't want it open, everything works fine.
Can someone explain this to me, and help with how I can auto close the
popupwithout messing with the authentication?
PHP is not my language of choice, but that looks like a scoping issue.
When you close the window with JavaScript, the authentication data you
obtained is lost when the window containing it is closed. You need to
persist the data whatever that means for your application - save a
cookie, submit data or (Ugh!) set a global - before you close the
window
Chris Babcock
Thanks for your tips Chris.
The thing is that the session variables are saved. I'm using Abrahams
oauth script (http://twitter.abrah.am/) and when I check against the
$_SESSION['oauth_state'], it tells me I'm still logged in (I have
connected the visibility of the post to twitter form to this
variable, which I only see when I'm logged in, and it works as
intended).
An addition to the previous description. When I don't use the script,
but close the popup manually, I can still post to twitter in chrome
and firefox. I can however not post in internet explorer, there I get
the message /statuses/update.xml Could not authenticate you. In all
three browsers $_SESSION['oauth_state'] indicate that I'm in fact are
logged in.
What can be different in this scenario between using chrome/firefox or
ie?
Thanks
[twitter-dev] Re: [twitter-api-announce] Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
+1 On 10/28/09 1:11 PM, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Post being flagged as a duplicate (when it is not)
Hello Folks, Not really sure what’s going on here. Below you will find what I am sending and what is coming back from the Twitter API. You can see that what is being sent doesn’t even come close to what is up there now. Am I missing something here? What am I doing wrong? Why is this completely different sting not posting? Sending method=post url=http://twitter.com/statuses/update.xml?status=Great%20Job%20for %20OAS%20TEST%20ONLY%20in%20California%2DAnaheim%2FHuntington%20Beach %2E%20http%3A%2F%2Flocalhost%2FAssignmentReady%2Findex%2Ecfm%3ForderID %3D2315510%26category%3DAllied%5FTravel%26ts%3D102809140819%20or %20800%2E469%2E5314 Result (from Twitter API) ?xml version=1.0 encoding=UTF-8? status created_atWed Oct 28 19:51:30 + 2009/created_at id5238791820/id textwhat/text sourceweb/source truncatedfalse/truncated in_reply_to_status_id/in_reply_to_status_id in_reply_to_user_id/ in_reply_to_user_id favoritedfalse/favorited in_reply_to_screen_name/in_reply_to_screen_name user id57127952/id nameLarp Master Flash/name screen_nameLarpMasterFlash/screen_name location/location description/description profile_image_urlhttp://s.twimg.com/a/ 1256674706/images/default_profile_0_normal.png/profile_image_url url/url protectedfalse/protected followers_count4/ followers_count profile_background_color9ae4e8/ profile_background_color profile_text_color00/ profile_text_color profile_link_colorff/profile_link_color profile_sidebar_fill_colore0ff92/profile_sidebar_fill_color profile_sidebar_border_color87bc44/profile_sidebar_border_color friends_count0/friends_count created_atWed Jul 15 20:31:16 + 2009/created_at favourites_count0/favourites_count utc_offset/ utc_offset time_zone/time_zone profile_background_image_urlhttp://s.twimg.com/a/1256674706/images/ themes/theme1/bg.png/profile_background_image_url profile_background_tilefalse/profile_background_tile statuses_count34/statuses_count notificationsfalse/ notifications geo_enabledfalse/geo_enabled verifiedfalse/ verified followingfalse/following /user geo/ /status Thanks for the input.
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Answers inline: On Wed, Oct 28, 2009 at 1:14 PM, Tim Haines tmhai...@gmail.com wrote: Marcel, Great changes. A couple of questions: - How long can a list description be? 160 :-) - A title can only be 15 chars - will that remain unchanged? Unchanged. - Will there be a little overlap where memberships and subscribers will still work while people migrate to followers/following? Yeah. There will be overlap for some period of time for those who might need to transition. It would be awesome if there was a way to retrieve all member ids and a separate call for subscriber ids - cursored if necessary. Right, I'll add that to the list of things to consider :-) Also, filed an edge case bug around list error messages a couple of days ago. http://code.google.com/p/twitter-api/issues/detail?id=1145sort=-openedcolspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component Thanks. Cheers, Tim. On Oct 29, 9:00 am, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
+1 to this Any news on when the rest of us devs can get access to this to work on our apps? On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Real soon now. We appreciate everyone's patience while we gradually ramp up traffic to lists to ensure we've got all our ducks in a row. On Wed, Oct 28, 2009 at 2:53 PM, Rich rhyl...@gmail.com wrote: +1 to this Any news on when the rest of us devs can get access to this to work on our apps? On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] statuses/friends not returning everything
Hi, When I'm making a call to http://twitter.com/statuses/friends/username.xml the resulting XML only contains 2 user statuses... but, the user has 55 friends. Why is the API not returning all of the data? I have verified that the people being followed aren't protected, and their status shows up on the web.
[twitter-dev] Re: new statuses not showing in statuses/friends call (only after long delay)
I'm having the same issue... but mine is even for users who have public accounts. I'm following 55 users, and only getting 2 results back with an authenticated API call. On Oct 21, 9:36 am, Frank Mertz fm4...@googlemail.com wrote: Dear all, recently I experience long delays (several hours) until a new status offriendsappears in the response of a statuses/friendscall. The users/show call for thesefriendsalready delivers the new tweet. This behavior can be observed for a large number of users, however, only forfriendswith protected status. Forfriendswith public statuses, these are always shown directly in the response. Even more strangely, sometimes statuses/friendsalready delivers the new status in the JSON response, but not in the XML response, or vice versa. I filed an issue on this behavior several days ago (http:// code.google.com/p/twitter-api/issues/detail?id=1121) and would be interested if others are having problems with this as well. Also, any information on when this might be fixed would be highly appreciated. Thank you very much and kind regards, Frank
[twitter-dev] php to json character handling
Hello, We are working on a service dealing with a high volume of tweets. We are seeing crazy things coming through in tweets and are running into recurring issues when creating large JSON strings to pass to our parser. I am curious if anyone can share approach or methodology on how they are creating valid JSON via PHP. - We are storing the tweets as they are first in a DB - doing some processing - sending them back to the UI in various forms, via jQuery ajax calls ($.getJSON). 99% of the time, our server side encoding works great, but some tweets are just bizarre and valid JSON fails. Any advice helps. Cheers Peter
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
How does one keep a list up to date for a client without the concept of since_id, like we have for the timeline methods? I look at a lists as just a different timeline (granted one filtered to specific users), but that is how I would expect to view them in a client. From my understanding of cursors, on each request we have to start at -1 (to start paging) and page until we find an id that we already have locally. While this will work, it has a high probability of always over requesting data.. So if I have a list with two people in it, and they only tweet once a week, when I poll for updates of this list (say every 30min) the data is going to be the same most of the time(last 100 messages that these two people post). This seems like a waste of bandwidth for Twitter and us.. Some may argue that bandwidth is cheap, but it really is not on mobile devices. Some carriers charge per kb, but even on unlimited plans every byte transferred translates to additional battery drain.. Is there some concept of the cursor that I am not understanding that will allow us to also filter based on something like since_id? So we want to get messages newer than we already have and notify the user that the list has something new to display. Thanks to anyone who can clarify if I am misunderstanding something. --Naveen On Oct 28, 6:14 pm, Marcel Molina mar...@twitter.com wrote: Real soon now. We appreciate everyone's patience while we gradually ramp up traffic to lists to ensure we've got all our ducks in a row. On Wed, Oct 28, 2009 at 2:53 PM, Rich rhyl...@gmail.com wrote: +1 to this Any news on when the rest of us devs can get access to this to work on our apps? On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
The cursors are for lists of lists and lists of users followed by/following lists. The statuses timeline for a given list takes all the same options you'd expect to manage status timelines. On Wed, Oct 28, 2009 at 5:43 PM, Naveen knig...@gmail.com wrote: How does one keep a list up to date for a client without the concept of since_id, like we have for the timeline methods? I look at a lists as just a different timeline (granted one filtered to specific users), but that is how I would expect to view them in a client. From my understanding of cursors, on each request we have to start at -1 (to start paging) and page until we find an id that we already have locally. While this will work, it has a high probability of always over requesting data.. So if I have a list with two people in it, and they only tweet once a week, when I poll for updates of this list (say every 30min) the data is going to be the same most of the time(last 100 messages that these two people post). This seems like a waste of bandwidth for Twitter and us.. Some may argue that bandwidth is cheap, but it really is not on mobile devices. Some carriers charge per kb, but even on unlimited plans every byte transferred translates to additional battery drain.. Is there some concept of the cursor that I am not understanding that will allow us to also filter based on something like since_id? So we want to get messages newer than we already have and notify the user that the list has something new to display. Thanks to anyone who can clarify if I am misunderstanding something. --Naveen On Oct 28, 6:14 pm, Marcel Molina mar...@twitter.com wrote: Real soon now. We appreciate everyone's patience while we gradually ramp up traffic to lists to ensure we've got all our ducks in a row. On Wed, Oct 28, 2009 at 2:53 PM, Rich rhyl...@gmail.com wrote: +1 to this Any news on when the rest of us devs can get access to this to work on our apps? On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: Updates to the List API (list descriptions, cursoring lists of lists, finding by list id rather than slug more consistent names)
Thanks for the quick response. I guess I was confused. On Oct 28, 2009, at 8:53 PM, Marcel Molina wrote: The cursors are for lists of lists and lists of users followed by/following lists. The statuses timeline for a given list takes all the same options you'd expect to manage status timelines. On Wed, Oct 28, 2009 at 5:43 PM, Naveen knig...@gmail.com wrote: How does one keep a list up to date for a client without the concept of since_id, like we have for the timeline methods? I look at a lists as just a different timeline (granted one filtered to specific users), but that is how I would expect to view them in a client. From my understanding of cursors, on each request we have to start at -1 (to start paging) and page until we find an id that we already have locally. While this will work, it has a high probability of always over requesting data.. So if I have a list with two people in it, and they only tweet once a week, when I poll for updates of this list (say every 30min) the data is going to be the same most of the time(last 100 messages that these two people post). This seems like a waste of bandwidth for Twitter and us.. Some may argue that bandwidth is cheap, but it really is not on mobile devices. Some carriers charge per kb, but even on unlimited plans every byte transferred translates to additional battery drain.. Is there some concept of the cursor that I am not understanding that will allow us to also filter based on something like since_id? So we want to get messages newer than we already have and notify the user that the list has something new to display. Thanks to anyone who can clarify if I am misunderstanding something. --Naveen On Oct 28, 6:14 pm, Marcel Molina mar...@twitter.com wrote: Real soon now. We appreciate everyone's patience while we gradually ramp up traffic to lists to ensure we've got all our ducks in a row. On Wed, Oct 28, 2009 at 2:53 PM, Rich rhyl...@gmail.com wrote: +1 to this Any news on when the rest of us devs can get access to this to work on our apps? On Oct 28, 8:11 pm, Jesse Stay jesses...@gmail.com wrote: Maybe a little more appropriate to post this to a private list (no pun intended) for beta users? I admit I feel a little jealous every time I see one of these updates, unless there's some way to get into the beta. Thanks, Jesse On Wed, Oct 28, 2009 at 2:00 PM, Marcel Molina mar...@twitter.com wrote: Two additions and two changes to the List API will be deployed in the next few days: * List descriptions We're adding a description to every list. You'll be able to specify a description when you create or update a list and the description will be included in the payload. * Cursoring through lists of lists All resources that return a list of lists will include next and previous cursors and will accept a :cursor parameter. * Finding by list id rather than slug When you change the name of a list, the slug will be updated to reflect that change. That means using the slug in the url for resources to operate on lists requires the onerous task of validating that the slug for the list you are about to do something with hasn't been updated since the last time you stored its slug. What a nightmare :-) Every list also has an id. This value won't change. We'll be changing the API to replace all instances of a list slug in urls to be list ids instead. * Consistent names The terminology we've used thus far for people you follow with a list is members. The terminology for people who are following a list is subscribers. We're going to mirror the terminology used for users and change it to followers and following respectively. So: /:user/lists/:list_id/memberships becomes /:user/lists/:list_id/ followers /:user/lists/:list_id/subscribers becomes /:user/lists/:list_id/ following As we deploy these changes we'll send out a heads up on the dev list and @twitterapi. -- Marcel Molina Twitter Platform Team http://twitter.com/noradio -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio -- Marcel Molina Twitter Platform Team http://twitter.com/noradio
[twitter-dev] Re: php to json character handling
I'm doing the same thing - communicating data back to the UI via AJAX and JSON. Haven't noticed problems but I'm not using the PHP json_encode functions. Where you able to determine whether it was JQuery or PHP? Through your logging facility (e.g log4PHP and the JQuery debug console) see at what point the JSON data is corrupted. Using log4PHP, I dump all inputs outputs to the database during development. You can check this information on your failures to help troubleshoot. For AJAX, 'm using Dojo which has a console for debugging. But I'm sure jQuery has similar debugging facility. Leon On Oct 28, 5:28 pm, Peter Denton petermden...@gmail.com wrote: Hello, We are working on a service dealing with a high volume of tweets. We are seeing crazy things coming through in tweets and are running into recurring issues when creating large JSON strings to pass to our parser. I am curious if anyone can share approach or methodology on how they are creating valid JSON via PHP. - We are storing the tweets as they are first in a DB - doing some processing - sending them back to the UI in various forms, via jQuery ajax calls ($.getJSON). 99% of the time, our server side encoding works great, but some tweets are just bizarre and valid JSON fails. Any advice helps. Cheers Peter
[twitter-dev] Re: To find out ids directly that both in (follower/ids) and ( friends/ids ) ?
Hi Sam, What make it inconvenient is due to that: The api of (follower/ids) can only return 5000 ids one time. when two lists are(5001 ids) + (100 ids), Its not just 1+1 times. We have to call these APIs 2+1 times and handle cursor. (I not sure is cursor-problem easy or hard.I dont touch it yet). It will nice if Twitter.com will provide this API in the future. It may called CircleRelationship/ids or some other name. Andrew On 10月28日, 下午6時12分, Sam Street sam...@gmail.com wrote: I don't think you can do this directly with the API. I've just usedhttp://uk2.php.net/array_diffin the past On Oct 28, 3:38 am, Chi-Shun Chen andrewchen...@gmail.com wrote: Hi all. I had a question, take a example for show what i want: if someone's Followers/ids = A,B,C,D,E,G Friends/ids = D,F,G are there a API that can get result Xxxx/ids= D,G directly? Its easy to call two apis and calculate by myself when two list are small. but it become inconvenient when one list is huge,(such as 7000 ids + 10 ids ) thanks. Andrew
[twitter-dev] How to query multiple Followers in one single call
Hi, Is it possible from the API in one single Call get the Followers/ Friends of multiple users? For example a function that receives a Array with user id's and returns all the ids of Friends/Followers. Thanks!
[twitter-dev] New Direct Messages breaks when a space is inserted
I am currently building an AS3 library for Twitter and Have everything working (that I need) except for sending a new direct message. This will work if there are no spaces / special characters, however as soon as a space / special character is inserted, it breaks and i get an 'invalid response' I have copied the URLs below along with the body of the posted (as it appears in fiddler) WORKS http://www.twitter.com/direct_messages/new.xml? oauth_consumer_key=Y6AmNZPsg1AOQLwCSmevQ oauth_nonce=R0agxUikM oauth_signature=R7spSxYu1fnhiCj4z4cc3nu3%2FKc%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1256737004 oauth_token=83934696-9mlD2907Boot90C1YbLpkexMJwAFR8WdZojMJCmC1 oauth_version=1.0 body text: helloWorld user: whomba DOESNT WORK http://www.twitter.com/direct_messages/new.xml? oauth_consumer_key=Y6AmNZPsg1AOQLwCSmevQ oauth_nonce=IPNusdfF3dw oauth_signature=CrcXThFjyZ1MIU84RkrG8lb5L60%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1256737136 oauth_token=83934696-9mlD2907Boot90C1YbLpkexMJwAFR8WdZojMJCmC1 oauth_version=1.0 body text:hello World user: whomba I have tried urlEncoding it, and just making the text 'hello%20World' however both of these fail. I am able to get updateStatus to work, which as far as i can tell, is pretty identical as new direct message (as far as how the URL is constructed, and POST is sent) Hopefully one of you has had this problem also, and might be able to help. Thanks a lot! -Andrew
[twitter-dev] Re: Automated Tweets
What is the criteria for dupliate tweets? then how the polling applications works? they may have several tweets with similar text? On Oct 28, 8:14 am, Dwi Sasongko Supriyadi ruck...@gmail.com wrote: Hello, On Wed, Oct 28, 2009 at 6:23 PM, Greg gregory.av...@gmail.com wrote: Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? I also develop an application that sends tweets taken from plaintext. So far, I found experiences that twitter doesn't allow consecutive tweets that are identical. DWI
[twitter-dev] Re: Invalid Signature when manipulating URL directly
Thanks. That was not it though. It turns out when working in AS3, when you POST a URL and don't explicitly give it an Obj to POST it defaults it down to a GET statement, thus killing it. However, this still does not fix one issue I am having I will post that in a different spot though, since it does not pertain to this thread. On Oct 28, 7:19 am, ryan alford ryanalford...@gmail.com wrote: The signature parameter should be the last parameter. It should not be sorted with the other parameters. Ryan On Oct 28, 2009, at 1:14 AM, whomba andrew.l...@gmail.com wrote: Hello all. I just recently started using the twitter API and oAuth for a site I am working on. After wrapping my head around oAuth things seemed to be going well. Out of the 12 components of the library i am using, 8 worked right off the bat. Unfortunately, methods where I change the URL, then post to it seem to be breaking, resulting an invalid signature response. I am able to successfully post a new status, get timelines and grab direct messages, so I am fairly confident that my oAuth lib is working my URL is constructed as follows (replaced the '' with new lines for readiblity): [POST-ing] http://www.twitter.com/statuses/destroy/5206890175.xml? oauth_consumer_key=Y6AmNZPU23AOQLwCSmevQ oauth_nonce=ret3uSMFONY oauth_signature=QBzS8c51wJE6KuHG8XjlmrzL2Ko%3D oauth_signature_method=HMAC-SHA1 oauth_timestamp=1256668802 oauth_token=83934696-9mlDot0sC1YbL2907BopkexMJwAFR8WdZojMJCmC1 oauth_version=1.0 This results in the aforementioned error. Am I suppose to use a different URL when I encode it? I appreciate the assistance, this is my first time working with oAuth, and I am a still a bit fuzy.
[twitter-dev] Whitelisting Notification
Good afternoon, I have a question regarding whitelisting. I am a developer looking to produce material against the Twitter API (blah blah), and I recently requested whitelisting. The form says it takes 72 hours. So far, so good. That was a week ago, and I've heard nothing. I haven't been rejected per sé (that I know of), but my IP is still very much rate-limited to 150 requests per hour, and I've heard nothing. I haven't gotten an email informing me in either direction. I don't want to fill out the form again as I don't really want to even further overload some poor fellow. Does anyone know what the story is here? Do they take longer than 72 hours now? It's fine if they do. I just don't want to keep filling out requests if in fact there's just a longer queue, but I also don't want to sit and wait only to find out in a month that I was supposed to do some arbitrary action I didn't notice. Thanks, Luke
[twitter-dev] Profile search based on Bio field
Hello, we are new to twitter development, we want to know is there any open source API that provides us to send String query (regular expression) and return the list of the users whose bio text match with the query in their profile. Thank you.
[twitter-dev] Re: Net::Twitter dev release with Lists API support
also interested in joining list beta. is there a contact/request email or @ ?
[twitter-dev] Re: from:user and since_id breaking Search API
I'm *not* using since_id, but I'm sporadically getting warning
messages about it. Most of the time, my queries work.
d:\curl http://search.twitter.com/search.json?q=
%23jquerylang=enpage=1show_user=truerpp=15
{
results: [{
profile_image_url: http://a1.twimg.com/profile_images/353780044/
avatar_normal.png,
created_at: Thu, 29 Oct 2009 00:05:02 +,
from_user: 2twittdotcom,
to_user_id: null,
text: create a simple infinite carousel with #jquery
http://2twitt.com/3u7;,
id: 5244850622,
from_user_id: 33556519,
geo: null,
iso_language_code: en,
source: lt;a href=quot;http://apiwiki.twitter.com/quot;
rel=quot;nofollowquot;gt;APIlt;/agt;
}],
max_id: 5244850622,
since_id
: 5056020580,
refresh_url: ?since_id=5244850622q=%23jquery,
results_per_page: 15,
page: 1,
completed_in: 0.02854,
warning: adjusted since_id to 5056020580 (2009-10-22 00:00:00
UTC), requested since_id was older than allowed,
query: %23jquery
}
It's very annoying. Any ideas?
[twitter-dev] Re: php to json character handling
I find that PHP is very unreliable when processing JSON. Rather than even trying to fight this, I find it much more reliable to call the Twitter API with a request for Atom format, which is really just XML. Then I can use simplexml_load_string to get the result into a PHP object. From there I can use a foreach loop to pull out the pieces and store them in a MySQL database. I also find it easier to send it to jQuery through Ajax as an HTML string, since I'm going to have to add it to the page DOM as HTML anyway. In jQuery I use .get() to pull down the HTML from the server. I know JSON is intended for delivery to Javascript, but I have given up on using it with PHP. The PHP forums are filled with complaints about JSON handling. On Oct 28, 8:28 pm, Peter Denton petermden...@gmail.com wrote: Hello, We are working on a service dealing with a high volume of tweets. We are seeing crazy things coming through in tweets and are running into recurring issues when creating large JSON strings to pass to our parser. I am curious if anyone can share approach or methodology on how they are creating valid JSON via PHP. - We are storing the tweets as they are first in a DB - doing some processing - sending them back to the UI in various forms, via jQuery ajax calls ($.getJSON). 99% of the time, our server side encoding works great, but some tweets are just bizarre and valid JSON fails. Any advice helps. Cheers Peter
[twitter-dev] Re: Whitelisting Notification
It took me a little longer than a week. Be patient... the form you filled is the only thing I know one can do. You could search the archives of a few weeks back for a thread where Chad answered this question. Hope this helps. Regards, Atul. On Wed, Oct 28, 2009 at 1:47 PM, Luke Sneeringer lukesneerin...@gmail.comwrote: Good afternoon, I have a question regarding whitelisting. I am a developer looking to produce material against the Twitter API (blah blah), and I recently requested whitelisting. The form says it takes 72 hours. So far, so good. That was a week ago, and I've heard nothing. I haven't been rejected per sé (that I know of), but my IP is still very much rate-limited to 150 requests per hour, and I've heard nothing. I haven't gotten an email informing me in either direction. I don't want to fill out the form again as I don't really want to even further overload some poor fellow. Does anyone know what the story is here? Do they take longer than 72 hours now? It's fine if they do. I just don't want to keep filling out requests if in fact there's just a longer queue, but I also don't want to sit and wait only to find out in a month that I was supposed to do some arbitrary action I didn't notice. Thanks, Luke -- Regards, Atul Kulkarni www.d.umn.edu/~kulka053
[twitter-dev] Re: Whitelisting Notification
Hello, The queue is being worked on, hopefully everything will be cleared out tomorrow. If you haven't gotten a response by tomorrow night, please let me know. -Chad On Wed, Oct 28, 2009 at 11:34 PM, Atul Kulkarni atulskulka...@gmail.com wrote: It took me a little longer than a week. Be patient... the form you filled is the only thing I know one can do. You could search the archives of a few weeks back for a thread where Chad answered this question. Hope this helps. Regards, Atul. On Wed, Oct 28, 2009 at 1:47 PM, Luke Sneeringer lukesneerin...@gmail.com wrote: Good afternoon, I have a question regarding whitelisting. I am a developer looking to produce material against the Twitter API (blah blah), and I recently requested whitelisting. The form says it takes 72 hours. So far, so good. That was a week ago, and I've heard nothing. I haven't been rejected per sé (that I know of), but my IP is still very much rate-limited to 150 requests per hour, and I've heard nothing. I haven't gotten an email informing me in either direction. I don't want to fill out the form again as I don't really want to even further overload some poor fellow. Does anyone know what the story is here? Do they take longer than 72 hours now? It's fine if they do. I just don't want to keep filling out requests if in fact there's just a longer queue, but I also don't want to sit and wait only to find out in a month that I was supposed to do some arbitrary action I didn't notice. Thanks, Luke -- Regards, Atul Kulkarni www.d.umn.edu/~kulka053
[twitter-dev] Re: Automated Tweets
Hello, Currently we discard a tweet if it is an exact duplicate of the previous tweet, however we still return a success code (200). We are planning on changing this so it will return an error code when a tweet is not posted. -Chad On Wed, Oct 28, 2009 at 10:40 AM, Jai jaishank...@gmail.com wrote: What is the criteria for dupliate tweets? then how the polling applications works? they may have several tweets with similar text? On Oct 28, 8:14 am, Dwi Sasongko Supriyadi ruck...@gmail.com wrote: Hello, On Wed, Oct 28, 2009 at 6:23 PM, Greg gregory.av...@gmail.com wrote: Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? I also develop an application that sends tweets taken from plaintext. So far, I found experiences that twitter doesn't allow consecutive tweets that are identical. DWI
[twitter-dev] Re: How to query multiple Followers in one single call
Hello, Currently there is not a way to do this. The ids/friends, ids/followers, statuses/friends, statuses/followers methods can only return data for one user at a time. -Chad 2009/10/28 Duarte Aragão dara...@gmail.com: Hi, Is it possible from the API in one single Call get the Followers/ Friends of multiple users? For example a function that receives a Array with user id's and returns all the ids of Friends/Followers. Thanks!
[twitter-dev] Re: Automated Tweets
Hi, On Wed, Oct 28, 2009 at 9:40 PM, Jai jaishank...@gmail.com wrote: What is the criteria for dupliate tweets? then how the polling applications works? they may have several tweets with similar text? Duplicate tweets = consecutively, exactly same tweet. tweet1 = foo; tweet2 = bar; rv1 = send_tweet(tweet1); rv2 = send_tweet(tweet1); rv3 = send_tweet(tweet2); above sequence, only rv1 and rv3 are succeed. DWI On Oct 28, 8:14 am, Dwi Sasongko Supriyadi ruck...@gmail.com wrote: Hello, On Wed, Oct 28, 2009 at 6:23 PM, Greg gregory.av...@gmail.com wrote: Hello, I have an application that sends out a Tweet when a user Authorizes the Application and asks a Question to a particular user. Does Twitter block continous sending out of a Tweet within a time period? I am doing testing of the application and whenever I try to do a Update Status - it returns the ID of the last Tweet that I made from the account. Did my Consumer Key/Consumer Key get blocked, or will Twitter not allow the same tweet to be posted in a certain time period? I also develop an application that sends tweets taken from plaintext. So far, I found experiences that twitter doesn't allow consecutive tweets that are identical. DWI
