Hi Twitter-developers, I'm kind of a twitter-api-newby trying to use this rest-api in a oauth- enabled server app to send out (too) many updates/tweets.
The application is for swim-meets, where we wanted to send out the swimmers' events, like signed-up event# with associated info, heat and lane info as they become available, and results of the race as they become available. This info is tweeted out from one account such that the participants and relatives/friends can easily get that information on their smart- phones by following or searching the tweets and without having to go to print-outs that are taped on the wall. As we have a few hundred swimmers, possibly 50+ events, 4-8 heats, 6-8 lanes... lots of tweets... and I was hitting this update limit after the first test case after about 40-50 tweets. The idea for the app seemed so neat and twitter seemed such a natural vehicle to spread this info...but all the twitter-docs about these update limits seem to indicate that our current set-up simply won't work with twitter. Any advice/suggestions to get this somehow to work is greatly appreciated. Regards, FrankS. -- 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
