Re: [twitter-dev] I've got the error:OAuth Authentication Failed.And I tried all the wordpress to twitter plugins.
I'm no OAuth expert, but did you make sure your system time is properly synchronized with a regional NTP server? Pascal On Feb 12, 2011, at 3:13 AM, Winson wrote: Hi there. Using WP 3.0.5and WP to Twitter 2.2.6 on a CentOS server, which I don't manage at all. I've got the error OAuth Authentication Failed. Check your credentials and verify that Twitter is running.. I've also checked all the data from the application, including erasing the older and creating a new one, but this issue remains. Twitter is active and working at this very moment I'm writing this message. Anybody help? PS:And I thought the problem is the Wp to Twitter 2.2.6 Plugins.Then I tried to install the other Wordpree to twitter Plugins..The result: Authentication Failed.. -- 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] Lifecycle of a Site Streams Connection
Is there any documentation which I could read which describes the lifecycle of site streams connections? I can set them up and respond to what I receive but there are a few things I am puzzled about. What am I supposed to do with a track limitation notice in site streams? I can't reduce the number of requests or back off as I can with a REST api? If I want to change the parameters of my site stream connection do I start a new connection and close my old one? How many simultaneous connections am I allowed? Do I start up a new connection with the new things I want (eg every 10 minutes), and then eventually (eg every hour/every day) consolidate these back into single site stream connections? Feel free to say rtfm if you can also point to the specific part of the manual I've missed :-) Alex -- 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 app development require guidance
Please read the error and post. On Sat, Feb 12, 2011 at 4:44 AM, raj kar rajkar2...@gmail.com wrote: We are working on Twitter part of this proposed project. we are trying to access twitter from stand alone java application, but got stuck in between. Here is the action flow that we followed. 1. Registered our application with twitter got consumer secrete keys 2. Tried to get request access token with above keys. We got request token but unable to get access token. Before we can get access token its throwing up error.. Suggest some solution please -- 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 -- xxx The butterfly does not count years, but moments, and therefore has enough time. - Rabindranath Tagore -- 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] Whitelisting is still in the docs. Please remove this.
http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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
Re: [twitter-dev] Re: Is there going to be another Chirp?
On Feb 7, 2011, at 5:25 PM, M. Edward (Ed) Borasky wrote: On Mon, 07 Feb 2011 15:25:59 +0100, Tom van der Woerdt i...@tvdw.eu wrote: I'd prefer London or some other West-European city. I'm guessing it will be in SFO, given how closely the Twitter team worked with the developers last year. They can't fly a few hundred folks to NYC or London. The question is *where* in SFO - Fort Mason wasn't particularly well suited for a barcamp-style conference with breakout sessions, wifi, etc. The noise level / acoustics were unacceptable. True enough, but Twitter is a global application - the developer conference should go global too! But really, unless they're going for late May - early June, they need to get some planning done now. Google I/O sold out in 59 minutes, and actually the scuttlebutt is that it was actually sold out for all practical purposes as soon as the web site went live - invited attendees had already scooped up most of the tickets. I'm not saying I think Chirp will be *that* popular, but I'm guessing a lot of people who didn't get in last year will want to come this year. Also true, I felt pretty lucky to have gotten a ticket last year. Mike Caprio Principal and Lead Consultant Brainewave Consulting 402 Graham Avenue PMB 211 Brooklyn, NY 11211 p: +1-347-269-0558 @brainewave -- 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] Whitelisting is still in the docs. Please remove this.
Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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] Whitelisting is still in the docs. Please remove this.
Damn! I had 120 days in the pool. :) Thanks, Taylor. On Sat, Feb 12, 2011 at 11:29 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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
Re: [twitter-dev] Whitelisting is still in the docs. Please remove this.
Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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] Whitelisting is still in the docs. Please remove this.
Release early. Release often. Hopefully, folks have learned an important lesson ... On 2/12/11 11:37 AM, Jan Paricka wrote: Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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] Whitelisting is still in the docs. Please remove this.
I don't see the connection to twitter chronically ignoring my whitelist requests http://beepl.com/jan is the app Jan On Sat, Feb 12, 2011 at 6:53 PM, Dossy Shiobara do...@panoptic.com wrote: Release early. Release often. Hopefully, folks have learned an important lesson ... On 2/12/11 11:37 AM, Jan Paricka wrote: Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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] Getting a 403
Hi, When i try to create an application the server throws me a 403 Forbidden: The server understood the request, but is refusing to fulfill it. Reason Please? -- 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] Pin via e-mail?
Is it possible to get PIN via e-mail? How long Auth Link lives? My desktop app will send clients authorization link Thet will click the link and get PIN e-mailed back to me What process to execute and data I need to store to finish authorization and get the keys? 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
[twitter-dev] Re: Looks like our application is DOA...
There's simple workaround for that. Just think about it and you'll figure it out ;-) -- 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: Whitelisting is still in the docs. Please remove this.
Jan, yes twitter have said they're removing whitelisting for new requests, see here : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 On Feb 12, 5:37 pm, Jan Paricka jpari...@gmail.com wrote: Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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: Whitelisting is still in the docs. Please remove this.
Cool. I am weeks from launch and I am fucked. Without whitelisting, my app won't sustain more than 15 users. Thank you twitter, thank you very much. Btw, I really hoped to launch at @geekn'rolla Jan On Sat, Feb 12, 2011 at 6:33 PM, mabujo jaa...@gmail.com wrote: Jan, yes twitter have said they're removing whitelisting for new requests, see here : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 On Feb 12, 5:37 pm, Jan Paricka jpari...@gmail.com wrote: Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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: Whitelisting is still in the docs. Please remove this.
won't sustain more than 15 users Why not? If you have 15 users, you can spread the API calls over them and the last time I checked, 15*350 gives you 5250 API calls. Tom On 2/12/11 7:24 PM, Jan Paricka wrote: Cool. I am weeks from launch and I am fucked. Without whitelisting, my app won't sustain more than 15 users. Thank you twitter, thank you very much. Btw, I really hoped to launch at @geekn'rolla Jan On Sat, Feb 12, 2011 at 6:33 PM, mabujo jaa...@gmail.com mailto:jaa...@gmail.com wrote: Jan, yes twitter have said they're removing whitelisting for new requests, see here : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 On Feb 12, 5:37 pm, Jan Paricka jpari...@gmail.com mailto:jpari...@gmail.com wrote: Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com mailto:140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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
Re: [twitter-dev] Re: Whitelisting is still in the docs. Please remove this.
The app I am working on is assisting these users - also importing (and semantically analyses) their contacts, replicate their follow structure, etc etc By importing these, I'm also building an index of the twitter experts It's the invisible part to the project that won't work. The http://74.3.248.227/user/fu2ri/arbor/ mumbo jumbo. Effectively, it's a supporting desktop app. I call it Sopy. (name comes from social.py) I'm hoping to launch on @geeknrolla if I'm accepted. Jan On Sat, Feb 12, 2011 at 7:43 PM, Tom van der Woerdt i...@tvdw.eu wrote: won't sustain more than 15 users Why not? If you have 15 users, you can spread the API calls over them and the last time I checked, 15*350 gives you 5250 API calls. Tom On 2/12/11 7:24 PM, Jan Paricka wrote: Cool. I am weeks from launch and I am fucked. Without whitelisting, my app won't sustain more than 15 users. Thank you twitter, thank you very much. Btw, I really hoped to launch at @geekn'rolla Jan On Sat, Feb 12, 2011 at 6:33 PM, mabujo jaa...@gmail.com mailto:jaa...@gmail.com wrote: Jan, yes twitter have said they're removing whitelisting for new requests, see here : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 On Feb 12, 5:37 pm, Jan Paricka jpari...@gmail.com mailto:jpari...@gmail.com wrote: Whoa, does that mean twitter is no longer whitelisting?? Guys, I spent nearly two years working on the app - it's nearly ready, whitelisting is essential to us. Please advice, Jan On Sat, Feb 12, 2011 at 5:29 PM, Taylor Singletary taylorsinglet...@twitter.com mailto:taylorsinglet...@twitter.com wrote: Sorry Adam, missed this document among the many -- it's fixed now. The form itself and its text are immutable at the moment. On Sat, Feb 12, 2011 at 5:26 AM, Adam Green 140...@gmail.com mailto:140...@gmail.com wrote: http://dev.twitter.com/pages/rate-limiting#whitelisting Ryan, Taylor, Matt, I know changing mistakes in the docs has been impossible in the past. My guess is that someone lost the password for these pages. But leaving the whitelisting statement in the docs and the whitelisting form online is a sign of complete disrespect for your developers. New devs will see this and still think they can get whitelisting. Even worse they will waste their time building apps that need whitelisting, since the request form says: Whitelisting is only available to developers and to applications in production How would you feel if you started building an app today, spent months on it, got it into production, and then waited months for approval, since the docs say you won't get a response until approval is done? Not removing this shows that developers don't really matter to Twitter. Removing it right away shows that they do. Please don't say that you are too busy to make that change, and that it will be done some time in the future. Nobody is that busy. Please remove it. 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 -- 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 developer documentation
[twitter-dev] Re: should search and streaming apis return similar tweets for equivalent geolocation areas
Some metrics: I just reran some tests to compare results for both the polling search api + geocode and the steaming api statuses/filter + locations using San Francisco as the geolocation. Basically, the polling search api+geocode returns approximately 30x more results than the steaming api statuses/filter + locations within the same test period for the same geolocation. The parameters used for the search api+geocode were: 37.736784, -122.44709, 40km The parameters used for the steaming api statuses/filter + locations were: -122.901549008664,37.3773810096865,-121.992630991336,38.0961869903135 which correspond to the bounding box around 37.736784, -122.44709, 40km. Why is there such huge difference and can we expect the streaming API to eventually match what the search API produces for geolocalized searches? Thanks, Colin On Feb 10, 5:32 pm, Colin Surprenant colin.surpren...@gmail.com wrote: Hi, I have been running some tests to gather tweets from users within a geo area using both the search API (with the geocode parameter) and the streaming API (with the statuses/filter method locations parameter). I have noticed that the streaming API returns far less tweets for an equivalent area expressed either as a latlong+radius for the search API or as a bounding box for the streaming API. Is this normal or should we expect a similar result set with both methods? In the doc it says that the streaming API will only return tweets that are created using the Geotagging API (and within the bounding box) but the search API will preferentially use the Geotagging API, but will fall back to the Twitter profile location. Can this explain why I see much more results with the search API? Thanks, 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-dev] DM rate limit
Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information -- 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] User stream and oauth headers
Hi. I'm using python-oauth2 to handle the authentication with the REST and user stream APIs. I'm using the same code to sign the request in both cases, and send the oauth credentials as authentication header. While everything works perfectly with REST requests, I'm getting 401 responses with the user stream ones. The oauth related code is exactly the same, and token and consumers keys and secrets too. If I change to query parameters based oauth, then everything works correctly with the user stream API. Is there any limitation in how oauth data is to be sent to user stream API? I can't find any specific information on how authentication is no be handled with this endpoint. Should the headers approach work just like in the REST API case? 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
Re: [twitter-dev] DM rate limit
Any one Twitter account that sends 250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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
I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why the questions are being asked about DM limit changes going forward. On Feb 11, 10:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. 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 Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- 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: DM rate limit
Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. On Feb 12, 11:46 am, Dossy Shiobara do...@panoptic.com wrote: Any one Twitter account that sends 250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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: DM rate limit
Actually, the limit is 250 per account, not 250 DMs per IP. Tom On 2/12/11 9:10 PM, DaveH wrote: Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. On Feb 12, 11:46 am, Dossy Shiobarado...@panoptic.com wrote: Any one Twitter account that sends250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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: Looks like our application is DOA...
Change the message so that it can go into their activity stream instead of a DM. It may be that you have less information, but a @storeowner, You just received an order is better than nothing. Granted with DM you could include more information, but at least a generic message would suffice to have them complete the order fulfillment. Hope this helps give you some other ideas. On Feb 11, 9:49 pm, pl plot.l...@gmail.com wrote: I've just been reading the messages on here wabout the whitelisting changes, rate limits, streaming API etc and can only come to the conclusion that the application we were just about to launch to our users is going to have to be cancelled. It's a simple application that uses DM to send notifications to users based on real time events - these events being a purchase from their hosted web store. It was only aimed a low-volume merchants, but even if they each only have one transaction a day (and they get more than that) then we would run out of the 250 message limit. This decision to not entertain any form of whitelisting in the future seems to me like it is going to impact a lot of developers. This is not something we can use the streaming API for as we only send messages, which the streaming API can not do. So we are stuck with REST, and therefore stuck with an enforced extremely low limit on messages. As a direct result of this, we now have to cancel the launch of this application. It was something that a couple of merchants had requestes and we had said we would look into it. Up until recently it certainly looked like an option we could give them, but now we are going to have to go to them and say that it's actually no longer possible to send them messages on twitter, and see if they have any other platform they would prefer us to us instead. Does anyone have any suggestions as to a way that it might be possible to actually launch this app - it's something that our customers requested, and it makes us look bad that we are going to have to say 'sorry, not possible to send mesasges to you on your preferred messaging platform...' -- 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] DM rate limit
On Sat, 12 Feb 2011 14:46:33 -0500, Dossy Shiobara do...@panoptic.com wrote: Any one Twitter account that sends 250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. Putting multiple Trending Topics on a tweet with porn links is not OK either, but that doesn't mean bots don't do it. #twittercouldfixthat. ;-) -- 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
Re: [twitter-dev] Re: Update on Whitelisting
Whitelisting does not remove the daily update and follower limits associated with POST requests; these limits are managed on a per user basis. Elevated DM limits are separate from the REST API whitelisting. It is possible that Twitter is no longer providing access to elevated DM limits as well but my reading of the announcement is that only the REST API whitelisting is being deprecated. http://dev.twitter.com/pages/rate-limiting#whitelisting 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 Sat, Feb 12, 2011 at 12:03, DaveH d...@idreia.com wrote: I disagree, Abraham. I requested whitelisting for my app because I needed more than 250 DMs per day. Twitter granted my request and my limit was increased considerably. This may be that Twitter did not increase DMs as a default. But at one time, if requested and justified, they would. This is why the questions are being asked about DM limit changes going forward. On Feb 11, 10:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. 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 Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- 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 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: Is there going to be another Chirp?
On Sat, 12 Feb 2011 11:29:09 -0500, Brainewave Consulting i...@brainewave.com wrote: On Feb 7, 2011, at 5:25 PM, M. Edward (Ed) Borasky wrote: On Mon, 07 Feb 2011 15:25:59 +0100, Tom van der Woerdt wrote: I'd prefer London or some other West-European city. I'm guessing it will be in SFO, given how closely the Twitter team worked with the developers last year. They can't fly a few hundred folks to NYC or London. The question is *where* in SFO - Fort Mason wasn't particularly well suited for a barcamp-style conference with breakout sessions, wifi, etc. The noise level / acoustics were unacceptable. True enough, but Twitter is a global application - the developer conference should go global too! Rio! Twitter's huge in Brasil, and Facebook is conspicuously absent there! -- 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
Re: [twitter-dev] Re: DM rate limit
It's an unfortunate reality, but for every one legitimate application of DM's, there's 100 projects being posted to rent-a-coder asking for an auto DM script ... As developers that use the Twtiter API, we're all collateral damage to the scammers and spammers. Yes, it sucks, but there's no other real solution here. On 2/12/11 3:10 PM, DaveH wrote: Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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: DM rate limit
On Sat, 12 Feb 2011 15:29:23 -0500, Dossy Shiobara do...@panoptic.com wrote: It's an unfortunate reality, but for every one legitimate application of DM's, there's 100 projects being posted to rent-a-coder asking for an auto DM script ... As developers that use the Twtiter API, we're all collateral damage to the scammers and spammers. Yes, it sucks, but there's no other real solution here. Yeah - Google doesn't seem to be able to do spam control without PhD-level manual intervention, so I can imagine how hard it is for Twitter. ;-) Rent-a-coder? Try Amazon Mechanical Turk - you can get things done there for pennies an hour ;-) -- 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
Re: [twitter-dev] Re: Is there going to be another Chirp?
I have one question? what is DM? From: M. Edward (Ed) Borasky zn...@borasky-research.net To: twitter-development-talk@googlegroups.com Sent: Sat, February 12, 2011 12:25:27 PM Subject: Re: [twitter-dev] Re: Is there going to be another Chirp? On Sat, 12 Feb 2011 11:29:09 -0500, Brainewave Consulting i...@brainewave.com wrote: On Feb 7, 2011, at 5:25 PM, M. Edward (Ed) Borasky wrote: On Mon, 07 Feb 2011 15:25:59 +0100, Tom van der Woerdt wrote: I'd prefer London or some other West-European city. I'm guessing it will be in SFO, given how closely the Twitter team worked with the developers last year. They can't fly a few hundred folks to NYC or London. The question is *where* in SFO - Fort Mason wasn't particularly well suited for a barcamp-style conference with breakout sessions, wifi, etc. The noise level / acoustics were unacceptable. True enough, but Twitter is a global application - the developer conference should go global too! Rio! Twitter's huge in Brasil, and Facebook is conspicuously absent there! -- 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 The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php -- 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: DM rate limit
Indeed, if you figure someone can send a customized DM once per 15 seconds, and an hour at Turk costs you $0.05/hour, you can consume 250 DM's/day in 62.5 minutes - you're talking less than $0.10/day to have someone send DM's on Twitter for you, personalized by a human ... If a script off rent-a-coder costs you $100 ... that's 1,000 days worth of Turk-time ... so using a script only breaks even after 2.7 years of use. LOL. On 2/12/11 3:38 PM, M. Edward (Ed) Borasky wrote: Rent-a-coder? Try Amazon Mechanical Turk - you can get things done there for pennies an hour ;-) -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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: Is there going to be another Chirp?
On 2/12/11 3:59 PM, Brian Pegues wrote: I have one question? what is DM? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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 inline: images
RE: [twitter-dev] Re: Is there going to be another Chirp?
Rofl thanks Dossy. Cheers, Dean Collins http://www.LiveBasketballChat.com http://www.livebasketballchat.com/ From: twitter-development-talk@googlegroups.com [mailto:twitter-development-talk@googlegroups.com] On Behalf Of Dossy Shiobara Sent: Saturday, February 12, 2011 4:30 PM To: twitter-development-talk@googlegroups.com Subject: Re: [twitter-dev] Re: Is there going to be another Chirp? On 2/12/11 3:59 PM, Brian Pegues wrote: I have one question? what is DM? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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 image001.jpg
Re: [twitter-dev] Re: DM rate limit
On Sat, 12 Feb 2011 16:28:43 -0500, Dossy Shiobara do...@panoptic.com wrote: Indeed, if you figure someone can send a customized DM once per 15 seconds, and an hour at Turk costs you $0.05/hour, you can consume 250 DM's/day in 62.5 minutes - you're talking less than $0.10/day to have someone send DM's on Twitter for you, personalized by a human ... If a script off rent-a-coder costs you $100 ... that's 1,000 days worth of Turk-time ... so using a script only breaks even after 2.7 years of use. LOL. Yes, and you can get Twitter accounts created on MTurk as well. It's supposedly a violation of Amazon's TOS but they don't enforce it because they collect per-HIT transaction fees. Dick Costolo and Jeff Bezos need to have a long talk IMHO, backed up by attorneys and possibly the IRS and FTS. ;-) -- 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
Re: [twitter-dev] Re: DM rate limit
I agree, don't be so quick to judge. We have an opt-in based service and out clients have thousands of customers that explicitly say yes send me direct messages. The information we send is requested by the end user and is not spam. So you can imagine that a client with a large user base could quickly go beyond the 250 dm/day limit. It's unfortunate that the spammers take advantage and ultimately ruin things for legitimate services. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information On 2011-02-12, at 3:10 PM, DaveH d...@idreia.com wrote: Dossy: Don't be so quick to condemn. I have an app that uses DMs and ALL DM traffic is generated by users and they know it--so there is no spamming. There are legitimate uses of DMs that users are OK with that push an app beyond 250/day. Think of it this way, if an application has 300 followers and they all interact via private message (DM) one time per day, then 50 users will be unable to communicate on any given day. On Feb 12, 11:46 am, Dossy Shiobara do...@panoptic.com wrote: Any one Twitter account that sends 250 DM's in a 24 hour period is DOIN' IT RONG. DM spamming your followers is JUST NOT OK. On 2/12/11 2:31 PM, Trevor Dean wrote: Just out of curiosity why can't DM's be limited by the hour instead if having this cap of 250/day? I think if this was an option most of the issues expressed by other developers including myself would be resolved. -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- 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: DM rate limit
On Sat, 12 Feb 2011 17:07:36 -0500, Trevor Dean trevord...@gmail.com wrote: I agree, don't be so quick to judge. We have an opt-in based service and out clients have thousands of customers that explicitly say yes send me direct messages. The information we send is requested by the end user and is not spam. So you can imagine that a client with a large user base could quickly go beyond the 250 dm/day limit. It's unfortunate that the spammers take advantage and ultimately ruin things for legitimate services. Trevor Dean | Director big time design communication Inc. 647 234 8198 Visit http://www.bigtimedesign.ca for more information Speaking of spam, there's a great article at the New York Times on J.C. Penney, black hat SEO and Google: http://www.nytimes.com/2011/02/13/business/13search.html Many thanks to Twitter's spam fighters for keeping it as clean as it is, under the circumstances. -- 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-dev] Re: Twitter app development require guidance
The error message which Twitter provides is very important for us to proceed further. - Mohan -- 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: Confused
Can you tell us exactly what it is that you are looking for? This is the Twitter API development group where we discuss issues faced by developers. - Mohan -- 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
This is the message I received yesterday from Twitter Support: sutorius, Feb-11 10:40 am (PST): Hey Brian, In the short amount of time since you've written in, our director of Platform, Ryan Sarver, has posted an update on whitelisting and that we will no longer be approving such requests: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1acd954f8a04fa84 I'm sorry if this causes any setbacks to your development process. There's some good discussion on that thread, and I invite you to participate if you want. Let me know if you have any other questions. --- Maybe somebody somewhere in the line had some misinformation, but this makes it sound like there will no longer be any DM whitelisting either. So my question still stands, what is the fate of DMing? My company's product sends notifications of grade changes to students, which obviously need to be sent privately. We planned to expand into messaging on Twitter, but it kind of sounds like that's no longer an option. :-( On Feb 11, 11:12 pm, Abraham Williams 4bra...@gmail.com wrote: Whitelisting never impacted DM limits or Search API limits. Niether of those are affected by @rsarver's announcement. 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 Fri, Feb 11, 2011 at 12:04, whitmer brian.whit...@gmail.com wrote: I'd also like to know the fate of DMing. On Feb 10, 7:07 pm, Trevor Dean trevord...@gmail.com wrote: Hey Taylor, what does this mean for DM limits and what’s the new path towards getting those limit increased for new accounts? Trevor Dean | Director big time design communication Inc. 647 234 8198 Visithttp://www.bigtimedesign.caformore information On 2011-02-10, at 8:48 PM, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: On Thu, 10 Feb 2011 17:40:03 -0800, Matt Harris thematthar...@twitter.com wrote: Hi Ian, For trends you might like to try our trends.api.twitter.com [1] server which hosts a cached copy of the trends information and is updated whenever the trends change. It should support your use case and we would be interested in any feedback you may have about it's performance. Nice! I was just about to try building something very much like twendr, but I can either use twendr or go right to your new server. Is this on a five-minute cycle like the main Trending Topics feed? Will we ever get to see the Promoted fields populated without spending money? ;-) -- 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: Where to send questions re: terms of service?
Brian, Taylor, Thanks very much for your quick responses. I'll send a message to the above once I can think it through more precisely -- or decide that what I was thinking of doing isn't needed after all. (FWIW, the issue is not so much a shouldn't but more of a gray area that I'm not sure the policy contemplated.) cheers and thanks again, Miles On Feb 9, 12:22 pm, Brian Sutorius bsutor...@twitter.com wrote: Hi Miles, I work on the API Policy team and monitor the messages at a...@twitter.com. We'd be happy to answer any questions you have about our policies or a specific feature you're thinking of. Brian Sutorius On Feb 9, 11:56 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Miles, While this public forum is great if you want to discuss the terms themselves with others, if you want to privately discuss API terms with Twitter, it's best to send a message to a...@twitter.com -- it might take a bit for you to get a response but the policy team will get your inquiry. That said, it's best to steer clear of anything explicitly prohibited in the terms and to follow the shoulds as closely as possible. Taylor @episod http://twitter.com/episod - Taylor Singletary - Twitter Developer Advocate On Wed, Feb 9, 2011 at 11:39 AM, Miles Parker milespar...@gmail.com wrote: Hi, I've got a case where I'm not sure whether a potential use would conflict with terms of service. I'd rather not get into details on public forum ;) but I can if this is the only place for it. But I'm wondering if there is someone or somewhere to ask questions? i.e. re: If you are doing something prohibited by the Rules, talk to us about whether we should make a change or give you an exception. -- Who is us? thanks, Miles -- 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
