For applications like yours, moving to the Streaming API will increase the quality of service for you and decrease load for us. A big part of building an effective application on our API is figuring out which methods to use and what strategies to use for retrieving information and sending updates and direct messages. If you reach out to us (a...@twitter.com), we're happy to help with that.
Often times, we don't hear from unhappy developers until they're already outraged and posting on their blogs or in this group. Please: give us a chance to help you out first. We may not always be able to make your particular issues our highest priority, but we'll give it our best shot. If you're still pissed, then you can go vent :) And yes, reporting bugs with detailed debugging output (HTTP requests and responses with all headers and full response bodies) are incredibly useful. We essentially can't help you without this information for any non-trivial bugs. Another huge help to us: if you know anyone who either wants to join our team as an engineer or help us out with full- or part-time developer support, please send them to http://twitter.com/jobs. We're a very small team with a very big job, but we've got the funding to add more people. Please, please, please send good people our way! Every addition to the team helps us help you. On Wed, Sep 16, 2009 at 03:13, Fabien Penso <fabienpe...@gmail.com> wrote: > > On Wed, Sep 16, 2009 at 7:00 AM, Matthew Ranney <m...@ranney.com> wrote: >> Hey Alex, would you consider just giving everybody their money back if they >> aren't 100% satisfied? > > Hi guys. > > I have been developing an iPhone application for push called > notifications : www.appnotifications.com > > I've added Gmail push, RSS, Google voice, I provide an API for sending > yourself notifications, and of course I've added Twitter too. I've had > some support from some Twitter developers and I'm happy I did. > However, to reply to the subject of this thread I also had many issues > with the API, some tweets not showing up for example. The complains I > get from users is all about the Twitter plugin I did, I almost regret > to have added it. > > I might have done something wrong on my side, but I also have the > feelings, like other people here, than the API is not always working > well. And I don't blame anyone, I think with the number of tweets you > have, and the massive number of new users you had within the last > year, it must be a super exciting job to work at Twitter, but also > such a stressed one :) I wouldn't want to be responsible for > scalability there. > > Is there anything we can do to help you guys? Reporting specific bugs > (they are sometimes hard to find and hard to reproduce as it's a > stream). > -- Alex Payne - Platform Lead, Twitter, Inc. http://twitter.com/al3x