We already have email as an option (and SMS, and a variety of other methods) - we had been specifically asked by a couple of customers to use twitter as a notification feed and this development was in response to those requests.
We actually do take customer requests in and listen to what they are asking, and see if it is something we can do for them. If we feel it is something that might be of use to more than one customer, we won't even charge for any of the dev work - infact it's very rare that a request is made that we can't see as being of interest to others, and we will share the resultant modules with other customers as long as the original requestor has no objection. I can only think of one such request over the last year or so that ended up as a charged piece of work. We have now gone back to these customers and explained the situation to them - that whilst we have an application that works and will do what they wanted, we can't release it owing to these restrictions as it would not be a reliable service. They now understand and accept the situation, and have thanked us the effort in making the app, and were appreciative that we have found out about these restrictions before we put things live and then later ran into problems and had to stop a service that they had started using. On Feb 13, 12:32 pm, Tim Skipper <t...@intonet-technology.co.uk> wrote: > On Feb 12, 2:19 pm, Gummy Bear <ser...@seductive.com> wrote: > > > There's simple workaround for that. Just think about it and you'll > > figure it out ;-) > > Yes, use email instead. > > I can't help thinking that all these devs up in arms because Twitter > have limited use of their (free) service are making twitter apps just > because it's the latest bandwagon to jump on, rather than because it's > the most suited platform for the task in hand. I personally think > Twitter should bin DMs altogether, it seems at odds with what Twitter > is all about. > > Regards > Tim -- 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
