[twitter-dev] Re: direct messages / conversations
No, there is no API method which will do what you are asking for. As Taylor says, you need build this up for yourself as best you can using the sent / received DMs endpoints. On May 12, 10:19 am, galeyte gaetan...@gmail.com wrote: ... So i guess there's no other way ? On May 11, 5:58 pm, galeyte gaetan...@gmail.com wrote: Hi, I'm building a qml/js app. I'm now getting direct messages and i'm wondering if there's any way to get direct messages by sender screen names or id. IBy now i'm requesting /dirtect_messages.json and /direct_messages/ sent.json and merging the results together to build a tree and i would really appriciate another easiest way to do it. Thanks, -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Quick update on Devnest
Thanks for the reply. I do hope the presentation doesn't blow :P On May 9, 11:36 pm, Jason Costa jasonco...@twitter.com wrote: Hi Orian, It's a limitation of the building - the electrical network isn't set up to support that many connections in the area where the event is being held. It would not be fun to blow a fuse in the middle of a presentation - thus, the ask that developers charge their laptops ahead of time. Thanks, --Jason On May 9, 8:28 pm, Orian Marx (@orian) or...@orianmarx.com wrote: Glad to see this is going on, and that the event is being recorded for those of us who can't attend. Sorry for the snark but, does Twitter not have any room in the developer outreach budget for power strips? @orian On May 9, 7:07 pm, Jason Costa jasonco...@twitter.com wrote: Hi everyone, We're excited to see many of you this Thursday for Devnest. Just a couple of quick updates on the event. The Agenda: - Introduction from Dick Costolo - Platform updates from Ryan Sarver - Presentations from ecosystem developers - QA session with members of our platform team - After QA, members of our platform team will be hanging out - please show us your apps! - Shortly after 8:30pm, we'll be heading to Jillian's to hang out - feel free to join us Other important notes about the event: - Please plan to start arriving around 6:15pm, as we'll do our best to start on time at 6:30pm - We'll be signing in registered guests in the first floor lobby of our office (795 Folsom Street) - Be sure to juice up your laptop battery before arriving: we'll be extremely limited on power outlets! - The hashtag for the event will be #devnestSF - If you can't attend but would like to ask questions, please tag them with #devnestSF - We'll be live-tweeting from the @twitterapi account - be sure to follow along! For those on the waitlist, we've had significant interest in the event and won't be able to accommodate additional attendees this time around. But don't worry, we'll be having more of these in the future and we'll also be recording the event. We plan to upload the video footage to dev.twitter.com. See you Thursday! --Jason -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Quick update on Devnest
Glad to see this is going on, and that the event is being recorded for those of us who can't attend. Sorry for the snark but, does Twitter not have any room in the developer outreach budget for power strips? @orian On May 9, 7:07 pm, Jason Costa jasonco...@twitter.com wrote: Hi everyone, We're excited to see many of you this Thursday for Devnest. Just a couple of quick updates on the event. The Agenda: - Introduction from Dick Costolo - Platform updates from Ryan Sarver - Presentations from ecosystem developers - QA session with members of our platform team - After QA, members of our platform team will be hanging out - please show us your apps! - Shortly after 8:30pm, we'll be heading to Jillian's to hang out - feel free to join us Other important notes about the event: - Please plan to start arriving around 6:15pm, as we'll do our best to start on time at 6:30pm - We'll be signing in registered guests in the first floor lobby of our office (795 Folsom Street) - Be sure to juice up your laptop battery before arriving: we'll be extremely limited on power outlets! - The hashtag for the event will be #devnestSF - If you can't attend but would like to ask questions, please tag them with #devnestSF - We'll be live-tweeting from the @twitterapi account - be sure to follow along! For those on the waitlist, we've had significant interest in the event and won't be able to accommodate additional attendees this time around. But don't worry, we'll be having more of these in the future and we'll also be recording the event. We plan to upload the video footage to dev.twitter.com. See you Thursday! --Jason -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to ignored
Yes you need both the in_reply_to information to be set as well as the @username to appear within the tweet. And yes, this could be documented better. @orian On May 5, 2:29 pm, Colt Fred coltf...@gmail.com wrote: Greetings community, I've experienced a problem recently that I can't find an official answer to. I'm attempting to use the update rest api and I'm passing in in_reply_to=XX, but it's being ignored. If I include a @user where user is the owner of the tweet id I passed in, it works fine. The official api documentation makes no note of this and I see that there was talk of not requiring the @user here(http:// groups.google.com/group/twitter-development-talk/browse_thread/thread/ f009c76d17199084?pli=1) but I also see someone complaining about the same problem here (http://groups.google.com/group/twitter-development- talk/browse_thread/thread/4ed686abbf59164b). What's twitter's official stance? If it is required to make the in reply to link, it should be noted in the api documentation. Thanks! Colt -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: New API Console Documentation updates on dev.twitter.com
It's great to see progress on this! The real test though will be whether future reported documentation errors can be fixed immediately by Twitter staff once verified. Refreshing documentation every 6 - 12 months is something, but far from ideal. Hopefully the recent efforts by Twitter staff to work on documentation, fix bugs and close out issues is a sign of continuous improvement. Keep it up! :) As for feedback on the current documentation: I think the biggest issue is that the navigation makes it very difficult to find a method if you don't know exactly what you're looking for. It would be useful if more than one node in the menu could be expanded at a time (make it a real tree, with an expand all) and even better would be a single page with all methods with brief descriptions inline. @orian On May 4, 12:50 pm, Arnaud Meunier arn...@twitter.com wrote: Hey Developers! You might have noticed that we started updating our developer portal yesterday, starting with the replacement of the old Twurl console with Apigee's. If you've never tried Apigee's test console, you should take a look at it! It's a great tool to test and debug your API calls, and we hope you'll like it as much as we do:http://dev.twitter.com/console On the documentation side, we updated our Twitter libraries page, cleaning and merging our old OAuth + Twitter sections. We know lots of you access our resources through open-sourced libraries, so let us know if you think we're missing a good one:http://dev.twitter.com/pages/libraries We've also been working on our API resources documentation (all of them are listed in the right sidebar onhttp://dev.twitter.com/doc): - Deprecated resources are now grouped in a new Deprecated resources category (for examplehttp://dev.twitter.com/doc/post/:user/lists). On their doc pages we've recommended a new or replacement method you should use instead. - New lists resources have been documented (8 List, 5 ListMembers and 4 ListSubscribers resources) - Redundant streaming resources have been removed and redirected (all streaming API methods can be found onhttp://dev.twitter.com/pages/streaming_api_methods). - Lots of other API resources have been updated to reflect the way they're actually working today. We know accurate documentation is important for you guys, so please let us know if you think some of our API resources documentation still need some love. We'd love your feedback :) Arnaud / @rno -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Visual refresh of the OAuth screens
I think it's good to be giving users more information on what they are granting access to, but by leaving out a number of things there are misleading implications. In particular, this list does not mention that users will be granting access to all their private DMs. I also find it interesting the list mentions the ability to follow new people, but not to unfollow existing people. Obviously it's been to everyone's benefit who has built apps that rely on OAuth up to this point that there has been specific mentioning of access to DMs as this would likely turn off a lot of people from granting access to experimental apps. The reality is that the OAuth system needs finer-grained controls. It would be good to hear if there has been any new thought on this from Twitter engineering. Otherwise, I like the new page :) @orian On Apr 28, 5:02 pm, Matt Harris thematthar...@twitter.com wrote: Hey Developers, Some of you may have noticed already that earlier today we deployed a redesign of the OAuth screens. We know both you and your users have been asking for better clarity about what an application can see and do with an account and these screens are a step towards doing that. One of the areas we wanted to improve is showing the details of your application. If you visit the new screens you will see we've separated your application details from the permissions that are being requested. We did this to help users see that it is your application, not Twitter's. Remember you can update your application details at anytime onhttp://dev.twitter.com/apps. Mobile and international support has also been improved and we now use the same rendering templates as those created for Web Intents. This ensures the design matches the rest of #newtwitter and, more importantly, works cross-browser, cross-platform, and multilingual. We hope you find the new designs more welcoming and friendly. Let us know what you think. Best, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Mentions by me
Use Twitter search for @username On Apr 4, 12:57 pm, nit_s nitinsing...@gmail.com wrote: Hi , Is there any API where I can get tweets that mention anyone (has an @ symbol in it)? The only option I can see is to get all the tweets and parse through them looking for @ symbols. thanks Nitin -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: consistency and ecosystem opportunities
What I am hearing by reading through this thread and the various responses by @rsarver and @raffi is that Twitter is helping developers of Twitter clients realize that their efforts will not be economically fruitful. This is because Twitter HQ can't see how someone can build a Twitter client that is economically viable, due to one of two possible things: either their roadmap dictates that third party developers will not be able to be economically viable or they simply cannot envision any innovation in Twitter clients that anyone would pay for. It seems the former is more of the case here, but I don't put the later out of the realm of possibility, which is unfortunate. As for the former, whether Ryan's email was informative, helpful, harassing, or threatening is really of little point relative to the actual changes to the Twitter Terms of Service. I have worked hard for a year on a Twitter client that I think delivers substantial innovation, and I came to SXSW to unveil it. It delivers innovation that I believe people would pay for, and my feedback here has been confirming that. The changes to the ToS I believe may jeopardize the viability of the various solutions I have provided to long-standing problems with Twitter. The end result is that Twitter users will be deprived of solutions to long-standing problems, I will be deprived of the opportunity to grow a viable business, and Twitter will be deprived of innovation in their ecosystem. This seems to be a lose-lose situation all around, but obviously Twitter sees a forthcoming benefit for them that outweighs this. In the end what I really don't understand is that services such as HootSuite and CoTweet suddenly become reclassified as enterprise applications because they've figured out ways to generate revenue and are therefor no longer Twitter clients? This all seems to be based around an assumption that people won't ever pay to use Twitter in some capacity, only businesses. This, to me, is ludicrous. @orian On Mar 11, 2:18 pm, Ryan Sarver rsar...@twitter.com wrote: Hey all, I’d like to give you an update about the state of the Twitter Platform and hopefully provide some much requested guidance. Since this time last year, Twitter use has skyrocketed. We’ve grown from 48 million to 140 million tweets a day and we’re registering new accounts at an all-time record. This massive base of users, publishers, and businesses is a giant playground for developers to build their own businesses on, and this means the opportunity has grown for everyone. With more people joining Twitter and accessing the service in multiple ways, a consistent user experience is more crucial than ever. As we talked about last April, this was our motivation for buying Tweetie and developing our own official iPhone app. It is the reason why we have developed official apps for the Mac, iPad, Android and Windows Phone, and worked with RIM on their Twitter for Blackberry app. As a result, the top five ways that people access Twitter are official Twitter apps. Still, our user research shows that consumers continue to be confused by the different ways that a fractured landscape of third-party Twitter clients display tweets and let users interact with core Twitter functions. For example, people get confused by websites or clients that display tweets in a way that doesn’t follow our design guidelines, or when services put their own verbs on tweets instead of the ones used on Twitter. Similarly, a number of third-party consumer clients use their own versions of suggested users, trends, and other data streams, confusing users in our network even more. Users should be able to view, retweet, and reply to @nytimes’ tweets the same way; see the same profile information about @whitehouse; and be able to join in the discussion around the same trending topics as everyone else across Twitter. *A Consistent User Experience* Twitter is a network, and its network effects are driven by users seeing and contributing to the network’s conversations. We need to ensure users can interact with Twitter the same way everywhere. Specifically: - *The mainstream consumer client experience*. Twitter will provide the primary mainstream consumer client experience on phones, computers, and other devices by which millions of people access Twitter content (tweets, trends, profiles, etc.), and send tweets. If there are too many ways to use Twitter that are inconsistent with one another, we risk diffusing the user experience. In addition, a number of client applications have repeatedly violated Twitter’s Terms of Service, including our user privacy policy. This demonstrates the risks associated with outsourcing the Twitter user experience to third parties. Twitter has to revoke literally hundreds of API tokens / apps a week as part of our trust and safety efforts, in order to protect the user experience on our platform. - *Display of tweets in 3rd-party services*.
[twitter-dev] Re: Follower analysis without whitelisting breaks limits?
I don't know what the current state of this is but it looks like Site Streams will support unfollow events for this purpose: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/74ae054ec728e6dc On Feb 18, 5:11 pm, Jo jseib...@seibert-media.net wrote: It seems as if no one at twitter as an answer or a solution on this. That's bad... Or are they still thinking about it? Cheers. Jo Seibert On 15 Feb., 11:03, Dewald Pretorius dpr...@gmail.com wrote: Thanks Tim. So the point is, we still need to rely on the follower ids list API method if we want to maintain an up to date picture of an account's followers. For larger accounts this becomes impractical with a limit of 350 calls per hour. On Feb 15, 4:13 am, Tim Haines tmhai...@gmail.com wrote: It sends you an event when our subject user follows someone else, unfollows someone else, or when they are followed by someone else. It does not send an event when they are unfollowed by someone else. Tim. On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius dpr...@gmail.com wrote: If I remember correctly, Site Streams sends you a transaction only when the user follows another user (adding to Following). It does not send you a transaction when someone else follows that user (adding to Followers). I don't know if this work the same in User Streams. Clarification by Twitter will be appreciated. On Feb 14, 12:38 pm, David Giamanco dgiama...@gmail.com wrote: I believe the new way to do this is to initially call the REST API to get all of the ids for the first time you process this user. Then you setup a User Stream on the user and process any requests that come in through there. For your uses, if you only show users the differences in follower counts then you don't need the initial call to the REST API to collect all ids. All you need is a count of the ids and then to initiate a User Stream. The User Stream will give you the differences in real time and you can store just the differences, instead of the entire set of ids. David Giamanco -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Is this a bug for referencing status urls?
It seems one can reference any valid status by id using the following URL formula *if* you are signed in to twitter.com: http://twitter.com/#!/this_can_be_anything/statuses/38671791899684864 but this will lead to a sorry this page doesn't exist if you are not logged in. This seems like strange behavior to me? This was pointed out to me by @samichaels. -@orian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Update on Whitelisting
Ryan et al, thanks for the update on this. Shall we also take this to mean 350 is the definitive cap on rate limits for the foreseeable future? This certainly seems to be implied but since the spirit of this update seems to be to remove ambiguity, I think a clear statement that Twitter is no longer planning on gradually increasing rate limits, as has been stated many times in the past, would be appreciated. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: Update on Whitelisting
Yup that certainly clarifies and thanks for the #newtwitter stats, it's something I've been very curious about (and I'm sure others as well)! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Is there going to be another Chirp?
I'll second holding it in NYC! (but I'm biased) On Feb 6, 11:35 pm, Brainewave Consulting i...@brainewave.com wrote: I vote for Chirp: NYC! Mike Caprio Principal and Lead Consultant Brainewave Consulting 402 Graham Avenue PMB 211 Brooklyn, NY 11211 p: +1-347-269-0558 @brainewave On Feb 6, 2011, at 11:20 PM, zbowl...@gmail.com wrote: Yah, more of these would be fun. On Feb 6, 12:28 pm, Abraham Williams 4bra...@gmail.com wrote: How about some more state of the union events too. I thought they were going to be quarterly. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sun, Feb 6, 2011 at 12:21, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Maybe this is the wrong place to ask, but is there going to be another Chirp? If so, when and where? I'm making my conference plans for the year and pretty much know when everything is *except* Chirp! -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Is there going to be another Chirp?
Non-Twitter-employee developer headcount might be something they should still be concerned with too... On Feb 6, 3:50 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: On Sun, 6 Feb 2011 12:28:39 -0800, Abraham Williams 4bra...@gmail.com wrote: How about some more state of the union events too. I thought they were going to be quarterly. Given the rumored growth rate of Twitter head count, I'd say they probably have more pressing priorities, like finding new digs. ;-) -- http://twitter.com/znmebhttp://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Different crossdomains for a0.twimg.com a2.twimg.com, a3 etc
That's good to hear. I wondering if these other crossdomain.xml issues that's I've be raising for more than a year will ever be addressed? http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/2a8e40506a039072 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/28232e3965222037/4a9763e9a77f959c http://groups.google.com/group/twitter-development-talk/browse_thread/thread/fa7c3f42f85b8d3/6862f36c734b1082 http://groups.google.com/group/twitter-development-talk/browse_thread/thread/4adf2a0297ce052d/e6831b2340a30478 On Dec 17, 5:21 pm, Matt Harris thematthar...@twitter.com wrote: Hey Ben, I've checked this with the team and they have corrected the crossdomain file so it is now open on twimg. Our CDN should be returning the correct file now but it's possible some hosts need a bit longer to have their caches cleared. Thanks, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Dec 16, 2010 at 10:13 PM, WildFoxMedia wildfoxme...@gmail.comwrote: Hi Matt, I appreciate you jumping into this thread and I look forward to your response. -Ben On Dec 16, 2:07 pm, Matt Harris thematthar...@twitter.com wrote: Thanks for letting us know about this. I've asked the team to if this file should be as restrictive as it currently is. Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Dec 16, 2010 at 11:16 AM, WildFoxMedia wildfoxme...@gmail.com wrote: Super, they are all returning the same thing now, which is blocking access from any non-twitter domain which you can see below: cross-domain-policy xsi:noNamespaceSchemaLocation=http:// www.adobe.com/xml/schemas/PolicyFile.xsd allow-access-from domain=twitter.com/ allow-access-from domain=api.twitter.com/ allow-access-from domain=search.twitter.com/ allow-access-from domain=static.twitter.com/ site-control permitted-cross-domain-policies=master-only/ allow-http-request-headers-from domain=*.twitter.com headers=* secure=true/ /cross-domain-policy What is Twitters official stance on this? Are Flash developers SOL and required to use a server-side proxy to grab images, or are we supposed to be able to grab profile images from *.twimg? On Dec 15, 5:57 pm, John Adams j...@twitter.com wrote: a0 through a4 should offer identical crossdomain.xml files. They are all going through a CDN, so it might be the case that the CDN endpoint you are hitting has a stale file. I just checked all of the CDN endpoints from here and they are returning the same data. Try again? -john On Wed, Dec 15, 2010 at 5:20 PM, WildFoxMedia wildfoxme...@gmail.com wrote: Im currently seeing the same issue, however, in completely reverse. As of this moment, a0 a1 are not allowing other domains and a2 a3 are allowing all domains. The other day, all 4 were not allowing other domains. Is there any reason or rhyme for this and more importantly, what is the expectation? Are we supposed to be able to make calls from Flash for profile images or not? On Nov 28, 3:57 pm, stephen sno...@bcm.com.au wrote: Hey, It appears the crossdomains for a2, a3, etc are different and are preventing flash from accessing profile images on these domains. a0 and a1 are fine, however the api returns profile image urls using all of these domains (a0 - a?). Are the crossdomains suppose to be all the same or are we suppose to target only the first two? From the few that I've tested, it seems all profile images are accessible through the a0 or a1 domains despite what the api returns. Crossdomains http://a0.twimg.com/crossdomain.xmlhttp://a1.twimg.com/crossdomain.xm. .. Stephen -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and
[twitter-dev] Re: not getting unfollow and retweet event from User Stream
Is there still an active discussion on whether or not Twitter will send deletion information in the future or has this been settled? On Dec 8, 6:32 pm, John Kalucki j...@twitter.com wrote: Yusuke, The documentation had an error. We don't send friendship deletions, even those that come from you. I fixed the documentation. I just tested retweets. I logged in, as myself, retweeted something, and the retweet (really, a tweet), and the subsequent deletion were syndicated properly. Can you reproduce this case? -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Wed, Dec 8, 2010 at 12:24 AM, Yusuke Yamamoto yus...@mac.com wrote: Hi all, I'm not getting unfollow (from me) and retweet (from me) events from User Stream now. I suppose I used to be getting that sort of events as documented. -- • Friendship Events • Created - To you, from you ... • Retweet Events • To you, from you. (Retweets from your followings are sent as the actual home timeline retweet) -- from:http://dev.twitter.com/pages/user_streams Is there any spec change that I'm missing? Thanks in advance, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on :http://twitter.com/yusukeyamamoto subscribe me at :http://samuraism.jp/ -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Rate limiting and whitelisting when making authenticated calls on a user's behave.
If I have oauth creds for a user, is there any way to make calls to a REST endpoint that requires authentication for that user but counts the rate limiting against a whitelisted account that I own? For example, if I have a user's oauth creds is there any way I can fetch their mentions using a whitelisted account and not have it count against their rate limit? Does this work with IP whitelisting? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How is the newTwitter getting Replies to this Tweet?
That's really unfortunate. Any chance someone could give us more insight into this? @themattharris? @episod? @raffi? On Nov 5, 1:21 am, Abraham Williams 4bra...@gmail.com wrote: Looks like they changed it. Maybe it didn't scale. Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Nov 4, 2010 at 19:11, Orian Marx (@orian) or...@orianmarx.comwrote: Well, I was super excited to try this out, but it seems like this endpoint has changed to only return related tweets that pretty much aren't related at all. They're just recent tweets to / from the users mentioned in the original tweet, not replies to the original tweet. I have no idea why this would have been changed as whatever you saw, Abraham, is way more useful than what's being returned right now. Argh! Am I missing something? On Sep 20, 6:55 pm, Abraham Williams 4bra...@gmail.com wrote: The related_results/show/status_id method is returning replies to a status_id. Screenshot in the new UI: http://www.flickr.com/photos/4braham/5009432215/ API call: http://app.apigee.com/console/apigee-console-snapshots-128331720_... Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Mon, Sep 20, 2010 at 15:30, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Vega, #newtwitter uses the same API pattern available to all developers for this. When a status contains an in_reply_to_status_id field, then it is considered a reply to a preceding status, which is then fetched by requesting the particular status referenced by in_reply_to_status_id. This is why you'll see that the implementation in #newtwitter doesn't list *replies to* the current status, but instead the original status that sparked the reply-to. These can be chained but in many cases can never show the whole picture easily. It would great if we had a statuses/:id/replies method to return all statuses that reference the original status -- would be very useful in this context. Taylor On Mon, Sep 20, 2010 at 2:33 PM, Vega edgardo.v...@gmail.com wrote: I have heard the new Twitter only uses the api to display information if so how does it get Replies to this Tweet? Cheers, Edgardo -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Copying or Importing Twitter Lists
We're actually only a bit more than a month away from the one year mark from when this was first requested, yay! Here it is: http://code.google.com/p/twitter-api/issues/detail?id=1296 This ticket was merged: http://code.google.com/p/twitter-api/issues/detail?id=1657 On Nov 3, 5:39 pm, Quy quyten...@gmail.com wrote: I know I can page but can I get more than 20 members somehow from another call? Maybe Twitter can great another social graph API that returns 500 members in one API call like we can do today for friends/ followers. Quy On Nov 2, 8:20 pm, Edward Hotchkiss edw...@edwardhotchkiss.com wrote: paging. look for obj-next_cursor_str, begin with -1 - it's a string Best, -- Edward H. Hotchkisshttp://www.edwardhotchkiss.com/http://www.twitter.com/edwardhotchkiss/ -- edward.png 3KViewDownload On Nov 2, 2010, at 9:10 PM, Quy wrote: Is there a better way to grab all the members of list? This API call only returns 20 members at a time so it'll take 25 calls to get a 500 member list: http://dev.twitter.com/doc/get/:user/:list_id/members Quy On Nov 2, 12:29 pm, Ken D. k...@cimas.ch wrote: Don't know of any public tool, but as you suggest it won't be hard to make one. If you were planning to use the list /create_all method, see this thread first:https://groups.google.com/group/twitter-development- talk/browse_threa... On Nov 2, 7:54 pm, Quy quyten...@gmail.com wrote: Is there a tool out there that allows me to copy a Twitter List? For example, I've created a new account and wanted to migrate my Twitter Lists over to this new account or I want to copy an existing public Twitter List and edit it to my liking. I'm thinking of creating a simple tool using the Twitter API but will this hit any rate limiting if this is a public tool? Quy -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How is the newTwitter getting Replies to this Tweet?
Well, I was super excited to try this out, but it seems like this endpoint has changed to only return related tweets that pretty much aren't related at all. They're just recent tweets to / from the users mentioned in the original tweet, not replies to the original tweet. I have no idea why this would have been changed as whatever you saw, Abraham, is way more useful than what's being returned right now. Argh! Am I missing something? On Sep 20, 6:55 pm, Abraham Williams 4bra...@gmail.com wrote: The related_results/show/status_id method is returning replies to a status_id. Screenshot in the new UI:http://www.flickr.com/photos/4braham/5009432215/ API call:http://app.apigee.com/console/apigee-console-snapshots-128331720_... Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Mon, Sep 20, 2010 at 15:30, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Vega, #newtwitter uses the same API pattern available to all developers for this. When a status contains an in_reply_to_status_id field, then it is considered a reply to a preceding status, which is then fetched by requesting the particular status referenced by in_reply_to_status_id. This is why you'll see that the implementation in #newtwitter doesn't list *replies to* the current status, but instead the original status that sparked the reply-to. These can be chained but in many cases can never show the whole picture easily. It would great if we had a statuses/:id/replies method to return all statuses that reference the original status -- would be very useful in this context. Taylor On Mon, Sep 20, 2010 at 2:33 PM, Vega edgardo.v...@gmail.com wrote: I have heard the new Twitter only uses the api to display information if so how does it get Replies to this Tweet? Cheers, Edgardo -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: GET :user/lists/memberships - for private lists
I actually just posted about an undocumented parameter filter_to_owned_lists=true on this service. http://groups.google.com/group/twitter-development-talk/browse_thread/thread/bce660f31728b4e7 Calling the service with that parameter is returning private lists for me. On Nov 2, 7:33 am, Bondi roibo...@gmail.com wrote: Hi. We are using the following function to see what lists are following a user :http://dev.twitter.com/doc/get/:user/lists/memberships The problem is we get a respond that only includes the public lists he is member of. If he is a member of a private list that was created by the user that signed the request - we do not get those lists Anyone else encountered this problem ? Anyone else uses this function and DOES get private lists ? Thanks, Roi -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Useful undocumented parameter for :user/lists/memberships - filter_to_owned_lists
You can efficiently determine which lists owned by the authenticating user have a target user as a member by adding the parameter filter_to_owned_lists=true to :user/lists/memberships. This should probably be included in the documentation here: http://dev.twitter.com/doc/get/:user/lists/memberships -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Feedback on the sidebar of the documentation site
I've been meaning to post some feedback in regards to dev.twitter.com for a while. I'm wondering if anyone else is having the same experience I am. It's pretty much all in regards to the sidebar: * I find it harder to find methods I'm looking for now that everything is listed under collapsible headers on the right. * I find it disorienting that the headers expand in place, but when I click a method on page refresh the header and methods have jumped to the top of the sidebar. * Once you're looking at a method, if you expand a different section in the sidebar the current section collapses and you can't reopen it. All this kinda makes me wish we just had a nice simple sidebar that didn't have any expand/collapse functionality or at least had the option to expand multiple sidebar items and have the state be retained after clicking a method. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Is list/create_all working?
I'm trying to make a call to add multiple users to a list using the format http://api.twitter.com/1/owner_id/list_id/create_all.xml?user_id=user_id_1,user_id_2,user_id_3 This seems to be failing and returning an HTML page from Twitter. My calls to add the same users to the same list one at a time using list_id/members.xml works fine. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Cross-domain policy file
Zeh, thanks for taking the time to bring this issue to light again and to present so many examples of other significant APIs that do not have restrictive crossdomain policies. As you note, this issue has been brought to Twitter's attention several times over the last few years but to no avail. For my work I continue to have to rely on a PHP proxy for all calls between my Flash client and Twitter. This is certainly not ideal. Team Twitter, it's time for you to address this issue. One of the most popular clients for Twitter out there, TweetDeck, is built with Flash technology and yet runs as an AIR app I'm guessing in part because that has a different security model and does not have to deal with this. You should recognize that there is a large pool of developer talent that has, over the years, attempted to build wonderful things on your platform but have thrown up their hands and left due to frustration with this crossdomain policy. Please stop treating us as second class developers. Thanks, Orian On Oct 18, 3:34 pm, zeh fernando z...@zehfernando.com wrote: Does Twitter have any plans on when/whether they'll change its current cross-domain policy file? http://api.twitter.com/crossdomain.xmldoes not allow requests from Flash-based websites and web apps because it restricts response to twitter.com subdomains. http://search.twitter.com/crossdomain.xml, however, does allow Flash requests from any domain. This policy pretty much renders all Flash calls to the API useless (unless they're search calls). One could use proxy scripts, but given the limitations imposed by the Twitter API (150 calls per IP per hour), it means public websites are out of luck if they're getting any kind of public data without authenticating like, say, getting a (public) user timeline. This has been discussed at length in previous threads. Change in crossdomain.xml??http://groups.google.com/group/twitter-development-talk/browse_thread... Most curiously, the above thread mentions on March 2008 that Twitter would be moving API calls to api.twitter.com and allowing a more permissive crossdomain policy file there in a few months. This hasn't happened, though, since people have continued to be dumbfounded by the inability to load Twitter data from Flash-based web apps. Twitter Stream crossdomain.xmlhttp://groups.google.com/group/twitter-development-talk/browse_thread... I think this decision is specially questionable as the cross-domain restrictions in place do nothing else other than put a tax on what people can do from Flash-based web apps, but also allow any other usage from any other technology, be it a security issue or not. In fact, even using PHP proxies one could make the API calls from Flash (albeit in a restricted manner) so I can't see a real reason for singling out/blocking this platform. Normally, public APIs add no such artificial/ineffective restrictions, and simply allow any kind of connection (doing their own top of their own built-in restrictions and rate limiting)... http://graph.facebook.com/crossdomain.xml- allows connections from all domainshttp://api.flickr.com/crossdomain.xml- allows connections from all domainshttp://api.plixi.com/crossdomain.xml- allows connections from all domainshttp://api.bit.ly/crossdomain.xml- allows connections from all domainshttp://stream.twitvid.com/crossdomain.xml- allows connections from all domains ...etc etc So, is there any clear reason why the restriction is still in place? Or any idea on when this policy will be reviewed? Thanks, Zeh -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
The in_reply_to info is definitely set. It's showing up properly in TweetDeck. However things are right now, I don't think they should be touched. On Oct 13, 3:28 pm, Matt Harris thematthar...@twitter.com wrote: Looking into this it shows this is a presentation issue on twitter.com as these are mentions. To confirm this I checked the in_reply_to fields in the API response. In these messages the in_reply_to fields are null. This can also be seen when not in #newtwitter -http://twitter.com/mikedizondoes not report the tweet as a reply to you. I've let the webteam know about this heading causing confusion. --- @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, Oct 13, 2010 at 11:40 AM, Orian Marx (@orian) or...@orianmarx.com wrote: It seems like a proper @reply does not require a leading @username. Take this recent reply to me for example:http://twitter.com/#!/mikedizon/statuses/27265789132 (note the reply was created via twitter.com too). On Oct 8, 12:07 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: I've never known this to work, but I easily could be wrong. API won't do anything to stop you from doing this -- but it won't be considered an @reply. HootSuite very well could do some server-side association of the post since it is cognizant of the intent during creation -- but that seems far-fetched. Taylor On Fri, Oct 8, 2010 at 8:44 AM, Orian Marx (@orian) or...@orianmarx.comwrote: When did this change to actually require starting the @reply with the @username? HootSuite has long supported sending tweets in reply to others without leading with the @username. Does this no longer work? On Oct 7, 3:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious: An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2. .. like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: status/update in_reply_to_user_id not being acknowledged
When did this change to actually require starting the @reply with the @username? HootSuite has long supported sending tweets in reply to others without leading with the @username. Does this no longer work? On Oct 7, 3:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: With as often as this comes up, it's obvious that we aren't communicating this clearly and the historical aspect of this isn't obvious: An @reply requires that it begins with the @username of the user being replied to. The in_reply_to_status_id field is not enough to associate the tweets as a reply -- the username must also be present. Also: When using a POST method, don't include your fields/parameters on the query string. Instead, put them in the POST body. You may find someday that passing such parameters on the query string just stops working. Taylor On Thu, Oct 7, 2010 at 1:37 PM, Matthew matt.c.w...@gmail.com wrote: Hello, Been working on a project that will allow users to reply to tweets. I am having difficulty in getting the 'in_reply_to_message_id' to be acknowledged. I have been using the latest version of Abraham's TwitterOAuth library, also confirmed the problem through apigee. Example request (over POST): http://api.twitter.com/1/statuses/update.json?in_reply_to_status_id=2... like its not working for apigee either I can confirm the in_reply_to_status_id message is a message I posted earlier. http://api.twitter.com/1/statuses/show/26673308442.json I get a response back from twitter with field populated except with in_reply_to_status_id : null. Is there currently a glitch in the twitterapi, or am I using this function improperly? Thanks in advance! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: user_timeline since_id issues
It remains a good idea. Imagine if Gmail only let you retrieve your last 3200 messages even if you had 40,000. On Sep 30, 4:20 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I also posted a request a long time ago that an authenticated user be able to retrieve all of his own tweets, back beyond the 16-page limit. In retrospect, now that I'm within shooting distance of 40,000 I'm not sure how good an idea that is. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Abraham Williams 4bra...@gmail.com: Here is a closed feature request from forever ago to return the status_id of all statuses for a user. Maybe Twitter wil reconsider the request. http://code.google.com/p/twitter-api/issues/detail?id=379 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 30, 2010 at 11:32, linuslive michael.c@gmail.com wrote: Hmmm...but there is no way to know the ids of the tweets without having a list of all of the tweets, which would kind of defeat the purpose of the limit. Oh well... On Sep 30, 12:39 pm, Tom van der Woerdt i...@tvdw.eu wrote: Only the 3200 most recent ones, unless you know the IDs of the tweets. Tom On 9/30/10 5:09 PM, linuslive wrote: Good morning all! Before the OAuth change, I wrote a twitter archiver that would grab my tweets and dump them into a database. Back then I only had about 1K tweets so I was able to grab all my tweets without hitting the limit. And of course since then, I don't post more than 20 tweets a day. But today, I was curious to see if I could use the new OAuth to retrieve my timeline, starting from my first tweet. I can't seem to get it. Here are my parameters: http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. When I do this, it only gives me the top 200 tweets. It doesn't start from the beginning and give me my 200 oldest tweets, as I would expect. I've tried various since_id's, even retrieving my first tweet: http://twitter.com/linuslive/statuses/872090728 Which equals http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. And I get the same response. According to twitter, I have 3682 tweets, just over the 3200 limit according tohttp://dev.twitter.com/doc/get/statuses/user_timeline. The confusing thing is that the documentation does not make it clear that it's 3200 of the most recent tweets, or just 3200 per session. Could I get a clarification on this? Thanks!- Hide quoted text - - Show quoted text - -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: user_timeline since_id issues
Fair point. Searching over it is trivial however, and perhaps that would provide the most immediate benefit if implemented by Twitter. Obviously though they don't have the capacity to handle that right now, so at least allowing users to access all of their own tweets so they can potentially index them themselves seems to make sense. On Sep 30, 4:43 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: Retrieving one's GMail, for example, if one wants to delete the account, is a decidedly non-trivial exercise. Perhaps it's simple with Outlook, but KMail, Evolution and Thunderbird all gave me a ration of doo-doo in the process, and I'm not sure I did it right. -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Orian Marx (@orian) or...@orianmarx.com: It remains a good idea. Imagine if Gmail only let you retrieve your last 3200 messages even if you had 40,000. On Sep 30, 4:20 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I also posted a request a long time ago that an authenticated user be able to retrieve all of his own tweets, back beyond the 16-page limit. In retrospect, now that I'm within shooting distance of 40,000 I'm not sure how good an idea that is. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Abraham Williams 4bra...@gmail.com: Here is a closed feature request from forever ago to return the status_id of all statuses for a user. Maybe Twitter wil reconsider the request. http://code.google.com/p/twitter-api/issues/detail?id=379 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 30, 2010 at 11:32, linuslive michael.c@gmail.com wrote: Hmmm...but there is no way to know the ids of the tweets without having a list of all of the tweets, which would kind of defeat the purpose of the limit. Oh well... On Sep 30, 12:39 pm, Tom van der Woerdt i...@tvdw.eu wrote: Only the 3200 most recent ones, unless you know the IDs of the tweets. Tom On 9/30/10 5:09 PM, linuslive wrote: Good morning all! Before the OAuth change, I wrote a twitter archiver that would grab my tweets and dump them into a database. Back then I only had about 1K tweets so I was able to grab all my tweets without hitting the limit. And of course since then, I don't post more than 20 tweets a day. But today, I was curious to see if I could use the new OAuth to retrieve my timeline, starting from my first tweet. I can't seem to get it. Here are my parameters: http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. When I do this, it only gives me the top 200 tweets. It doesn't start from the beginning and give me my 200 oldest tweets, as I would expect. I've tried various since_id's, even retrieving my first tweet: http://twitter.com/linuslive/statuses/872090728 Which equals http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. And I get the same response. According to twitter, I have 3682 tweets, just over the 3200 limit according tohttp://dev.twitter.com/doc/get/statuses/user_timeline. The confusing thing is that the documentation does not make it clear that it's 3200 of the most recent tweets, or just 3200 per session. Could I get a clarification on this? Thanks!- Hide quoted text - - Show quoted text - -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter
[twitter-dev] Re: user_timeline since_id issues
This should probably be a separate thread, but... what about a bulk tweet lookup using status_ids for one very specific use case: turning search results into proper tweets and avoiding all the other issues that exist with the current implementation? I know bulk tweet lookup by id has been asked before and the response is it's the same capacity issue of accessing old tweets from storage. Okay, so what about a bulk tweet lookup limited to timestamps that fall within whatever range search capacity is currently at (ya know, like the last seven days)? I bet this could actually reduce the number of calls developers are making when dealing with converting search result items into proper status objects. On Sep 30, 4:57 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: I'll agree with all of you that'd it be valuable for us to do this. The current state of availability of tweets is a capacity issue. It's not in anyway a deliberate prevention of access. As for since_id in this context -- it'd be great if it'd work to just use since_id=1, but it doesn't. I don't even think it'd work if you knew the very first status id that the user had ever posted.. because in most cases, that status id would be unknown to the back end transport layer (for the same reason it can't access the tweet itself). If we could provide a means today to allow complete traversal of a user_timeline for a specific user with over ~3200 tweets, we would -- and I'm pretty confident we will. But not today and not tomorrow. Taylor On Thu, Sep 30, 2010 at 1:43 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Retrieving one's GMail, for example, if one wants to delete the account, is a decidedly non-trivial exercise. Perhaps it's simple with Outlook, but KMail, Evolution and Thunderbird all gave me a ration of doo-doo in the process, and I'm not sure I did it right. -- M. Edward (Ed) Borasky http://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Orian Marx (@orian) or...@orianmarx.com: It remains a good idea. Imagine if Gmail only let you retrieve your last 3200 messages even if you had 40,000. On Sep 30, 4:20 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I also posted a request a long time ago that an authenticated user be able to retrieve all of his own tweets, back beyond the 16-page limit. In retrospect, now that I'm within shooting distance of 40,000 I'm not sure how good an idea that is. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Abraham Williams 4bra...@gmail.com: Here is a closed feature request from forever ago to return the status_id of all statuses for a user. Maybe Twitter wil reconsider the request. http://code.google.com/p/twitter-api/issues/detail?id=379 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 30, 2010 at 11:32, linuslive michael.c@gmail.com wrote: Hmmm...but there is no way to know the ids of the tweets without having a list of all of the tweets, which would kind of defeat the purpose of the limit. Oh well... On Sep 30, 12:39 pm, Tom van der Woerdt i...@tvdw.eu wrote: Only the 3200 most recent ones, unless you know the IDs of the tweets. Tom On 9/30/10 5:09 PM, linuslive wrote: Good morning all! Before the OAuth change, I wrote a twitter archiver that would grab my tweets and dump them into a database. Back then I only had about 1K tweets so I was able to grab all my tweets without hitting the limit. And of course since then, I don't post more than 20 tweets a day. But today, I was curious to see if I could use the new OAuth to retrieve my timeline, starting from my first tweet. I can't seem to get it. Here are my parameters: http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. When I do this, it only gives me the top 200 tweets. It doesn't start from the beginning and give me my 200 oldest tweets, as I would expect. I've tried various since_id's, even retrieving my first tweet: http://twitter.com/linuslive/statuses/872090728 Which equals http://api.twitter.com/1/statuses/user_timeline.json?screen_name=linu. .. And I get the same response. According to twitter, I have 3682 tweets, just over the 3200 limit according tohttp://dev.twitter.com/doc/get/statuses/user_timeline. The confusing thing is that the documentation does not make it clear that it's 3200 of the most recent tweets, or just 3200 per session. Could
[twitter-dev] Re: user_timeline since_id issues
If you need any reinforcement from the developer community just let us know ;) On Sep 30, 5:19 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Theorizing from the outside-in on our capacity issues aside, I'm a big advocate for a bulk status/show or lookup function. We're definitely giving that a lot of thought at the moment. Taylor On Thu, Sep 30, 2010 at 2:10 PM, Abraham Williams 4bra...@gmail.com wrote: Considering Twitter can support returning the ids of almost 300,000 followers then 40,000 tweets should be easy. http://api.twitter.com/1/followers/ids.json?screen_name=rsarver Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 30, 2010 at 14:04, Orian Marx (@orian) or...@orianmarx.com wrote: This should probably be a separate thread, but... what about a bulk tweet lookup using status_ids for one very specific use case: turning search results into proper tweets and avoiding all the other issues that exist with the current implementation? I know bulk tweet lookup by id has been asked before and the response is it's the same capacity issue of accessing old tweets from storage. Okay, so what about a bulk tweet lookup limited to timestamps that fall within whatever range search capacity is currently at (ya know, like the last seven days)? I bet this could actually reduce the number of calls developers are making when dealing with converting search result items into proper status objects. On Sep 30, 4:57 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: I'll agree with all of you that'd it be valuable for us to do this. The current state of availability of tweets is a capacity issue. It's not in anyway a deliberate prevention of access. As for since_id in this context -- it'd be great if it'd work to just use since_id=1, but it doesn't. I don't even think it'd work if you knew the very first status id that the user had ever posted.. because in most cases, that status id would be unknown to the back end transport layer (for the same reason it can't access the tweet itself). If we could provide a means today to allow complete traversal of a user_timeline for a specific user with over ~3200 tweets, we would -- and I'm pretty confident we will. But not today and not tomorrow. Taylor On Thu, Sep 30, 2010 at 1:43 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: Retrieving one's GMail, for example, if one wants to delete the account, is a decidedly non-trivial exercise. Perhaps it's simple with Outlook, but KMail, Evolution and Thunderbird all gave me a ration of doo-doo in the process, and I'm not sure I did it right. -- M. Edward (Ed) Borasky http://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Orian Marx (@orian) or...@orianmarx.com: It remains a good idea. Imagine if Gmail only let you retrieve your last 3200 messages even if you had 40,000. On Sep 30, 4:20 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I also posted a request a long time ago that an authenticated user be able to retrieve all of his own tweets, back beyond the 16-page limit. In retrospect, now that I'm within shooting distance of 40,000 I'm not sure how good an idea that is. ;-) -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting Abraham Williams 4bra...@gmail.com: Here is a closed feature request from forever ago to return the status_id of all statuses for a user. Maybe Twitter wil reconsider the request. http://code.google.com/p/twitter-api/issues/detail?id=379 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Sep 30, 2010 at 11:32, linuslive michael.c@gmail.com wrote: Hmmm...but there is no way to know the ids of the tweets without having a list of all of the tweets, which would kind of defeat the purpose of the limit. Oh well... On Sep 30, 12:39 pm, Tom van der Woerdt i...@tvdw.eu wrote: Only the 3200 most recent ones, unless you know the IDs of the tweets. Tom On 9/30/10 5:09 PM, linuslive wrote: Good morning all! Before the OAuth change, I wrote a twitter archiver that would grab my tweets and dump them into a database. Back then I only had about 1K tweets so I was able to grab all my tweets without hitting
[twitter-dev] Re: @user_mentions and profile_image_urls
How are you getting the user mentions? Is it through statuses/mentions or using search? If you're using search, each result includes a field like this: link type=image/png href=http://a3.twimg.com/profile_images/ 5/of_normal.jpg rel=image/ That url is a reference to the user's profile image. On Sep 2, 5:40 pm, Claudia cbern...@gmail.com wrote: I've asked about this before - so apologies if anyone is re-reading this... I'm needing to get the profile_image_urls of all the @user_mentions in a timeline. Right now, it looks like the only way I can do this without killing rate limit in about an hour (which I just did) is to send a comma separated-list to users/lookup. However - this is adding major complications to my app structure, and I'd much rather avoid it. I can store the returned urls in a local DB, but if enough people use the app within an hour, it'll still quickly exceed the rate limit. Does anyone have any suggestions as to how I can get this done? Even better - anyone at Twitter think that the API could return the profile_image_url with the current @user_mention data.. seems it would be useful for many. Thanks in advance, Claudia -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: retweeted always returing as false in /1/statuses/user_timeline.json
At this point there are a number of fields on various objects returned by Twitter that should be considered unreliable (mostly on user objects). It might be time for Twitter to consider a better solution than just returning unreliable data, such as either stripping out the fields, giving them an attribute such as fieldstatus=deprecated or fieldstatus=disabled. These expected behaviors are only expected by the engineers on Twitter's end and I've seen lots of posts on the mailinglist where people have had to question why they were getting unreliable data. On Sep 3, 12:25 pm, Matt Harris thematthar...@twitter.com wrote: Hi Michael, Soon after launching those fields we identified some problems with them so had to disable them. That means the behavior you are seeing is expected right now. When the fields are enabled again we'll announce it to this mailing list. Best, Matt On Thu, Sep 2, 2010 at 9:04 PM, Michael Babker mbab...@flbab.com wrote: Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I've retweeted using the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? Thanks! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Character limits on Direct Messages
It would appear that today Twitter began enforcing a 140 character limit on DMs. To my knowledge their was never a limit enforced before, and even Twitter.com would show up to 255 characters of a DM. Some Twitter clients, including mine, supported 140 char DMs and now I'm seeing people really upset that they can't send longer messages any more. To me this was a significant change and should have been announced to the developer community prior to being made. -Orian -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Rate limits for whitelisted IPs using user credentials
Is it possible to use a whitelisted IP to fetch data using a user's OAuth credentials without utilizing the user's 350/hr rate limit? For example, if I'm building a DM backup service, I'd like to be able to back up the user's DMs on their behalf without draining their rate limit. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Get resolved URLs?
Agreed, this would make a lot of sense for Twitter to return, especially as the t.co link wrapping gets rolled out. On Aug 6, 3:17 pm, Tom allerleiga...@gmail.com wrote: I agree - it would be nice to have this. Possibly as an entity? http://dev.twitter.com/pages/tweet_entities Tom On Aug 6, 6:35 pm, Brian Medendorp brian.medend...@gmail.com wrote: I can see that twitter itself must be resolving any shortened URLs somewhere, because if you search for a domain name (such as amazon.com), you get a bunch of results that don't seem to match until you resolve the shortened URL in the tweet and see that it points to the domain you searched for, which is fantastic! However, I am wondering if there is any way to get those resolved URLs from the API, or (better yet) if there is anyway that those URLs could be exposed in the search results themselves. Currently, I am resolving the URLs myself by requesting the URL and saving the resulting location, but that starts to take a while when there are a lot of results returned.
[twitter-dev] Re: Get just the IDs for a lists members
Yeah, this was actually requested in the issue tracker back in December: http://code.google.com/p/twitter-api/issues/detail?id=1296 On Jul 19, 10:23 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There's no way to get this at this time, but it'd be a good feature to request on the issue tracker:http://code.google.com/p/twitter-api/issues/list On Sun, Jul 18, 2010 at 2:09 PM, Dharmesh dharme...@gmail.com wrote: I'm looking to do do some analysis on twitter lists. I'd like to be able to retrieve the list of all users that are members of a list -- but all I need are the User IDs. Is there a way to get a list of members (up to 5,000) like we can with the call followers/ids and friends/ids? Right now, we can only retrieve 20 members at a time -- which requires many API calls for large lists and wastes bandwidth as I don't need all the user data. Thanks.
[twitter-dev] Re: Get Twitter replies since
I assume you mean you're using statuses/mentions to retrieve the tweets you're looking for. If you want to get just the most recent mentions since the last time you fetched them, you should pass the id of the most recent mention you have in the since_id parameter. You can't send it a timestamp. Here is the documentation: http://dev.twitter.com/doc/get/statuses/mentions On Jul 14, 4:22 pm, Sillysoft liquidcha...@yahoo.com wrote: Perhaps Im not understanding this correctly but I am using the Twitter API to grab the replies from my twitter account. The problem is I dont want to grab the same ones so Im trying to use the since variable but no matter what value I use for the since variable in the url it always comes back with the same replies. For example: http://twitter.com/statuses/replies.xml?since=Tue%2C+27+Mar+2011+22%3... I did this as a test, I was assuming the since variable meant show all replies that have been added since Tues March 11 2011. If that is correct then it should come back with 0 results correct? Well right now it is coming back with the same results as if I am not using the since variable. Anyone point me in the right direction?
[twitter-dev] Re: since_id confusion
Try calling without the count parameter. The page and count parameters may not work properly with since_id, and since_id may not work properly if the id you pass results in too many tweets. :/ On Jun 27, 3:17 am, Terence Eden terence.e...@gmail.com wrote: To make this slightly clearer Imagine I have retrieved a page with 20 statuses. Status IDs are 60 ... 40 Calling the timeline with max_id=40count=20 allows me to step back in time. It gives me 40 ... 20 Suppose I just want to see *next* 20 tweets since status_id 60? I would expect calling the timeline with since_id=60count=20 to give me 80 ... 60 It doesn't. It gives me 100 ... 80. That is, the 20 most recent tweets from *now*. I want the reverse of that. The 20 tweets from *since_id*. Is there any way to get that? I don't want to call the 200 most recent tweets and try to find the 20 I'm looking for, partly on bandwidth processing grounds, but also, if the user is, say, 300 tweets deep into their timeline, they'll miss tweets. Thanks Terence On Jun 26, 3:52 pm, Terence Eden terence.e...@gmail.com wrote: Am I mistaken in how since_id works? Callinghttp://api.twitter.com/1/statuses/home_timeline.json?count=20max_id=... Gives me the *next* 20 tweets from 1234 However, calling with since_idhttp://api.twitter.com/1/statuses/home_timeline.json?count=20since_i... Gives me the *first* 20 tweets in the timeline. I was expecting it to show the 20 tweets *from* 1234 Am I the only one with this confusion? Or is there a better way to just retrieve the first 20 tweets which have occurred since? Thanks T (Essentially, I'm implementing older and newer buttons which always show older/newer tweets, rather than pages.)
[twitter-dev] Re: How to compute the user list membership count
Yeah, this was requested a few days after the official list rollout, back in November (seven months ago): http://code.google.com/p/twitter-api/issues/detail?id=1186 It's been marked as an enhancement even though it has seemed to exist on Twitter.com this entire time. On Jun 22, 2:56 pm, Alfredo Artiles aarti...@gmail.com wrote: Hi, Is there any way to count the user lists membership other than iterating with the /:user/lists/memberships method? All the best, --- Alfredohttp://e24apps.com fd1b63583b fd1b63583b
[twitter-dev] Re: 4 Listed How can i get that number from an api call?
This was brought up pretty much the day lists came out of beta back in November, but still hasn't been addressed in the API. There are two issues logged in the tracker: http://code.google.com/p/twitter-api/issues/detail?id=1176 http://code.google.com/p/twitter-api/issues/detail?id=1186 On May 21, 1:07 pm, adamjamesdrew theikl...@gmail.com wrote: any ideas? On May 19, 8:32 pm, adamjamesdrew theikl...@gmail.com wrote: Thanks
[twitter-dev] Re: Twitter Crossdomain.xml issue
I've been asking Twitter to review the crossdomain.xml situation for months. You can find old threads on the issue by searching this forum. @raffi has said he elevated the issue to the security team for review. I'm sure they've been mulling it over day-and-night :) In the meantime you will indeed need to use a proxy, and there are lots of examples out there for creating PHP proxies. Here is one to get you started: http://www.switchonthecode.com/tutorials/using-a-php-proxy-with-flex-to-talk-cross-domain You'll have to extend that a bit if you want to pass parameters from Flex to your proxy and then on to Twitter. On May 18, 8:09 am, AndyCatch andrew.ca...@gmail.com wrote: Hello there, My name is Andy, and I'm a Flash Developer. I have been using the Tweetr/SwfJunkie library, and recently when I updated/uploaded my site recently, I got: Ignoring 'secure' attribute in policy file fromhttp://twitter.com/crossdomain.xml. The 'secure' attribute is only permitted in HTTPS and socket policy files. Seehttp://www.adobe.com/go/strict_policy_filesfor details. Now, having done a little research I found this thread from 2008: http://groups.google.com/group/twitter-development-talk/browse_thread... In which a talented Flash Dev named Kris Temmerman mentions using a server side php script on your own domain to connect to the api. He also mentions a nice php class in the docs. a) Can anyone point me to any tutorials/resources that will help me create such a script? I've googled proxy php, data php, server side script and many more but I can't even tell if it's the right thing to be looking at. b) Long shot, but these docs that Mr Temmerman mentions...where might they be? As far as I can tell, though I'm no expert, the problem is stemming from the Twitter Cross Domain policy. Have there been any resolutions that anyone knows of? I've done a lot of digging, but can't really find anything more than a few bug logs, and old forum threads. Any help/advice would be very much appreciated. Kind Regards, / Andy
[twitter-dev] Re: users/show bug with nested user object
I'm still seeing the errant userid/user node at noon EST. On May 6, 10:03 am, janole s...@mobileways.de wrote: Just as a follow-up, I've just seen a userid/user again while doing a verify_credentials.json call after I've retweeted some user. The userid/user entry is inside the status entry of the calling user's user entry. Oh, complex. It's like: user status retweeted_status.../retweeted_status userid/user /status /user Here's the link to the data:http://data.mobileways.de/brokentweet.txt Ole -- Jan Ole Suhr s...@mobileways.de On Twitter:http://twitter.com/janole On 6 Mai, 15:18, Taylor Singletary taylorsinglet...@twitter.com wrote: It's taking a long time. We're investigating possible means to hasten the resolution and any other reasons the cache might not be resolving. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Thu, May 6, 2010 at 3:17 AM, rohit mrro...@gmail.com wrote: Seems like the cache has still not cleared. Regards, Rohit On May 6, 6:14 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The bug is fixed. The cache, however, has to negotiate its way through the dusty corridors of memory. Please let us know if you don't see a significant improvement in regards to the impact this had on your applications within a reasonable amount of time. Sorry about the mess. Taylor On Wed, May 5, 2010 at 2:02 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Folks, We've identified the bug where an inner user object is being passed with the current status on users/show, are working on a fix and will have a deploy go out as soon as we can. Thank you for your patience. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
[twitter-dev] Re: User tag inside users/show
This totally just broke my app as well. Twitter please change this back ASAP! On May 5, 4:39 pm, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard
[twitter-dev] Re: User tag inside users/show
This broke for me because my app has logic that handles instantiation of User objects as it comes across them in XML. The addition of a new user node that contained nothing but an id broke this. Sorry Taylor but this is different than adding a new field that doesn't already have an existing meaning / structure. On May 5, 4:42 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Looking into it. Sorry about the chafe. While the versioning in the API is important as noted, we continually stress that API clients need to be resilient to new fields appearing on any node. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Wed, May 5, 2010 at 1:40 PM, Orian Marx (@orian) or...@orianmarx.comwrote: This totally just broke my app as well. Twitter please change this back ASAP! On May 5, 4:39 pm, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard
[twitter-dev] Re: User tag inside users/show
Well, I'm not sure if Rich was referring to the output per se or rather that this bug was probably tied to the skip_user parameter that was just added to timelines... which one could argue is a candidate for versioning. On May 5, 5:02 pm, Raffi Krikorian ra...@twitter.com wrote: versioning has absolutely nothing to do with this - this is clearly a bug. On Wed, May 5, 2010 at 1:39 PM, Rich rhyl...@gmail.com wrote: Oh I'll add, I thought the point of a versioned API was that this sort of thing didn't happen? On May 5, 9:37 pm, Rich rhyl...@gmail.com wrote: I noticed today inside the user tags an extra user tag has appeared We now have user-status-user This is causing a crash on my app and number of engines I've tried. When did this get added and did I miss the notification? Many thanks Richard -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: get public replies (or mentions) to following
You could try requesting an invite here: http://api.replyto.it/ On Apr 28, 11:57 pm, athanhcong athanhc...@gmail.com wrote: Hi all, In my apps, I want to (1)get all recent official replies (or mentions) to my following and also the tweet's ids that replies reply to OR (2)get all replies to a tweet I found that I can use search API to get all recent replies to a username or m, but the results don't give me the tweet's id that each search result reply to. To get that id I need to use statuses/show/ id API to get full information of result-tweet. But this approach costs a lot of requests to server. Do you have any idea to solve this? Thanks.
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
So no one else would find this useful? On Apr 20, 12:34 pm, Orian Marx (@orian) or...@orianmarx.com wrote: I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url:http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: User Stream's API usage
Being able to retrieve a list of unfollows a user performed since some point in time would be hugely valuable for anyone trying to maintain an up-to-date record of a user's connections without regularly having to refetch all the ids. Is there any way this could be accomplished, perhaps as a REST endpoint? On Apr 21, 5:00 pm, Mark McBride mmcbr...@twitter.com wrote: We likely won't send down the unfollows in the short term, for reasons outlined previously. It's not that we won't *ever* do it, but it's delicate. On the user profile changes, that does seem like a good idea. No promises, but I'll look at what we can do. The highest priorities we have right now are 1) Getting the formatting of messages locked down 2) Getting list activity in (lists created/deleted/modified, users added to lists, etc.) ---Mark http://twitter.com/mccv On Wed, Apr 21, 2010 at 1:30 PM, Cameron Kaiser spec...@floodgap.com wrote: Also, unfollows should be treated the same as follows. I know its sad when an unfollow happens, but this is important information too. I disagree. I think unfollows should be totally without penalty, and making them visible/exposed could depending on the situation assign them a very heavy social penalty. Qwitter comes to mind. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- EH! STEVE! --- -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Good to hear. I've got more coming... :) On Apr 23, 11:39 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Fri, Apr 23, 2010 at 8:32 AM, Orian Marx (@orian) or...@orianmarx.comwrote: So no one else would find this useful? On Apr 20, 12:34 pm, Orian Marx (@orian) or...@orianmarx.com wrote: I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url:http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
I've actually never understood the value of having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). On Apr 23, 11:57 am, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 9:39 AM, Taylor Singletary wrote: Hi Orian, Definitely think it would be useful and I've added it to my bucket of useful API ideas. We're focused on a number of projects right now, but I'm definitely keeping track of good ideas like this one for when the team has some feature selection flexibility in the future. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod Do we want one endpoint or two endpoints, one for all direct messages sent to a particular account and one for all direct messages sent from a particular user (maybe a filter on the current direct messages endpoint, perhaps)? -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] [Feature Request] friends/screen_names and followers/screen_names
It would be useful to have endpoints for retrieving user screen names 5000 at a time just like with friends/ids and followers/ids. The primary use case I see for this is for twitter clients to be able to easily provide screen name auto-complete based on a user's connections (without having to load up the full user objects using statuses/ friends and statuses/followers). -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Feature Request: Retrieve direct messages between requester and a single user
Sure, yeah. But I would argue that DMs make more sense to be viewed by default as a stream of back and forth messages vs a separate history of sent and history of received. I would say it makes more sense to offer it as one endpoint to be split client side rather than two endpoints to be merged client side. Of course, the current situation is they are split and I'm sure there is some historical reason for that and I wouldn't expect it to be changed. But in terms of a new endpoint specifically for retrieving a history of conversation with a particular user I don't really see what the benefit would be of serving it up split (to the consuming application). On Apr 23, 1:04 pm, John Meyer john.l.me...@gmail.com wrote: On 4/23/2010 10:58 AM, Orian Marx (@orian) wrote: f having two endpoints for sent / received DMs in the first place, as you end up needing to make two calls and then sort everything (if you're trying to show a stream of DM conversations). But if you're not making them into a conversation it makes more sense (i.e. a history). -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Feature Request: Retrieve direct messages between requester and a single user
I think it would be incredibly helpful to have an endpoint where we could request direct messages sent back and forth between an authorized user and some other user. This would make it significantly easier to allow users to move backward through conversations with a single user. Right now the only alternative is potentially making lots of calls to direct_messages and direct_messages/sent hoping to come across dms specific to that one user. I imagine this endpoint would look like this: url: http://api.twitter.com/1/direct_messages/between.xml(json) parameters: * user_id. Specifies the ID of the user whose private conversations with the authenticated user should be returned. * screen_name. Specifies the screen name of the user whose private conversations with the authenticated user should be returned. * since_id. Optional. Returns only direct messages with an ID greater than (that is, more recent than) the specified ID. * max_id. Optional. Returns only statuses with an ID less than (that is, older than) or equal to the specified ID. * count. Optional. Specifies the number of direct messages to retrieve. May not be greater than 200. * page. Optional. Specifies the page of direct messages to retrieve. It would also be helpful to have an endpoint that retrieved new dms sent or received since some id, instead of having to make calls to two endpoints as we currently do, but I imagine user streams probably covers this need. @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Privacy issues with the proposed annotations feature
I think Brian brings up some interesting points. What this reminds me of is the machine identification codes secretly being including in every page printed by personal use printers ( EFF article here: http://www.eff.org/wp/investigating-machine-identification-code-technology-color-laser-printers ). Annotations could potentially be used to add a lot of tracking information users might not be happy with. What happens when a developer decides to attach the user's OAuth info to their tweets for whatever dumb reason? I think these are interesting questions, though I'm not sure Twitter can do too much about them in advance without severely restricting what annotations has the potential for. Twitter is taking a wait-and- see approach to what developers do with annotations and I think that it probably the right one for now. @orian On Apr 18, 8:23 pm, Brian Smith br...@briansmith.org wrote: Right now the web UI exposes every piece of metadata in a tweet to end-users. That is, an end-user can use twitter.com to check the complete contents of tweet sent by an application. I didn't see anything in the proposals regarding the annotation feature that says that users will be able to see all the annotations through the web UI. And, even if they could see them, chances are they couldn't understand them. And, even if end-users could understand them, applications will be able to use encryption and other obfuscation to make them impossible to interpret. This reduces the amount of control users have over their tweets. Right now an application cannot disclose the user's location in a tweet, except by putting the location information in the tweet text (which the user can see very clearly), or by putting the location information in the built-in geo feature. The ability for applications to expose the user's information is controlled by a preference that can be controlled only by the official web interface on twitter.com. However, with the annotations feature, applications will be able to expose the user's location-again, possibly encrypted or otherwise obfuscated-even when application access to the location feature is disabled. It doesn't make sense to disable an applications' access to the geo feature and then let it silently and undetectably disclose the user's location-perhaps in even more detail than the built-in geo feature allows. I think there must be some kind of control mechanism in place for annotations, or the web UI must present all the annotations of a user's tweets to that user, or both, in order to prevent the annotations feature from becoming a side channel for applications to communicate users' private information without users' knowledge or consent. I would like to know more about how this is going to be done. Thanks, Brian -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Get user profile pic by name, unauthenticated?
Why not? You know people are just going to continue to ask for it ;) On Apr 18, 6:36 pm, Raffi Krikorian ra...@twitter.com wrote: we don't support the original in this endpoint - just the three that you listed. On Sun, Apr 18, 2010 at 3:33 PM, Abraham Williams 4bra...@gmail.com wrote: Mini, normal, and bigger are work but what about original? Abraham On Sun, Apr 18, 2010 at 13:37, Raffi Krikorian ra...@twitter.com wrote: http://api.twitter.com/1/users/profile_image/raffi?size=bigger we will document this endpoint this week. On Sun, Apr 18, 2010 at 1:34 PM, WBC wooden.brain.conce...@gmail.comwrote: Thanks Raffi... I knew there had to be something more simple! Is there a way to get the bigger image? I can parse the HTML and just replace _normal with _bigger of course... Anyway, cheers. On Apr 18, 8:50 am, Raffi Krikorian ra...@twitter.com wrote: e.g.http://api.twitter.com/1/users/profile_image/raffi On Sat, Apr 17, 2010 at 9:41 PM, WBC wooden.brain.conce...@gmail.com wrote: Hello all, please forgive a newbie here. I would like to accomplish one simple task as described in the title: get the URL of a user profile picture by user name, in the context of a Mac application. At this time (and in the foreseeable future) I have no interest in doing more with the API(s). I do not want to ask users to authenticate with their own accounts for this simple purpose, and I don't want to run into an application-based rate-limit for my distributed, desktop application. I do plan to cache and honestly I can't imagine more than 50 calls a WEEK per IP for this purpose. I assume based on this from the FAQ: The REST API does account- and IP-based rate limiting. Authenticated API calls are charged to the authenticating user's limit while unauthenticated API calls are deducted from the calling IP address' allotment. ... that the user's IP is the one deducted if unauthenticated, which is perfectly fine. But the search API requires authentication: http://api.twitter.com/1/users/search.xml?q=username I've spent quite a lot of time trying to figure this out already, so a simple yes, you can do it and here's the URL would be very kind. (I can easily accomplish what I want just by parsing some HTML... but I thought I'd try to be legit about it ;-) -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- 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 Teamhttp://twitter.com/raffi
[twitter-dev] Re: Favorites Error
Yeah I realized shortly after writing that that I was already handling this bug, and it was only that I just happened to be noticing it again and thinking that it was a recent occurrence :-) On Apr 15, 12:14 pm, btjones btjo...@gmail.com wrote: FYI, looks like this bug was submitted quite a while ago. http://code.google.com/p/twitter-api/issues/detail?id=855q=favorites... On Apr 14, 5:47 pm, btjones btjo...@gmail.com wrote: This is happening for me as well. The problem can be easily recreated with the Twitter API explorer:http://twitapi.com/explore/favorites-create/http://twitapi.com/explor... -Brandon On Mar 30, 7:26 pm, Orian Marx (@orian) or...@orianmarx.com wrote: It seems thatfavorites/createandfavorites/destroy are no longer returning tweets with a properly updated favorited node. If I try to favorite a tweet, theresponsecomes back with favorited = false, but if I re-fetch the tweet immediately after it comes back as favorited = true. It was not working like this until very recently. Anybody else getting this? Thanks, @orian -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Thoughts moving forward
Anyone else want to join in on this? Ryan wants to chat about specifics in the 10:15 am session of the Hack Day, so I agree with Abraham that it makes sense to try and meet some time on Day 1 to collect some thoughts. I'm sure we'll have a lot of new info to digest as well. On Apr 12, 4:31 pm, Abraham Williams 4bra...@gmail.com wrote: I'm looking forward to Chirp and the dialogs that will happen. The Coop session on the second day looks to be the best time to have a heart to heart between third-party developers and the platform team. I think it would be good to have the third-party developers meet before then have a discussion about what we want and what our priorities are. I'm not sure when the best time would be. During the afternoon break or at 9pm on the first day seem like good times. I also think it would be respectful of Twitter employees to not attend this gathering so developers can be frank and honest. There will be many other opportunities. Abraham -- Abraham Williams | Developer for hire |http://abrah.am PoseurTech Labs | Projects |http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What's happening with Tweetie for Mac
This is certainly a risk we all face. However in my mind there are ways Twitter can do a better job in indicating where we should and should not concentrate effort. For example, there are things that Twitter has had in its V2 roadmap for years now, and some of us have decided to try and implement them on our own. If Twitter was willing to set even very rough priorities for things and very rough estimates (soon is not a rough estimate) that could go a long way in preventing us from wasting our time. Obviously they aren't going to tell us in advance of major new functionality, but I'm referring to functionality they have already indicated they would like to tackle at some future point On Apr 12, 3:23 pm, Jesse Stay jesses...@gmail.com wrote: Not at all - I've spent 3 years building features constantly replaced by Twitter (or killed due to Twitter changing the TOS). I've been there, and had plenty of my share of crankiness - I guess I'm used to it now, and I realize that's just a part of writing apps for the ecosystem (or any 3rd party ecosystem for that matter). The more Twitter can be transparent about things like this, the happier I am. I'm glad they're starting to open up on where they stand. I hope this continues. Jesse On Mon, Apr 12, 2010 at 11:12 AM, Isaiah Carew isa...@me.com wrote: sorry for being cranky, but i just spent a year building a tweetie competitor. you can't fault a guy for saying ouch while your knife is still sticking out of his back, right? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
[twitter-dev] Re: Twitter Stream crossdomain.xml
I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off of www.twitter.com malicious Flash code could potentially get at user's cookies from any browser sessions from visiting www.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.html http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.comwrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features,crossdomain.xml
[twitter-dev] Re: Twitter Stream crossdomain.xml
Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d3230be66c27c88e On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commalicious Flash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please seehttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... andhttp:// groups.google.com/group/twitter-development-talk/browse_frm/th... -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote
[twitter-dev] Re: Twitter Stream crossdomain.xml
w00t On Apr 12, 12:29 pm, Raffi Krikorian ra...@twitter.com wrote: yup - totally :P just giving you an update that its been low on our priority list :P twitter now has a dedicated security manager, so i have just elevated this to his attention. On Mon, Apr 12, 2010 at 9:27 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Totally understood. You shouldn't be relaxing any security on anything you're not convinced will remain secure. Just remember you and I started this conversation six months ago ;) http://groups.google.com/group/twitter-development-talk/browse_frm/th... On Apr 12, 11:43 am, Raffi Krikorian ra...@twitter.com wrote: as i said, unfortunately, i'm not comfortable relaxing the crossdomain file on api.twitter.com until we more carefully analyze our own stack that is running there. we completely agree with your statements here, and we will gladly listen to anybody who wants us to relax the file -- but, you're all preaching to the choir :P we want to relax the file! to be responsible, we need to carefully analyze our stack and write a few test cases first. On Mon, Apr 12, 2010 at 8:34 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I'm no security expert, but this continues to make little sense to me. I believe it is possible to do nasty things using the crossdomain.xml file, just as it is possible to do nasty things with lots of other approaches. My understanding is that having a separate domain for the api now significantly reduces any security risks of placing an unrestricted policy file on that domain. The main issue I think was that when the api was served off ofwww.twitter.commaliciousFlash code could potentially get at user's cookies from any browser sessions from visitingwww.twitter.com. There aren't any cookies kept for visits to api.twitter.com. Oh and lets not forget OAuth has been added now. These policies were in place since before OAuth was in effect I believe. Here are two resources that should be passed to your security team: http://www.adobe.com/devnet/flashplayer/articles/cross_domain_policy.. .. http://www.adobe.com/devnet/flashplayer/articles/secure_swf_apps.html I will definitely be pushing for this to be addressed at Chirp, so it would be great if someone could start looking into it now :-) On Apr 12, 10:03 am, Raffi Krikorian ra...@twitter.com wrote: - there should be a very permissive crossdomain.xml file on search.twitter.com; - the firehose does not host a crossdomain.xml file for its production usage; and - twitter.com and api.twitter.com have restrictive crossdomain.xml files. to my understanding (but correct me if i'm wrong), it is possible to do some nasty things regarding cookies between web applications when crossdomain.xml files get involved. twitter.com will probably remain to have a restrictive policy, but we have wanted for a while (but haven't gotten around to it yet) to do a security audit of api.twitter.com before relaxing the file there. i apologise for the inconvenience. On Mon, Apr 12, 2010 at 5:04 AM, Martin Heidegger mastakan...@gmail.com wrote: To me this step makes very few sense. This API is already public - all data served by this api is public - flash programmers or not. Programmers start to create twitter.api proxys infrastructure that reads data from this api and serves just to work around the crossdomain.xml. It is also possible to work-around this with javascript bridges. With some around-the-corner-thinking most flash applications should work. To me this is unnecessary hazzle for a lot of developers that doesn't really stop them doing anything that they would without this restriction (well - it might reduce the responsetime and the quality of their applications). And for what? To avoid or some temporary load difficulties? This API is online/live for more than a year now. I hope you reconcider opening it soon. yours Martin. On Mar 19, 8:53 pm, Orian Marx (@orian) or...@orianmarx.com wrote: John, thanks for the response. This makes sense. While I do trust that the existingcrossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non
[twitter-dev] Re: Thoughts moving forward
This was the conclusion to my email to Ryan... a few actionable points: Immediate term: * Carve out a block during the Chirp hack day to engage with the developer community with the specific intent of figuring out ways to make the issue tracker and forums more effective. (The conference shouldn't be an entirely push experience for the Twitter team) * Carve out a block during the Chirp hack day to review the open issues in the issue tracker and reset priorities on open issues as a collaborative effort between the community and Twitter. (You will never have a better opportunity to do this in one shot) * Work *with the developers* to define the role of Developer Advocate. (I don't think there will be a better opportunity than Chirp for this one as well) Longer term: * Fill the newly defined Developer Advocate role. Provide a mechanism for the community to formally review the Developer Advocate's performance over time. (this is not about Taylor, he sounds like an awesome member of the team) * Scrap the V2 roadmap and replace it whatever kind of roadmap can have realistic estimates, and update the roadmap and its estimates as they change. If you need help figuring out how to build a better roadmap, I'm sure there are lots of folks with ideas they'd love to contribute. * Have upper management issue reflections on their respective areas of the company. Talk about what the company is doing well and what it's still struggling with. Don't b.s. these. It would be great, for example, to hear from you about whether or not new roles need to be filled and why. On Apr 12, 4:31 pm, Abraham Williams 4bra...@gmail.com wrote: I'm looking forward to Chirp and the dialogs that will happen. The Coop session on the second day looks to be the best time to have a heart to heart between third-party developers and the platform team. I think it would be good to have the third-party developers meet before then have a discussion about what we want and what our priorities are. I'm not sure when the best time would be. During the afternoon break or at 9pm on the first day seem like good times. I also think it would be respectful of Twitter employees to not attend this gathering so developers can be frank and honest. There will be many other opportunities. Abraham -- Abraham Williams | Developer for hire |http://abrah.am PoseurTech Labs | Projects |http://labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What's happening with Tweetie for Mac
I've spent eight months on a new Twitter client myself, and I had planned to start showing it at Chirp. Mine is in-browser so I suppose it's not quite the same situation, but in reality I do think they are all, for the most part, in competition with each other - no? On Apr 12, 1:12 pm, Isaiah Carew isa...@me.com wrote: sorry for being cranky, but i just spent a year building a tweetie competitor. you can't fault a guy for saying ouch while your knife is still sticking out of his back, right? isaiahhttp://twitter.com/isaiah On Apr 12, 2010, at 9:10 AM, Jesse Stay wrote: I think it's great that Twitter is finally being more transparent about all this. I could argue they need to be more transparent (where do they plan to go in the analytics and enterprise spaces?), but it's about time. They've finally drawn the line in the sand - now we need to adapt. Yes, it's frustrating, but then again, 90% of businesses fail - it's the risk all of us took. We either compete, or quit, and move on. I don't get all the complaints - this is nothing new. I've had half my features replaced by Twitter over the last few years (quite literally - just read my blog - I'm the chief complainer). By now I realize that's either part of life (note: it's the same on Facebook, too - there's no escaping it), or I change my focus to where Twitter is not my core and I instead use Twitter to strengthen my new core. That's where Twitter (and Fred Thompson) have made it clear they want us to go. Finally, some clarity. I'm appreciative of it, regardless of how frustrating it can be. Time for all of us to take this constructively and adapt. Just my $.02 FWIW... Jesse On Mon, Apr 12, 2010 at 9:54 AM, Isaiah Carew isa...@me.com wrote: Crystal clear. 1. You're decimating the client market on every platform but Windows. 2. You're killing any potential for innovation or investment. 3. You have no clear (public) plan for any innovation yourself. What marketing genius... Oh never mind. It's not worth the breath. Good luck with that. Anyone want a chirp ticket? isaiah http://twitter.com/isaiah On Apr 12, 2010, at 7:40 AM, Ryan Sarver wrote: One more from me. People have been asking for specific details around Tweetie for Mac and I wanted to make sure we clearly message our plans as we know it. To be clear, Tweetie for the iPhone and it's developer, Loren Brichter, were the focus of our acquisition, but as part of the deal we also got Tweetie for Mac. Loren had been hard at work on a new version of Tweetie for Mac that he was going to release soon. Our plan is to still release the new version and it will continue to be called Tweetie (not renamed to Twitter). We will also discontinue the paid version. Hope that's clear. Please let me know if you have any questions. Best, Ryan
[twitter-dev] Re: What's happening with Tweetie for Mac
I seem to remember some debate over how uberTwitter comes out with such a large share in that analysis, but either way everything I have seen has pointed to 40% of tweets posted coming from Twitter.com. In my mind it would be smart for people to think about how to get market share from that piece of the pie. I'm not sure I see a significant distinction between Twitter-only clients and clients that aggregate other services in terms of whether or not they are in competition with each other. On Apr 12, 6:37 pm, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/12/2010 01:58 PM, Orian Marx (@orian) wrote: I've spent eight months on a new Twitter client myself, and I had planned to start showing it at Chirp. Mine is in-browser so I suppose it's not quite the same situation, but in reality I do think they are all, for the most part, in competition with each other - no? Yes, there is a competition - two competitions, in fact: 1. Clients that interface only to Twitter, and 2. Clients that interface to Twitter and other services. If we narrow the field to Twitter-only clients, the stats are very clear:http://twitter.comhas the lion's share of the tweet count, with uberTwitter a distant second and TweetDeck third. Seehttp://tdash.org/stats/clientsfor the numbers. Tweetie is number 11 on the list - *1.39%* of all the tweets posted come from Tweetie! In short, Twitter clients are jockeying for position in a crowded field with 39.31% of the usage already subtracted out by Twitter's main web page. See Which Twitter Clients Do People Actually Use?http://meb.tw/9iRfxUfor some analysis. -- M. Edward (Ed) Boraskyhttp://borasky-research.net/m-edward-ed-borasky/@znmeb I've always regarded nature as the clothing of God. ~Alan Hovhaness -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Bulk User Relationship Lookup?
Sorry, late night stupidity was in effect. I was sending up message ids instead of message sender ids :-) It's all working great. On Apr 11, 6:35 am, Raffi Krikorian ra...@twitter.com wrote: really? that's interesting. i have tests for it working in oauth can you send me details, please? On Sun, Apr 11, 2010 at 12:38 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Also, does this endpoint support oauth? I seem to be having trouble making an oauth request to it vs basic-auth. On Apr 9, 12:17 pm, Raffi Krikorian ra...@twitter.com wrote: at the risk of introducing features instead of fixing bugs, this endpoint may also be of use -- its a work in progress, and a few details of it may change: http://api.twitter.com/1/friendships/lookup.xml?user_id=813286,783214 On Wed, Mar 31, 2010 at 8:02 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.com wrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/README Abraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply
[twitter-dev] Re: Bulk User Relationship Lookup?
Any way I can specify a target other than myself for who to lookup relationships against? On Apr 9, 12:17 pm, Raffi Krikorian ra...@twitter.com wrote: at the risk of introducing features instead of fixing bugs, this endpoint may also be of use -- its a work in progress, and a few details of it may change: http://api.twitter.com/1/friendships/lookup.xml?user_id=813286,783214 On Wed, Mar 31, 2010 at 8:02 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.com wrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/READMEAbraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Bulk User Relationship Lookup?
That's awesome. I'm putting it to use this weekend. (fully understanding the caveat that it might change) On Apr 9, 12:17 pm, Raffi Krikorian ra...@twitter.com wrote: at the risk of introducing features instead of fixing bugs, this endpoint may also be of use -- its a work in progress, and a few details of it may change: http://api.twitter.com/1/friendships/lookup.xml?user_id=813286,783214 On Wed, Mar 31, 2010 at 8:02 AM, Orian Marx (@orian) or...@orianmarx.comwrote: I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.com wrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/READMEAbraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Chirp is coming to San Francisco April 14 and 15
If nobody tweets about it it didn't really happen :-) On Apr 7, 1:51 am, M. Edward (Ed) Borasky zn...@comcast.net wrote: On 04/06/2010 03:30 PM, Abraham Williams wrote: On Tue, Apr 6, 2010 at 15:06, Jonathan Strauss jonat...@snowballfactory.com wrote: Secondly, is there a wiki or something for coordinating among Chirp Hack Day participants? Twitter.com? :-P What if the brightest and best Twitter developers gathered for two days in Twitter's home town and *nobody* tweeted a single tweet about it? ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
Raffi, one of the things that really stands out for me in what you are saying here is that there are lots of moving pieces that the team is trying to align quickly. The question is, who and what is dictating the schedule? I get the sense that all the recent changes are parts of a bigger picture plan for Twitter, but the reality is that Twitter HQ has not conveyed a real sense of this bigger picture to the developer community - and it certainly hasn't conveyed why these recent changes need to align quickly. So inevitably the situation at hand seems to be that some serious developer concerns effectively need to be pushed aside in order to meet some internal goals of Twitter that have not been made public. I can understand that as a choice that Twitter management might make. What I think would be unreasonable would be for Twitter to expect the developer community to not push back. I think it's pretty clear that the developer advocate concept needs to be fleshed out more, and i'll try to push for that at Chirp. If anyone else is interested in helping make that discussion productive, lets get started :-) On Apr 5, 8:45 pm, Raffi Krikorian ra...@twitter.com wrote: to clarify (from my personal view), what taylor has provided to the team is a clear view into what developers want / think / feel -- basically, a pulse on the developer community. he's doing a fine job. and for these particular issues, not only has he conveyed the feelings of our community, but everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. On Mon, Apr 5, 2010 at 5:01 PM, Dewald Pretorius dpr...@gmail.com wrote: To be fair to Taylor, we may be expecting too much from his role. When reading the job description of a Twitter Developer Advocate [1], the only traditional advocate responsibility listed there is Represent developer needs when planning new API features and changes. Now, if Taylor conveyed our objections to the Platform team, then he adequately executed that responsibility. I'm sure he did. The rest of the responsibilities all speak in a Twitter to Developer direction, i.e., more a Communicator than an Advocate. In particular, in the About This Job section, it says, it is necessary to have an official voice regularly communicating with the community, which underlines Communicator instead of Advocate. [1]http://dld.bz/7Z On Apr 4, 9:39 pm, funkatron funkat...@gmail.com wrote: Taylor, I'm about to vent. Sorry about this. At some point did you plan on addressing any of the numerous complaints raised against making this anything other than opt-in? Several of us raised this, and you offered no response for 10 days. See http://groups.google.com/group/twitter-development-talk/ browse_thread/thread/983086ae9935d50c/d4a8e0fbc0fee5c0? lnk=gstq=popular+search#d4a8e0fbc0fee5c0 When you *did* post, you didn't actually address any concerns, or say hey, I spoke with the API team. This is why it's going like this. Like, say, an advocate of 3rd party developers would do. I'm not doing Twitter any favors; I realize that. I'm just the developer of a tiny, old open source client whose been hacking away on the API since spring of 2007. I'm not a strategic partner, and I don't bring Twitter any value. No VC funding will be coming my way, I'm afraid, and it doesn't make headlines on TechCrunch when I add a new feature (ping.fm? I supported that in 2007). But what I would like is to be treated with some respect. If you post something, and get significant pushback, I'd expect at *very* least some explanation about why doing it the way you guys want to do it is a great idea. If you are an advocate for 3rd party developers, as I interpreted your title, then doing us the courtesy of not simply ignoring/avoiding the concerns we voice seems like part of your job. It seems like you're doing a lot of selling of changes to *us*. That's not an advocate -- that's an evangelist. If your role there is an evangelist, then fine. You're doing a good job of ignoring the tougher questions and sticking to company lines. The point here is that I used to cut the API crew a lot of slack because I thought they at least weren't feeding us a line. I felt they actually were aiming for transparency, but were just overworked. If this is the way things are gonna go with someone who is, presumably, tasked with being *our* advocate, I think Twitter is losing the thread. Maybe it doesn't matter for you guys financially, and you'll go on and do
[twitter-dev] Re: Lists count in User object
Yeah this was logged in the bug tracker I think the day lists were rolled out to the public, but it looks like it never received an official response and is still marked as a new entry. :( http://code.google.com/p/twitter-api/issues/detail?id=1186 On Apr 1, 5:16 pm, DustyReagan dustyrea...@gmail.com wrote: I was wondering if it'd be possible to get the number of lists a user belongs to returned in the User object. I noticed the list count is displayed beside status, follower, and following counts all over Twitter, looks like the list count may be on the same level as the other counts. I'd like to include the list counts in my application without making additional API calls. Possibility?
[twitter-dev] Re: Bulk User Relationship Lookup?
I would certainly be interested in such a list, but no I don't think Twitter will be providing one. On Mar 30, 9:26 pm, mcfnord mcfn...@gmail.com wrote: Hi, Abraham, and everyone. I'm crawling twitter. (But who isn't, right?) Us social graph geeks have our own advantages, and our own set of challenges. For example, I would not want to manage the vastness of tweet volumes. But I do get neck-deep in social graph data. Which means I crawl with this:http://twitter.com/friends/ids.xml/?user_id=12345 x20,000/hr. so far i've discovered existance of 51 million accounts, and examined 13 million of these. if i need two scrapes to determine account activity, then i've got just 89 million captures to go! that's 6 months at full speed. inactive accounts can live with a vastly slower refresh cycle. so really what would benefit me (and twitter, as i see it) is a cheat sheet of active vs. inactive accounts. download the file, and know the integers within it are active accounts. in one move, through occasional publication of one file, twitter saves 6 months of scrapes for anyone who can leverage a quick-start list of which accounts are active, and which are inactive. i imagine people could, in many scenarios, limit their entire set of inquiries to these active accounts, saving millions of calls to twitter's api. maybe it's bad p.r. to state explicitly which accounts merit resources and which are dead. i guess once it's over i won't look back and perhaps it is i who can publish this dataset to some other newbie. but what a great efficiency for twitter to avoid this for everyone in my shoes. which are small shoes, i accept. best regards, john On Mar 23, 11:56 am, Abraham Williams 4bra...@gmail.com wrote: Bulk lookup of social graphs seems like it would be a pretty resource intensive call. I would not hold my breath for Twitter to implement it. Abraham On Tue, Mar 23, 2010 at 08:21,OrianMarx (@orian) or...@orianmarx.comwrote: Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/READMEAbraham On Mon, Mar 22, 2010 at 19:41,OrianMarx (@orian) or...@orianmarx.com wrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.- Hide quoted text - - Show quoted text - -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Bulk User Relationship Lookup?
Thanks Abraham, don't worry I'm watching Intersect closely ;) Unfortunately, this doesn't currently address what I'm getting at, namely, if I use the bulk user lookup, I'd like to similarly get accurate friend / follower info for each of those users (relative to the user making the bulk lookup) in one call. On Mar 22, 11:00 pm, Abraham Williams 4bra...@gmail.com wrote: I provide a simple API that returns common friends and follower of two specific Twitter users. It currently works for the 5000 most recent (although soon to be increasing) and only on public accounts. http://github.com/abraham/intersect/blob/master/README http://github.com/abraham/intersect/blob/master/READMEAbraham On Mon, Mar 22, 2010 at 19:41, Orian Marx (@orian) or...@orianmarx.comwrote: The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Bulk User Relationship Lookup?
The bulk users/lookup call recently added to the API is a great new tool for developers. This call would become even more useful with a corresponding bulk lookup for user relationships. Are there any plans for this? Also, I'm assuming that the following and notifications nodes returned in the user objects of the users/lookup call should be considered unreliable as is stated for users/show. Thanks, @orian To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? The crossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons. Given our current plans, it's going to be a little while longer before we can turn this on. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 10:29 AM, TarGz julien.ter...@gmail.com wrote: hi, I have prevriuosly work on twittearth.com and now I work a project that use the stream API. The stream API work very well, it is very responsive and powerfull and help me build a realtime geolocated search tool... The bad sing is that my Flash app only work offline because of the lak of crossdomain.xml Did you have plan to put ahttp://sream.twitter.com/crossdomain.xml file live soon ? because I love to share my tools with the world. Thank per advance for your answer(s) Looking forward for your reply To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Twitter Stream crossdomain.xml
John, thanks for the response. This makes sense. While I do trust that the existing crossdomain.xml policies were implemented out of a *concern* for user privacy and security, I don't believe they should remain as they currently are, and while the issue has been repeatedly brought to attention in this forum it has never had an official response other than we're thinking about it. I think a lot of Flash developers have been very patient with Twitter in this regard. Keep in mind we're not talking about some particular service call on an API being unavailable, but rather the entire non-search Twitter API. Twitter has addressed security concerns very well through OAuth. There is really no reason Flash apps should be restricted if they are making OAuth calls to the new api.twitter.com endpoints. For other discussions of this please see http://groups.google.com/group/twitter-development-talk/browse_frm/thread/e35a708400b529b3 and http://groups.google.com/group/twitter-development-talk/browse_frm/thread/d3230be66c27c88e?hl=entvc=1 -Orian On Mar 19, 2:17 pm, John Kalucki j...@twitter.com wrote: Currently the Streaming API is primarily intended for service to service integrations, and we've provisioned stream.twitter.com as such. We've also opened it up for all sorts of open-ended experimentation as well. However, we've asked large-scale deployments, such desktop apps and widgets, to hold off on releasing products against the Streaming API until we can provide a few more features (oAuth, etc.), provide sufficient capacity, and fully isolate desktop traffic from integration traffic. A single Hosebird process can pump out a lot of data. A cluster of them is a bit like a bull in a china shop. We want to avoid a success catastrophe where a set of popular clients releases all at once and inadvertently overwhelms the service and potentially knocks integrations and/or non-trivial slice of www traffic offline. This would be bad for everyone, including open experimental access. So, among a dozen other disabled features, crossdomain.xml is also off on stream.twitter.com. We're working on this right now. Please have patience. The crossdomain.xml policy on other endpoints is the doing of others, and I don't remember all the details. Please trust that the policies chosen were made with user privacy and user security as the primary concerns. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Fri, Mar 19, 2010 at 8:55 AM, Orian Marx (@orian) or...@orianmarx.comwrote: Am I interpreting this correct as saying out of capacity concern we're currently blocking Flash developers? The crossdomain.xml issue has been extremely frustrating across all of Twitter's service endpoints and if I'm interpreting this post correctly this just adds to a series of poor choices Twitter has made in regard to Flash developers in my opinion. If this service needs to be limited for capacity reasons it should be limited in the same way regardless of what technology you are using to make requests of the API. -Orian Marx Flex Developer On Mar 17, 1:50 pm, John Kalucki j...@twitter.com wrote: It's in the code, but turned off out of an abundance of caution for capacity reasons. Given our current plans, it's going to be a little while longer before we can turn this on. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 17, 2010 at 10:29 AM, TarGz julien.ter...@gmail.com wrote: hi, I have prevriuosly work on twittearth.com and now I work a project that use the stream API. The stream API work very well, it is very responsive and powerfull and help me build a realtime geolocated search tool... The bad sing is that my Flash app only work offline because of the lak of crossdomain.xml Did you have plan to put ahttp://sream.twitter.com/crossdomain.xml file live soon ? because I love to share my tools with the world. Thank per advance for your answer(s) Looking forward for your reply To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: Search crossdomain.xml accidentally deleted again?
I see it now too, but when I posted yesterday I was getting some error referring to Bucket does not exist or something like that. On Feb 27, 11:30 pm, Raffi Krikorian ra...@twitter.com wrote: My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. i still see it [ra...@tw-mbp13-raffi Desktop]$ wgethttp://search.twitter.com/crossdomain.xml --2010-02-27 20:29:27-- http://search.twitter.com/crossdomain.xml Resolving search.twitter.com... 168.143.162.59 Connecting to search.twitter.com|168.143.162.59|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 206 [application/xml] Saving to: `crossdomain.xml' 100%[=] 206 --.-K/s in 0s 2010-02-27 20:29:27 (16.4 MB/s) - `crossdomain.xml' saved [206/206] And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? yup. we have a few thing we want to make sure we do first, and then the plan is to loosen restrictions on api.twitter.com. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Search crossdomain.xml accidentally deleted again?
My flash application is currently getting security errors from search.twitter.com. It would appear the crossdomain.xml file no longer exists. This problem has happened before: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/d3230be66c27c88e/ And while we're at it... has the Twitter team thought more about loosening the restrictions in their crossdomain.xml files so that Flash developers can actually access the api without using a php or similar proxy? I brought this issue up in October: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e35a708400b529b3/
[twitter-dev] Re: @twitterapi meetup @ Twitter HQ
Seriously. I'd love to be involved in this but I already have to spend nearly a grand to fly over there from NYC to attend Chirp. How about a live feed? On Feb 26, 3:22 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote: Is there an on-line component to this? TweetChat? Or is it strictly a physical space event? -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos Quoting Ryan Sarver rsar...@twitter.com: Hey folks, We wanted to let you know that we're hosting a little developer gathering at our new offices this coming Monday afternoon. The meetup is meant to be an informal gathering of Twitter developers where we will be available to hear how we can improve and answer any questions you have. We'll give a quick state of the union of the platform and then open up for questions from both the audience and from people online. We want you all to build things that push us in ways we haven't been thinking about and we'd love to learn how we can provide a platform that helps you innovate. We'll be providing developer staples, like beer and pizza, and we'll leave a bunch of time at the end for everyone to mingle, meet each other and meet the whole @twitterapi team. We look forward to doing more events like this regularly in the future and look to improve them based on your feedback. *** Please note, while we would love to have everyone join us, space is limited to around 150 so you'll need to register on http://twitterapi-meetup.eventbrite.comand you'll need a confirmed ticket to get into the building. We look forward to hosting you here. Ryan
[twitter-dev] Re: @twitterapi meetup @ Twitter HQ
If TwitterHQ isn't opposed I'm sure there's someone who'd be willing to stream the event... On Feb 26, 5:31 pm, kosso kos...@gmail.com wrote: Out of interest, will there be any (legal?) reason why any of the attendants can't stream the meetup to UStream, for example? Also, do we need to bring a ticket, or will we sign in using OAuth? ;) heh On Feb 26, 2:19 pm, Ryan Sarver rsar...@twitter.com wrote: We won't be having a live video stream of the event this time around. We will be in the IRC channel and we'll be using Google Moderator to take questions from people both at the event and people who are remote. We'll walk before we run :) On Fri, Feb 26, 2010 at 12:42 PM, M. Edward (Ed) Borasky zzn...@gmail.com wrote: On Feb 26, 12:33 pm, Abraham Williams 4bra...@gmail.com wrote: A live feed would be awesome. Also the event says March 1st through April 1st... Ah ... an early April Fools' joke? ;-) I'm waiting for Linus Torvalds' April Fool email - I'm guessing this year he'll announce that he is buying Twitter ;-) But I'd settle for an IRC channel today and a Live from Twitter HQ broadcast in full streaming fashion at a later date ;-)
[twitter-dev] Re: listed count?
This issue was first brought up Nov 10 on the issue tracker but of course no response from the Twitter team. http://code.google.com/p/twitter-api/issues/detail?id=1186 On Feb 8, 6:26 pm, waukesha_area waukesha.a...@gmail.com wrote: Is it possible to get a count of how many lists a user belongs to? I am able to get the lists a user belongs to, page through them, and then get a count of them. That seems like a lot of work and bandwidth to find this out.
[twitter-dev] Re: Getting Replies to A Message
You should add your thoughts to
http://code.google.com/p/twitter-api/issues/detail?id=142
This would be a hugely beneficial addition to the API but of course
it's being completely ignored.
On Jan 20, 4:41 am, rob robert.bag...@gmail.com wrote:
Hello,
Questions regarding how to get replies to a tweet
What is the recommended way to do this properly?
A few things I have tried
{I am aware that there is no current way to use the search API and
grab all responses to a tweet (i.e by reply_to_status_id) [bummer].}
1. The search API using a to:someUsersince_id=
[theIdOfTweetIAmWatching]: this does not work since I have no
reply_to_status_id in the results to match up with.
2. API -- home_timeline: Requires the credentials for the user who
created the tweet [Which I may or may not have]
3. API -- user_timeline with the user_id from the tweet I am
watching: this does not include the tweets to the user
4. Cheat and have twitter to the
workhttp://search.twitter.com/search/thread/[theIdOfTweetIAmWatching] :
does not seem to support JSON or anything other than HTML or ATOM
5. Searched the list :)
I am just trying to get a handle on how to take a tweet that I get in
via a stream and go look [poll] for replies.
It seems I would need to follow the user using the streaming API and
match based on the in_reply_to_status_id but that would get quite out
of hand due to incoming tweet volume [i.e would need to follow a large
amount of users that may or may not ever produce a valid reply].
Thanks in advance,
Rob
[twitter-dev] List counts
User objects should have counts added to them for number of lists owned by, followed by and following the user. This does not seem to exist anywhere in the API currently, though clearly Twitter.com has access to the information (notice the counts at http://twitter.com/username/lists). Is this on the roadmap? No response from Twitter at either http://code.google.com/p/twitter-api/issues/detail?id=1176 or http://code.google.com/p/twitter-api/issues/detail?id=1186 (posted two months ago and which should probably be merged).
[twitter-dev] Re: favourites_count on user profile is not updated !
Has this been logged in the issue tracker? Seems like something that should be fixed. On Jan 20, 2:38 pm, Tim Haines tmhai...@gmail.com wrote: Ono, I think it's been this way for 8+ months? Tim. On Thu, Jan 21, 2010 at 1:14 AM, ono_matope matope@gmail.com wrote: Hi, Twitter team! I'm @ono_matope I made a fav-crawler that fetches favourite-feeds only when favourite_count of the user profile information (whitch is retrieved by or list members API) get increased. This mechanism will lat me crawl your data in less resouces. But I've noticed that the user's favourites_count attribute that retrieved by user/show or some other API does NOT to be updated even though he created a new favourite. Through some experiments, I found out following specifics. 1. When user created new favorites, his user info does NOT update. 2. That will be updated only when he tweets, follows someone or do some other activities but creates favourites. ...My new crawler development has been stuck : ( I would like to request that favourite_count attribute to be updated without any other activities, please. Thank you. @ono_matope
[twitter-dev] Re: When will delete list members and delete list be fixed?
Dear Team Twitter, I don't mean to be rude about this, but how can we expect that Twitter will role out an all new developer support center that's going to be more responsive when inquiries about a major defect in the API are left hanging for months on end? There is an open issue that is making list functionality completely unusable for a lot of people and has received zero comment from Twitter staff: http://code.google.com/p/twitter-api/issues/detail?id=1239 On Jan 11, 12:22 pm, Orian Marx (@orian) or...@orianmarx.com wrote: There has been an accepted defect in the issue tracker which really should be a high priority and there has been no word of any status on a fix. The defect is that any developers who cannot use a DELETE request were supposed to be able to make a POST request with a _method=DELETE param, but that has never actually worked. This leaves list management functionality *complete broken* for any client that cannot issue a DELETE request. This was first noted in November, and the defect was accepted one month ago:http://code.google.com/p/twitter-api/issues/detail?id=1239
[twitter-dev] Saved Searches API questions
Three questions: 1) Is there (/should there be) an update method for existing saved search in order to modify the query? I'm guess right now the only way to do this is to create a new query and delete the old one. 2) Is there a way to modify the name field? Right now it seems to just be a duplicate of query. 3) How is the position field supposed to be used?
[twitter-dev] Re: AS3 library comparison
I have been building a Flash app that uses OAuth authentication with Twitter. But before you even worry about that, you need to know that thanks to Twitters bizzare crossdomain.xml policy, you're going to need a PHP proxy or something similar in order to send your requests to Twitter. Flash in the browser cannot authenticate directly to Twitter thanks to their policies. Take a look: http://groups.google.com/group/twitter-development-talk/browse_frm/thread/e35a708400b529b3/a523a3f5e6c3d6a5?lnk=gstq=crossdomain#a523a3f5e6c3d6a5 That said, here are some resources that may be useful: http://soenkerohde.com/2009/07/high-level-as3flex-library-for-oauth-with-twitter-from-air/ http://www.iotashan.com/index.php/2008/04/28/oauth-actionscript-library/ On Jan 14, 5:02 pm, eco_bach bac...@gmail.com wrote: For a personal project I am building an AS3 only web based Twitter search and client application. According to Twitter's FAQ, they recommend using Oauth moving forward as a means of authentication. But from what I've seen (and please correct me if I'm wrong), 3rd party libraries (Tweetr, twitterscript, SWX) don't yet implement OAuth. Is anyone aware of any objective comparison between the various Actionscript Twitter libraries available? And can anyone point me to any live as3 web applications currently using Oauth?
[twitter-dev] When will delete list members and delete list be fixed?
There has been an accepted defect in the issue tracker which really should be a high priority and there has been no word of any status on a fix. The defect is that any developers who cannot use a DELETE request were supposed to be able to make a POST request with a _method=DELETE param, but that has never actually worked. This leaves list management functionality *complete broken* for any client that cannot issue a DELETE request. This was first noted in November, and the defect was accepted one month ago: http://code.google.com/p/twitter-api/issues/detail?id=1239
[twitter-dev] Missing favorites... please help!
I'm trying to help @whitneyhess figure out what happened to her favorites. Until yesterday she had several hundred favorited tweets, many of which were critical to her ongoing business as a freelancer. Currently Twitter is returning 20. If anyone has any insight into what is going on it would be *greatly* appreciated.
[twitter-dev] Re: Missing favorites... please help!
I've been checking for the last 24 hrs and telling her she just has to be patient and that it's probably a glitch (albeit a very very distressing one). It seems that after posting here to the dev group the glitch has resolved itself and over 2500 favorites have returned. If anyone at Twitter was responsible, thanks very much. If this is all coincidental, sorry for cluttering the dev group and I appreciate the responses! Let's hope they don't disappear again in a sec... --Orian On Jan 5, 6:18 pm, Abraham Williams 4bra...@gmail.com wrote: I just check out her favorites in my browser and loaded up the last 80 no problem. It was probably just a glitch with Twitter Abraham On Tue, Jan 5, 2010 at 16:35, Orian Marx (@orian) or...@orianmarx.comwrote: I'm trying to help @whitneyhess figure out what happened to her favorites. Until yesterday she had several hundred favorited tweets, many of which were critical to her ongoing business as a freelancer. Currently Twitter is returning 20. If anyone has any insight into what is going on it would be *greatly* appreciated. -- Abraham Williams | #doit |http://hashtagdoit.com Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: OAuth DELETE LIST problem
There is a bug logged for this in the issue tracker. I can't get it working with _method=DELETE either. http://code.google.com/p/twitter-api/issues/detail?id=1239 On Nov 26, 9:48 pm, Wilfred yau wld991...@gmail.com wrote: Hello all, When I call _method= DELETE in List API, I got 401 Unauthorized from api.twitter.com. After I read the document of OAuth, it mention that _ is no need to encode so it may be a another problem. I have try when I using other parameter include _ like a_method=DELETE is work well and return 200 OK, So, I wound it is the problem in server side?? I can't develop in my twitter Client using Flex in FireFox more since this problem ,can any twitter support team member help me to find out what is the problem?? or any people can success use _method as parameter in Oauth can provide solution for me?? Thanks. Wilfred
[twitter-dev] Re: Draft of List API documentation
Any update on possibly supporting bulk add / remove actions for list memberships? What about the request to fetch all list member IDs in a single call? On Nov 5, 2:01 pm, Marcel Molina mar...@twitter.com wrote: We will support specifying alistby bothidand slug indefinitely. Though we recognize the short comings of finding by slug since they are prone to changing, there are use cases where finding by slug is a lot more convenient. So we'll be supporting both. You never *have* to search by slug :-) On Thu, Nov 5, 2009 at 7:05 AM, Milen mi...@thecosmicmachine.com wrote: I think that all methods which refer to lists should use theid, not the slug. As people have mentioned, the slug can change, so in order to reliably delete alist, you will have to fetch its slug and then issue a delete (or you risk getting an error as the slug might have changed in the meantime). I also tried to page through the statuses in alistbut it seemed that: - next_cursor / previous_cursor had no effect on what was returned - cursor=-1 or anything else didn't have an effect Can anyone shed some light on how we're supposed to do paging? Thanks, M On Oct 16, 7:04 am, Marcel Molina mar...@twitter.com wrote: GET'/:users/lists/:list_slug/statuses.:format' Show tweet timeline for members of the specifiedlist. Parameters: * list_slug: the slug of thelistyou want the member tweet timeline of. (required) * next/previous_cursor: used to page through results (optional) Supported formats: xml, json e.g. curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml -- Marcel Molina Twitter Platform Teamhttp://twitter.com/noradio
[twitter-dev] Re: Typo in delete list subscribers documentation
Agreed. On Dec 10, 3:38 pm, Abraham Williams 4bra...@gmail.com wrote: If only some of the community could be involved in updating the wiki this could be fixed already. Abraham On Wed, Dec 9, 2009 at 19:51, Orian Marx (@orian) or...@orianmarx.comwrote: In the DELETE list subscribers documentation ( http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-DELETE-list-sub... ) the URL for the service is http://api.twitter.com/1/user/list_id/members.format but I think it's supposed to be http://api.twitter.com/1/user/list_id/subscribers.format -- Abraham Williams | Community Evangelist |http://web608.org Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] List statuses paging question
The documentation for GET list statuses shows an optional pagination parameter. Is this going to be replaced with a previous / next cursor in the near future, similar to all other timeline methods?
[twitter-dev] Typo in delete list subscribers documentation
In the DELETE list subscribers documentation ( http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-DELETE-list-subscribers ) the URL for the service is http://api.twitter.com/1/user/list_id/members.format but I think it's supposed to be http://api.twitter.com/1/user/list_id/subscribers.format
