Confirming limits is not Twitter HQ's strength. I can see why. They want to keep their options open. Instead of asking for approval, why not start a petition to get what you need?
Put up a message here stating a case for more DMs. Explain why you want it. Ask other devs to sign on with a confirming response. When you get no reaction, repost the same request the following week, and again, and again, until Twitter makes the change or comes up with a useful alternative. What can they do to you? Cut off your whitelisting? Believe me, grandfathered whitelisting is just a way of keeping established devs quiet, and is unfair on its face. All whitelisting will go away. Anyone want to bet against that? Devs are Twitter's partners, not users to be controlled. Dev's make money for Twitter. Let's help them make more money by getting them more serious, business oriented users, not just more Beiber fans. We can do this for Twitter. Twitter needs to help us do it. Ok, Trevor? On Sun, Feb 13, 2011 at 10:49 AM, Trevor Dean <trevord...@gmail.com> wrote: > I appreciate the feedback but the issue is that our clients send DM's to > their customers and the customer base could and has grown beyond 250 users. > We have whitelisted the clients that needed increased rate limits so we are > ok for now but this could effect how we deal with future clients. There has > been a lot of activity from this group and it's been hard to keep track of > all of the information but I did read that you can still request increased DM > rate limits which is all we need but I don't know if this has been confirmed > by someone from twitter. > > Trevor Dean | Director > big time design & communication Inc. > 647 234 8198 > > Visit http://www.bigtimedesign.ca for more information > > On 2011-02-12, at 6:59 PM, Xristofer Obbit <dixt...@dixtort.net> wrote: > >> Why not have each client register a notification account with your app >> that sends a DM to their main account. That gives every client 250 >> DMs. Better yet, make it a private account and push notifications as >> status updates giving you 1000/day while keeping privacy. >> >> Sent from my iPhone >> >> On Feb 12, 2011, at 5:17 PM, "M. Edward (Ed) Borasky" >> <zn...@borasky-research.net> wrote: >> >>> 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 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