OK Alex, thanks for that insight. I'm trying hard to be patient, but I hope you can understand that this issue is strangling my new business.
Also, I don't see anything in the documentation which differentiates these social graph calls from those rising above support on a "best- effort basis". I'm not trying to be argumentative, but it would help me tremendously with prioritization of ongoing development if I knew which other API calls won't receive priority support if they should suddenly fail. If there is some internal prioritization, I think the community needs to know what it is. I know I do! Thanks, - Waldron On Sep 15, 2:04 pm, Alex Payne <a...@twitter.com> wrote: > Waldron, > > We're looking into this issue, but it requires a great deal of > coordination with the folks who work on our back-end infrastructure. > When you ask for a list of denormalized IDs, that request spends very > little time in "API code", and most of its time talking to a back-end > system that my team has no control over. We're working with the folks > in charge of that on reliability and better ways for developers to > access that data. > > Please understand that the denormalized lists are currently provided > to developers on a best-effort basis. For the vast majority of Twitter > applications, this data isn't necessary. A specialized class of > applications need this data, and we're doing our best to provide it. > > On Tue, Sep 15, 2009 at 00:21, Waldron Faulkner > > > > <waldronfaulk...@gmail.com> wrote: > > > Ryan, please look no further than existing, accepted issues in the > > issues list for examples as to how this platform is not yet ready. One > > of your primary API calls, followers/ids (and friends/ids) is broken, > > and has been for more than a week now. Since paging is not working, > > and un-paged requests on accounts with many followers yields fail > > whale, we CANNOT GET LISTS OF FOLLOWERS. That is a major failure, and > > it doesn't feel like it's getting any kind of response. > > > As I have said repeatedly in this forum and in the issues list, this > > has frozen business development for my fledgling business, which I > > have trusted to the Twitter API. I can't show a broken product. At > > some point, you will put this little dream of mine out of business. > > I'm up late working on my project, which will ultimately add value to > > Twitter's business. I hope your team isn't leaving me high and dry. > > Please tell me I don't have to go do a Facebook app instead. Please > > tell me that someone was working on this over the weekend. > > > I'd love to have some solid, no-nonsense response to this, with hard > > dates. So far we've had well-meaning but empty words. > > > Thanks, > > > - Waldron Faulkner > > Founder, GraphEdge LLC. > >http://graphedge.com > > > On Sep 15, 2:59 am, Ryan Sarver <rsar...@twitter.com> wrote: > >> WyoKnott, > > >> Thanks for your email. We really appreciate the candid feedback and > >> definitely is not something we want to see happening. I would like to > >> hear more about what you mean by "not stable enough" and what specific > >> issues we can work on that would get you to consider Twitter a > >> platform worthy of building your business on. > > >> I look forward to your feedback. > > >> Best, Ryan > > >> On Fri, Sep 11, 2009 at 6:36 AM, WyoKnott <mycro...@lifewithindustry.com> > >> wrote: > > >> > A few months ago I was introduced to the Twitter API by a prospective > >> > client who wanted a custom application. I took the time to learn the > >> > API and wrote a quick and dirty standalone windows app. The project > >> > fell through (the client could not get financing) but I have continued > >> > to be a twitter user and have subscribed to this group email. I > >> > stopped development on the project because the API does not yet seem > >> > stable enough for me to try to produce a marketable product on my own > >> > while at the same time chasing an API around. Is my opinion way off > >> > the mark or are some of the other developers out there feeling the > >> > same way. > > >> > I am considering restarting development on the project if the Twitter > >> > API is likely to get more stable in the near future. > > >> > Thanks for tolerating my ravings > > >> > WyoKnott > > -- > Alex Payne - Platform Lead, Twitter, Inc.http://twitter.com/al3x
