[twitter-dev] Are private twitter user lists searchable?
Guys, Are private twitter user lists searchable? If so, can anyone help me with a PHP based sample code for this. I need to develop a grouping feature with a twitter backend. Will also appreciate any feedback on possible issues and pitfalls for the above proposal along with suggestions. Regards Umashankar Das -- 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
Re: [twitter-dev] What I want to see at a developer event
a) +1 If u prefer Google b) Like if u prefer facebook c) RT if the below was a Tweet. My tiny 2-bit -: a) Dont forget your outstation developers. Mobile grows faster here. Cheers Umashankar Das On Wed, Apr 27, 2011 at 12:13 AM, Adam Green 140...@gmail.com wrote: Actually, let me start with what I don't want to see: 1. Announcements of really cool features coming in the future, because we won't believe that they will ever appear (how are annotations coming along?). 2. Promises of greatly increased rate limits, because every announcement of that in the past failed to materialize. 3. Anything that is intended to wow us with the amazing future of what is back in the lab. See #1. 4. Biz Stone telling amusing anecdotes of all the famous people who have used Twitter. The story about the guy getting arrested in Egypt is moving, but we already watch the Daily Show. What is really needed is honest discussions about how to create better channels of communication between developers and the Twitter staff. Right now there is nothing beyond this forum. And yes, Taylor and Matt do a great job here. But outside this forum it has become accepted practice to ignore requests and say there isn't enough time to respond. I realize that there are millions of users who post silly questions on the support forum, but there has to be a higher level of access that a real developer can call on. If you held open discussions where other ways of communicating problems and suggested improvements could be hashed out, that would do a lot to improve the relationship with developers. The other thing that is needed is a discussion of how developer can become partners in mutually beneficial business relationships. No, we don't all have millions in VC, but collectively we influence millions of users, and we do that at no cost to Twitter. That is worth promoting. Finally, how about an open source process for creating docs and tutorials. I won't mention how bad the current docs are. What is more amazing is how incorrect they are. How about a real wiki that developers can contribute to. If you learn more from us than we learn from you, you will have run the right kind of event. -- 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
Re: [twitter-dev] How to get the Friends ip address
This is only possible if geotagging is enabled for the device where the tweet came from. Check this link for more details -: http://apiwiki.twitter.com/w/page/22554649/Geotagging-API-Best-Practices The API returns latitude and logitude not ip-addresses as you mentioned in the subject. Regards Umashankar Das On Fri, Apr 1, 2011 at 2:32 PM, Mukesh Srivastav mukicha...@gmail.comwrote: Hi Team, We are integrating the Twetter api in one our site and we require to get the current location of the user who post the tweets. Any clues or suggestion ? Regards, -Mukesh Srivastav, India, Hyderabad. -- 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
Re: [twitter-dev] app to block all users ending with numerals
Today someone tweeted a quote on steve jobs to me. I responded to him referencing the same quote. I got two mentions since Steve Jobs was in both my tweets from an id @RT_steve_jobs . I consider this spam. What would the general opinion be. This does not have any numerics :). Regards Umashankar Das On Sat, Mar 26, 2011 at 12:03 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Fri, 25 Mar 2011 15:17:25 +, hax0rsteve hax0rc...@btinternet.com wrote: I know a number of people who use twitter as a read only source of information (for instance they may follow only news outlets and celebrity tweeters) and therefore may have large follow counts with zero tweets. This may not be a use case that you are familiar with, but it is a valid use case. Also, I don't know if you are aware of the current limits on following, etc, which are described here, my apologies if you already are : http://support.twitter.com/forums/10711/entries/15364 As for the OP, well, a) if this is what you (or your users) want, just parse the follow messages looking for numerical postfixes and offer the user the user the option to block them, there is no need for an API call specifically to do this. And b) again, you are missing a use case, there are lots of genuine accounts that have numerics postfixed to them, some people use birth years, and some people - perhaps finding that the screen name they wanted is not available in a naked form - will have chosen [screen name]76 or some similar format, or picked a year with some historical connection with their chosen name. It is not safe to simply assume that ending with numerics is sufficient to indicate that the account is used only in the delivery of spam, be that tweet spam or simply follow spam. While the assumption may hold in a large number of cases - and I am not aware of any empirical data that shows what this number is, though I'd be interested to see one - it will undoubtedly include some false positives. HTH hax0rsteve On 25 Mar 2011, at 15:00, Adam Green wrote: What if Twitter just suspended anyone who followed more than 1,000 users without ever having tweeted? But then their membership would sink dramatically. How about not allowing following past 100 users without tweeting at least once. What is the point of these accounts anyway, unless they are being built up and then sold? They can't be used for spam, since they don't tweet, and generally don't have URLs in their profiles. On Fri, Mar 25, 2011 at 10:47 AM, Dean Collins d...@cognation.net wrote: Lol, someone want to write me an app that blocks all users where their username ends with two or three numbers. This is getting ridiculous. Seems like something that would be pretty easy to achieve via the API don’t you think? Cheers, Dean -- 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 -- Adam Green Twitter API Consultant and Trainer http://140dev.com @140dev -- 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 1. There are plenty of good spam detection and filtering algorithms. The ones listed here, however, are simple hacks unlikely to work without extensive manual intervention. The same can be said for ManageFlitter, TwitCleaner and similar services. They give you a start, but you still have to wade through hundreds or thousands of positives to weed out the keepers. 2. A first name followed by a few numbers is a common legitimate screen name - just having a name like that isn't necessarily an indication of a spammer. Here's how it works - Bobby asks Kelly if she's on Twitter. Kelly says No and signs up. She starts with the screen name Kelly, finds it's taken, so she adds her age or the year she was born. If that's taken too, she'll maybe get clever and pick something like PiercedChick, or she'll pick a few random numbers and get in as Kelly117. (Now don't go blaming me if you start getting followers with names like PiercedChick117.) 3. The User / Twitter spam reporting process could definitely be improved with a few simple steps. I don't have any data - that would have to come from inside Twitter - but the two most common types of spam I see is spambots riding Trending Topics and spambots replying to keywords. In either case, the actual spam tweets sent are usually easily found via Twitter Search. Given that, what I do when I get a spam tweet is perform the search, then go through
Re: [twitter-dev] Re: consistency and ecosystem opportunities
Relevance in microblogging. Big opportunity but very difficult to define. Last i read, even google is stumped. Cheers Umashankar Das On Mon, Mar 14, 2011 at 1:21 AM, Dewald Pretorius dpr...@gmail.com wrote: Ed, I don't have an issue with the size, placing, or color of the #DickBar box. I have an issue with the fact that it shoves stuff in my face that is of absolutely no interest to me. Google got ads right. When your search results include a list of news articles about the Japan earthquake, they don't show ads next to them that yell, #WHATNOTTOSAYTOAFATWOMAN. On Mar 13, 4:18 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: On Sun, 13 Mar 2011 11:49:45 -0700 (PDT), Dewald Pretorius dpr...@gmail.com wrote: I used to be counted in the 90% until they defaced Tweetie, sorry, Twitter for iPhone with that moronic #DickBar that shoves irrelevant nonsense in your face. It's like yelling at you, I KNOW YOU DON'T WANT TO SEE THIS AND HAVE NO INTEREST IN THIS, BUT HERE, TAKE IT ANYWAY. LEARN #WHATNOTTOSAYTOAFATWOMAN AND TRY TO #FARTLIKEJUSTINBIEBER AND OH, JUST WHILE YOU'RE AT IT, HERE'S ANOTHER STUPID ONE THAT'S NOT TRENDING AT ALL, BUT SOMEONE PAID US TO SHOVE IT IN YOUR FACE!!! Are any of you guys developing a better Twitter client for iPhone, because I'll switch in a heartbeat. Oh... Wait Dewald, you have to remember that Twitter isn't the only granfalloon that one must deal with on the iPhone - there's Apple, too. If Steve Jobs didn't like the #DickBar, how long do you suppose it would last? ;-) -- 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
Re: [twitter-dev] Re: consistency and ecosystem opportunities
Privacy -: As I understand twitter, the data is public.[Other than private messages and protected users]. What is the concern here? I guess you are pointing to the credibility quotient of the owner of the tweet and hence his private information? Not wanting to challenge Google, but, we are developing a different algorithm. This thread sure has put a spanner on the works. But, we will work to get around it. Cheers Umashankar Das On Mon, Mar 14, 2011 at 2:20 AM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Mon, 14 Mar 2011 01:32:27 +0530, Umashankar Das umashankar...@gmail.com wrote: Relevance in microblogging. Big opportunity but very difficult to define. Last i read, even google is stumped. Cheers Umashankar Das I don't think it's relevance that stumps Google so much as privacy. It's a lot of work for users to control how much they reveal and to whom, and the Holy Grail of permission marketing - timely, relevant and personal - runs square up against that. I'm cynical enough to think that the sole consumer benefit that has come from social media, including Twitter and Facebook, is the ability to talk back to granfalloons like the State Department, United Airlines and Google. Everything else about the technologies simply reduces costs to marketers, and those cost reductions are not passed on to consumers in the form of less expensive or higher-quality products and services. ;-) -- http://twitter.com/znmeb http://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
Re: [twitter-dev] Re: consistency and ecosystem opportunities
How does one create innovative solutions, if Twitter enforces on us the stipulation, that, the view should be user oriented? It sounds like we're being told, you cannot reference tweets with content which is similar to a certain topic. Imagine the earthquake in Japan, Now, it sounds like I cannot build an app/client/website, which shows tweets which have been sent talking about this unfortunate occurrence. I've already asked if one is allowed to discuss a particularly relevant tweet on this topic. No response from Ryan. You could just say NO. That is a minimum norm of politeness. Regards Umashankar Das On Sun, Mar 13, 2011 at 9:15 AM, Adam Green 140...@gmail.com wrote: Can we get a definition of client? This seems to be where we are talking across each other. 1. Twitter HQ sees a client as an app that displays *only* a user's home time line and allows the user to tweet, retweet, follow, etc. 2. Developers see a client as an app that displays tweets from any source, including the home timeline *and* those that are curated by editors and algorithms, and allows the user to tweet, retweet, follow, etc. I think to Twitter HQ, these are two very different things. I believe that this is what Ryan was trying to say. I believe that Ryan was trying to say, don't build apps that *only* do 1. You will have more luck with 2. Developers heard don't build apps that do 2 or you will be instantly shut down. If Ryan hadn't combined his message with things that inadvertently also were perceived as a threat of instant shutdown as a result of an innocent misunderstanding of the rules, his statement would have been taken as advice, rather than a threat. I believe he meant well. He failed. He should keep trying until everyone understands. That is his job. Or it should at least be someone's job. Collectively the developers are worth the effort. Hey, why not hold a conference, put everyone together, and talk until this is clear? You can afford it. We all need it. Your future IPO investors aren't stupid. Well, at least not all of them. It is not just your revenue numbers they will see. It is lots of either happy or unhappy developers. We will raise your valuation. Keep saying that to Dick and the Board. They need to understand that. On Sat, Mar 12, 2011 at 10:26 PM, Raffi Krikorian ra...@twitter.comwrote: is the twitter client what's the most useful thing there? i would think the algorithms and system to match tweets to that content is the most fruitful place for entrepreneurship? On Sat, Mar 12, 2011 at 7:22 PM, Shannon Whitley shannon.whit...@gmail.com wrote: Thanks, Raffi, but obviously I'm not the only one reaching these conclusions. If our interpretation is incorrect, then the policy isn't clear. Television shows, newspaper articles, and band pages are perfect examples of places where a Twitter client might be useful. I could build a full-featured Twitter client around a single news site and that might be the perfect solution for that set of users. Under the new guidelines, it sounds like I'd be shutdown. On Mar 12, 6:39 pm, Raffi Krikorian ra...@twitter.com wrote: in reading your blog post, i think you're misunderstanding what @*rsarver*wrote. the API is open -- i personally love seeing all the innovation around getting content into twitter (/1/status/update). there is a cafe in france who's oven tweets whenever its done baking. that uses the platform to get content in there. there was a NYU project that enabled your plants to tweet when they needed water. that uses the platform to get content into twitter. then there are people who match tweets to context. seeing twitter in action with a television show, or a newspaper article, or a conference, or a band -- that's how people really understand and get twitter. they see it through the lens of what's happening in the world. what @*rsarver* said, effectively, was building a business around *simply*rendering /1/statuses/home_timeline was probably-not-the-best-thing-to-do. please go still innovate. just don't bet money on simply making an API call to grabbing a user's home_timeline and rendering it. that's thinking too small, and @*rsarver* is telling you that. On Sat, Mar 12, 2011 at 4:29 PM, Shannon Whitley shannon.whit...@gmail.comwrote: I was hoping that Ryan was just a few weeks early for his April Fools' post. Don't build clients? It sounds like a bad joke. I wrote a letter to Ryan on my blog in response to this post: http://www.voiceoftech.com/swhitley/index.php/2011/03/a-letter-to-rya... I know you guys can't be serious about this. Stage a mutiny if you have to, but don't let this boneheaded decision stand. -- Raffi Krikorian Twitter, Application Serviceshttp://twitter.com/raffi -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com
Re: [twitter-dev] consistency and ecosystem opportunities
It has got to do with the nature of the way content is used. We will also have 'reply' to respond to the user. But, 'Discuss' is there to allow discussion on a certain topic. Imagine the context of the earthquake in Japan. Some user wants to know about facilities being provided by relief agencies in Tokyo. The discussion will be useful for a group of people who reference a particular tweet. Regards Umashankar Das On Sun, Mar 13, 2011 at 9:51 AM, Raffi Krikorian ra...@twitter.com wrote: why would you need a brand new verb? what's wrong with reply? On Fri, Mar 11, 2011 at 8:40 PM, Umashankar Das umashankar...@gmail.comwrote: Dear Ryan, A very direct question. Is it being said that I cannot associate a brand new field like 'Discuss' with a tweet in my website? Regards Umashankar Das On Sat, Mar 12, 2011 at 1:48 AM, 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*. We need to ensure that tweets, and tweet actions, are rendered in a consistent way so that people have the same experience with tweets no matter where they are. For example, some developers display “comment”, “like”, or other terms with tweets instead of “follow, favorite, retweet, reply” - thus changing the core functions of a tweet. With this in mind, we’ve updated our Terms of Service: http://dev.twitter.com/pages/api_terms. *The Opportunity for Developers* Developers have told us that they’d like more guidance from us about the best opportunities to build on Twitter. More specifically, developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no. If you are an existing developer of client apps, you can continue to serve your user base, but we will be holding you to high standards to ensure you do not violate users’ privacy, that you provide consistency in the user experience, and that you rigorously adhere to all areas of our Terms of Service. We have spoken with the major client applications in the Twitter ecosystem about these needs
Re: [twitter-dev] Re: consistency and ecosystem opportunities
Hi Raffi, * **[you're right, we do think there is a lot to be done with tweet summarization, curation, selection, matching, etc. focus your efforts on that and just follow our lead with tweet rendering and interaction.]* This statement really helps me, personally. We're not doing tweet rendering. Interaction was a like 20% of the product we are working on here. We will try to think of a workaround. If the above statement was part of Ryan's original mail, it would've helped us a lot. You've mentioned that your statement is neither official nor definitive. It would be really great if Ryan (as the head of Platform development) would discuss this. Twitter's restrictions on usage of streaming and search api's were a big bottleneck to our product. We've finally found a solution which does not overload twitter at all. Please ask Ryan if he may repeat your statement above, mentioned by you. Appreciate you putting the time into this. Regards Umashankar Das On Sun, Mar 13, 2011 at 10:08 AM, Raffi Krikorian ra...@twitter.com wrote: hey adam. i can't speak officially and definitively, however, we don't think there are as many business opportunities in making a piece of software that * simply* renders any of our timeline methods (/1/statuses/home_timeline, /1/statuses/mentions, lists, etc.). that's your #1. you're right, we do think there is a lot to be done with tweet summarization, curation, selection, matching, etc. focus your efforts on that and just follow our lead with tweet rendering and interaction. does that help? On Sat, Mar 12, 2011 at 7:45 PM, Adam Green 140...@gmail.com wrote: Can we get a definition of client? This seems to be where we are talking across each other. 1. Twitter HQ sees a client as an app that displays *only* a user's home time line and allows the user to tweet, retweet, follow, etc. 2. Developers see a client as an app that displays tweets from any source, including the home timeline *and* those that are curated by editors and algorithms, and allows the user to tweet, retweet, follow, etc. I think to Twitter HQ, these are two very different things. I believe that this is what Ryan was trying to say. I believe that Ryan was trying to say, don't build apps that *only* do 1. You will have more luck with 2. Developers heard don't build apps that do 2 or you will be instantly shut down. If Ryan hadn't combined his message with things that inadvertently also were perceived as a threat of instant shutdown as a result of an innocent misunderstanding of the rules, his statement would have been taken as advice, rather than a threat. I believe he meant well. He failed. He should keep trying until everyone understands. That is his job. Or it should at least be someone's job. Collectively the developers are worth the effort. Hey, why not hold a conference, put everyone together, and talk until this is clear? You can afford it. We all need it. Your future IPO investors aren't stupid. Well, at least not all of them. It is not just your revenue numbers they will see. It is lots of either happy or unhappy developers. We will raise your valuation. Keep saying that to Dick and the Board. They need to understand that. On Sat, Mar 12, 2011 at 10:26 PM, Raffi Krikorian ra...@twitter.comwrote: is the twitter client what's the most useful thing there? i would think the algorithms and system to match tweets to that content is the most fruitful place for entrepreneurship? On Sat, Mar 12, 2011 at 7:22 PM, Shannon Whitley shannon.whit...@gmail.com wrote: Thanks, Raffi, but obviously I'm not the only one reaching these conclusions. If our interpretation is incorrect, then the policy isn't clear. Television shows, newspaper articles, and band pages are perfect examples of places where a Twitter client might be useful. I could build a full-featured Twitter client around a single news site and that might be the perfect solution for that set of users. Under the new guidelines, it sounds like I'd be shutdown. On Mar 12, 6:39 pm, Raffi Krikorian ra...@twitter.com wrote: in reading your blog post, i think you're misunderstanding what @*rsarver*wrote. the API is open -- i personally love seeing all the innovation around getting content into twitter (/1/status/update). there is a cafe in france who's oven tweets whenever its done baking. that uses the platform to get content in there. there was a NYU project that enabled your plants to tweet when they needed water. that uses the platform to get content into twitter. then there are people who match tweets to context. seeing twitter in action with a television show, or a newspaper article, or a conference, or a band -- that's how people really understand and get twitter. they see it through the lens of what's happening in the world. what @*rsarver* said, effectively, was building a business around *simply*rendering /1/statuses/home_timeline
[twitter-dev] A very basic question
Guys, I just wanted to tap the extensive knowledge of such esteemed developers aroundd here. Can anyone recomend the best library which supports twitter api's in C/C++. We're specifically looking at the samplestream API on twitter. Thanks In Advance Regards Umashankar Das -- 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] A very basic question
Thanks.. Regards Umashankar Das On Thu, Mar 10, 2011 at 1:24 PM, Georgooty varghese georgo...@gmail.comwrote: you can use libauth library from twitter On Thu, Mar 10, 2011 at 11:59 AM, Umashankar Das umashankar...@gmail.comwrote: Guys, I just wanted to tap the extensive knowledge of such esteemed developers aroundd here. Can anyone recomend the best library which supports twitter api's in C/C++. We're specifically looking at the samplestream API on twitter. Thanks In Advance Regards Umashankar Das -- 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
Re: [twitter-dev] Re: Twitter API Timeouts
Hi, Even echofon clients are timing out. It coul be a general failure of service. Let us see if Twitter wants to clarify Regards Umashankar Das On Mon, Feb 28, 2011 at 5:13 PM, Leon Meijer l...@lmeijer.nl wrote: Hi, I have noticed the same behaviour today, connections time out after 30 seconds, even the verify_credentials api call fails... the api status page shows everything is fine though. Regards, Leon Meijer -- *From:* Naveen [mailto:knig...@gmail.com] *To:* Twitter Development Talk [mailto: twitter-development-talk@googlegroups.com] *Sent:* Mon, 28 Feb 2011 11:36:57 +0100 *Subject:* [twitter-dev] Re: Twitter API Timeouts We have been seeing this behavior as well since early yesterday. We have a lot of connections (a noticeable percentage) simply timeout. We have tested various timeouts and work arounds and it appears as though the connections will happily be kept open indefinitely with no response if there is no timeout set.. I am also curious if there was a change made that would be attributed to this change in behavior. --Naveen On Feb 28, 2:14 am, Colin Howe colintheh...@googlemail.com wrote: Hi, We've started seeing the API drop a lot of our requests. No error, no response at all. Is this a known issue or is it a change I should have been aware of? Cheers, Colin -- 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
Re: [twitter-dev] Http Response code handling
Hi Matt, Do the failed requests count [one's with 420 response] into the tally for the next hour? Regards Umashankar Das On Wed, Feb 23, 2011 at 12:41 PM, Matt Harris thematthar...@twitter.comwrote: Hi Zaver, A 420 response from the Search API means you have been rate limited. What you should do is stop making requests and then try again 30 seconds later. If you still get 420, wait 1 minute. Continue doubling the time you wait until the 420 stops and you get results. Then gradually increase your request rate again. For extra back off magic add a little jitter (e.g. a random number of seconds between say 0 and 30) to the doubled wait times. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Feb 22, 2011 at 12:29 AM, zaver zave...@hotmail.com wrote: Hello, I am using the search api with multiple keywords (120 keywords) using curl (curl_multi_init etc.), querying the api every 5 mins and i need some help on how to handle some of the response codes. Specifically: 420 - i get this error on some of my keywords not all. Does this mean that i am rate limited and should wait for the amount of time in the Retry-after part in general or only for these keywords? Currently I do wait for the amount of time it specifies for the whole keyword set. Is that right? Haven't come across these yet although i would like to have some handling for these. 502: Bad Gateway: Twitter is down or being upgraded. 503: Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. Any help is greatly appreciated. Thanks Zaver -- 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
Re: [twitter-dev] Twitter Development platform - A Rant
While , being philosophical about loss of whitelisting, the recent behaviour wsith regard to searches is not necessarily very postive for Twitter's public profile. Software history has shown that more than the individual product , it is the ecosystem, which determines the future of the product and the company. The current debate on Nokia and it's viability has been a prime-example of that. It is well-known that Java became popular despite efforts by various forces to discourage it's widespread usage . Now, Twitter and it's API groups claim that, they, are putting artificial limits of rates to ensure proper delivery for regular service. Someone has not studied the history of path-breaking products up there. If the method here is to discourage developers to invest in twitter to create applications, it is not the best idea. There is a lot of talk in market ccts that Twitter is looking at different ways to monetise it's huge userbase. Somehow, the recent actions leads us to believe , that, with that kind of focus you guys are losing track of what twitter can actually become. Twitter is already a successful product. It was a great idea which has changed the way people communicate with each other. Today, revolutions happen in twitter. With all these restrictive views and thought processes, one believes that, perhaps, It does not think like a startup anymore. Guys, your role model should be facebook. Even today, they think like startups. It was facebook's open development platform which was the driver to more users in it's 2nd phase of expansion. We in our company view twitter as much larger than micro-blogging product. We believe it can symbolise the next WWW. Our product lines are designed on that. We dont have whitelisting and we were not planning to apply for it. We were willing to work around the different restrictions and come up with innovative solutions. These restrictions have increased resource requirements for the product we're building, but out here, we're happy about it. They've got us people who have innovation which is essential to a successful startup. Somehow, the recent statements make me believe that twitter is losing it here. I come from the domain of server technologies. I completely understand that QoS (Quality of service) is a big issue. But, in times of peak load, twitter still does go down. By putting artificial limits on querying twitter, you're not allowing creation of the next generation of products. All these limits indirectly makes one believe that twitter does not want more users. That seems very contradictory for a company whose valuation of 8-10 Billion USD is a function of it's userbase. If I were given the charge of solving this problem i would add new servers . Our server requirement[dedicated] costs us about 140 USD permonth/perserver. It has been said that you guys use Cassandra. Given Cassandra's performance replication efficencies are fairly decent. A fleet of 10 servers should be enough to handle things for you guys for the near future. That will be less than what you guys pay a developer. I'm sure lots of users will be happy to pay for this too. Although, the real trick is to be free. The future is about being open. Facebook was a means of bringing your social experience online. But, there was a concept of exclusivity to it. Twitter was diametrically opposite. It allowed people to talk to anybody. Politically speaking, it was a very democratic experience. I would like to see twitter bigger than Google someday. Blocking development platforms is not the way to go. Regards Umashankar Das On Sun, Feb 13, 2011 at 6:16 PM, Adam Green 140...@gmail.com wrote: The behavior on this group has changed significantly since Ryan finally admitted that Whitelisting no longer exists. I've never seen anyone discuss methods of getting around TOS before, well there was Edward H., and we saw what happened to him. Now there are free flowing discussions of MTurk and other tricks to go way beyond the rate limits. I think this is great. Frankly, Twitter has done a good job of offering free resources to devs, which I thank them for, but there was way too much fear before. Now there are no extra benefits that can be given and withdrawn on a case by case basis. Boy do I hate that phrase. Of course, they can ban people from this list, but maybe the irony of Twitter blocking free speech on their own forum may restrain that urge in the future. Personally, I've treated Whitelisting like Social Security. It ain't going to be there when I need it. That has turned out to be a winning strategy. I don't really violate TOS, since I'm not as spammer, but I have never tried building anything that would fail if Twitter didn't give me Whitelisting after it got into production, which BTW was the most disrespectful thing I've seen from a platform vendor. Everyone should assume that you need to use what is there by default, and always be ready with a workaround if that gets
Re: [twitter-dev] Twitter Development platform - A Rant
Andrew , Thank you for such a measured response. I'm not looking at the immediate action of stopping whitelisting by twitter. I must add, that, if a certain feature requires an application process, I had doubts in my ability to convince twitter, that, I really deserve to be in the list. I believe I've also mentioned in my mail ,that , we, as a team/company, have already made arrangements which does not require us to use whitelisting. Perhaps, since, my initial mail was a rant, but, not a structured 'reply' it got lost in whatever I said. What I say is essentially this. Twitter seems to be discouraging developers whose products have the potential who increasing their userbase. It almost as If I'm hearing that, 'WE DONT WANT ANYMORE USERS' . We're tired of managing the existing number. I don't disagree that nobody should make plans on features which have no guarantees [whitelisting], that, they will continue in future. But, by putting such limits isn't Twitter running the risk of becoming just another product. The creation of the facebook development platform was responsible in spawning a market leader in gaming field i.e ZYNGA.But, These limits by twitter dont allow someone to think about a new idea. He will stop thinking that ; what if I get traffic ? Anyhow, twitter will block me if I cross their rate limit. How can an innovator think in such an environment? I'm not sure if you find this as conjecture. This , to me , is a logical line of reasoning. Anyhow, We ,as a team , have planned on working with a worst case scenario. twitter's search API is very important to us. We never planned for whitelisting, we dont need it. The only worry is if tomorrow, (hopefully), if we generate traffic from our product, will twitter just stop the 'SEARCH API' . We need to know that. Clarity in this will go a long way. I hope I haven't offended anybody here. These are views , since, we as a team , feel that we can create something path-breaking using twitter as our backend resource. We will only help twitter that way. Thanks Regards Umashankar Das On Sun, Feb 13, 2011 at 11:48 PM, Andrew W. Donoho andrew.don...@gmail.comwrote: On Feb 13, 2011, at 08:53 , Umashankar Das wrote: Now, Twitter and it's API groups claim that, they, are putting artificial limits of rates to ensure proper delivery for regular service. Mr. Das, While you make many interesting points in your rant, I think many of them are conjecture and opinion. As reasonable people can disagree about opinions, I've edited them out of my reply. I wish to focus on some unambiguous issues. We each have to make our business bets with respect to the Twitter platform. (I speak as the developer of ch@tter™, an iPad Twitter client. In many ways, Twitter destroyed my business opportunity when they purchased Tweetie and made it free. I mention this for context and not as a cause to rant at Twitter. I'm making plenty of money as a result of building ch@tter™. The iOS consulting business is very healthy.) It is clear from this thread that many developers made, perhaps unwisely, product plans based on Twitter's continued support for white listing. In my case as a client developer, the increase of my API count from 150/hour to 350/hour due to moving to OAuth totally removed my need for white listing. If user streams was supported, I could easily live with 150/hour limit. If they would stand behind their user streams API, I would switch to it immediately. (Beta status is not, frankly, good enough. If they cannot make a commitment to their new API, why should I? By my count, user streams has been in beta for almost 6 months.) Changing a platform's API is hard. Twitter is discovering this the hard way. Every developer has an investment they would like to preserve in the status quo. That said, Twitter's API evolution practices, presumably approved by their CTO, Mr. Sarver, are not, in my opinion, helping their partners grow with Twitter. That they are turning off white listing while not having yet made a production commitment to user streams, is a great example of an evolutionary stumble. That they haven't announced any other methods of enhancing Twitter's ability to scale while supporting functionality enabled by the large white lists is an oversight. The outrage expressed in this thread is good, unambiguous evidence of the stumble. Another example is the closed roll-out of promoted tweets. I think every third party app developer would love to find a way to further monetize their Twitter application. Twitter did announce that they would find a way to allow their developer partners to participate with the promoted tweets program. That has not yet happened. Currently, as Twitter has made a floor price of $0.00 for iOS apps, I have to resort to Apple's iAds to capture revenue from my labors. I don't mind but it does cut my other market-making partner, Twitter, out of the revenue stream. As it reduces my revenue
Re: [twitter-dev] Update on Whitelisting
Hi Taylor, Could you please elaborate on IP + user ? Does this mean that the rate of 350/hour is applicable per user? Alternatly, does this mean I can have more than 1 user using the same IP and having seperate rate buckets( 350 each per hour). Thanks Regards Umashankar Das On Fri, Feb 11, 2011 at 7:07 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Correction, Ed: Rate limiting is considered on an IP + user basis only at this time, while authenticated, not by client + user. Hold-over from the old world. Taylor On Thu, Feb 10, 2011 at 3:11 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Ed, Some quick answers to a few specific points below: That brings up an interesting question. Suppose I'm using a web-based service like HootSuite that *isn't* using Site Streams (at least, I think they aren't using Site Streams). They're then getting 350 API calls per hour via oAuth in the znmeb account from their IP address. Now I log on to Twitter using the standard web app from my workstation. Do I get another 350 calls per hour because I have my own IP address, or are all IP addresses authenticated as znmeb sharing that 350? With authentication, whitelisting works at the junction of a user and an application. @znmeb using Twitter for iPhone has 350 requests per hour. @znmeb using YoruFukurou has 350 requests per hour. Using one user request in Twitter for iPhone does not effect the user quota for YoruFukurou. A related question - how far away from production is Site Streams, and is there a plan to encourage services like HootSuite to migrate to Site Streams? It seems like it would be a big win for them (and all the other web-based Twitter platforms). Site Streams is nearing availability for general use -- there are a few more t's to cross and i's to dot. In fact, HootSuite is currently a Site Streams beta consumer. Taylor -- 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] Thoughts on cloud computing and Twitter search
With less than encouraging responses with regard to whitelisting, firehoses and limits on search rates from the twitter development group, it becomes increasingly clear that a cloud computing approach is required for avoiding ip-address rate limits on Twitter search. The obvious potential of Twitter search in terms of data is such a big resource base makes it very significant. My query for twitter dev here is that, If a solution is designed for a single application to work in a cloud-based-framework(i.e Multiple ip addresses) , can a guarantee be provided that twitter will not block the app in future ? If traffic becomes fairly high. We here ebelieve that Twitter is a big resource for data. We would like to utilise it and provide better services. Hoping to get a positive response to my query which does not seem to violate any guidelines as of now. Thanks In advance Umashankar Das -- 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] Twitter search / streaming API limitation query
Thanks, It has been a big help. Looks like twitter does not want to respond to me :). Regards Umashankar Das On Mon, Jan 10, 2011 at 3:14 PM, Mauro Asprea mauroasp...@gmail.com wrote: I don't know if this would help you but is a nice overview about a) Search vs streaming http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das umashankar...@gmail.comwrote: Hi, We are working on a product which will do searches on twitter from a certain server system. We are yet to take a decision whether the searches will be anonymous(Non-authenticated) or authenticated. The decision is subject to limitations on search results using twitter search / streaming apis. I was hoping if you could provide info or references based which provide the information. We hope to have substantial number of unique search (pattern) queries from a particular ip-addresses. Although , the users by themselves are expected to have much lesser queries. We are willing to put a limit of 30 per hour for the search queries which are authenticated. Please advise on the specs . We do expect that twitter will get many new users after our product is launched. Educated guesses will also be useful for us in making a design decision :) Parameters: a) Search vs streaming b) anonymous vs authenticated Regards Umashankar Das -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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
Re: [twitter-dev] Twitter search / streaming API limitation query
Hi Taylor, Thanks for your suggestions. We want to use twitter data to provide a user-oriented search based on tweets in a personalised context. The idea to use it from a client is not feasible since, the product is expected to have a thin client i.e. browser. We have developed an algorithm which is expected to sort out tweets based on relevance of the query. Therefore we need to collate the data at the web server. The streaming api does not seem to retrieve older data, and that might well be very relevant, since, lots of queries will require older data in which case a search api query is required. That will hit the ip-address limit. Could any alternative be suggested? Thanks Regards Umashankar Das On Mon, Jan 10, 2011 at 8:40 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Umashankar, Just an additional note that Twitter doesn't yet offer an authenticated search API -- the Search API is subject to per-IP Address rate limits that are apart from the rate limits afforded in the standard REST API on api.twitter.com. If your primary goal is to provide ad-hoc search, then the unauthenticated Search API will work for a limited amount of queries (but will require a larger caching infrastructure on your part as you grow). Another alternative with unauthenticated search is to push the search API queries to the client (web browser) so that the search query limits apply to the user's IP address that is utilizing your application. If you're going to be tracking multiple search queries and are providing those tweets for display to your users, then the Streaming API is probably a better fit. It's wise to consider the end-user-authenticated variations provided in User Streams and Site Streams (which might be better for your scenario) http://dev.twitter.com/pages/streaming_api What kind of search-based app are you looking to build? Taylor On Mon, Jan 10, 2011 at 7:00 AM, Umashankar Das umashankar...@gmail.comwrote: Thanks, It has been a big help. Looks like twitter does not want to respond to me :). Regards Umashankar Das On Mon, Jan 10, 2011 at 3:14 PM, Mauro Asprea mauroasp...@gmail.comwrote: I don't know if this would help you but is a nice overview about a) Search vs streaming http://140dev.com/twitter-api-programming-tutorials/aggregating-tweets-search-api-vs-streaming-api/ On Fri, Jan 7, 2011 at 6:32 PM, Umashankar Das umashankar...@gmail.comwrote: Hi, We are working on a product which will do searches on twitter from a certain server system. We are yet to take a decision whether the searches will be anonymous(Non-authenticated) or authenticated. The decision is subject to limitations on search results using twitter search / streaming apis. I was hoping if you could provide info or references based which provide the information. We hope to have substantial number of unique search (pattern) queries from a particular ip-addresses. Although , the users by themselves are expected to have much lesser queries. We are willing to put a limit of 30 per hour for the search queries which are authenticated. Please advise on the specs . We do expect that twitter will get many new users after our product is launched. Educated guesses will also be useful for us in making a design decision :) Parameters: a) Search vs streaming b) anonymous vs authenticated Regards Umashankar Das -- 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 -- Mauro Sebastián Asprea E-Mail: mauroasp...@gmail.com Mobile: +34 654297582 Skype: mauro.asprea Algunos hombres ven las cosas como son y se preguntan porque. Otros sueñan cosas que nunca fueron y se preguntan por qué no?. George Bernard Shaw -- 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
[twitter-dev] Twitter search / streaming API limitation query
Hi, We are working on a product which will do searches on twitter from a certain server system. We are yet to take a decision whether the searches will be anonymous(Non-authenticated) or authenticated. The decision is subject to limitations on search results using twitter search / streaming apis. I was hoping if you could provide info or references based which provide the information. We hope to have substantial number of unique search (pattern) queries from a particular ip-addresses. Although , the users by themselves are expected to have much lesser queries. We are willing to put a limit of 30 per hour for the search queries which are authenticated. Please advise on the specs . We do expect that twitter will get many new users after our product is launched. Educated guesses will also be useful for us in making a design decision :) Parameters: a) Search vs streaming b) anonymous vs authenticated Regards Umashankar Das -- 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
