[twitter-dev] Re: Looks like our application is DOA...
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 wrote: > On Feb 12, 2:19 pm, Gummy Bear 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
[twitter-dev] Re: Looks like our application is DOA...
On Feb 12, 2:19 pm, Gummy Bear 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
[twitter-dev] Re: Looks like our application is DOA...
Change the message so that it can go into their activity stream instead of a DM. It may be that you have less information, but a "@storeowner, You just received an order" is better than nothing. Granted with DM you could include more information, but at least a generic message would suffice to have them complete the order fulfillment. Hope this helps give you some other ideas. On Feb 11, 9:49 pm, pl wrote: > I've just been reading the messages on here wabout the whitelisting > changes, rate limits, streaming API etc and can only come to the > conclusion that the application we were just about to launch to our > users is going to have to be cancelled. > > It's a simple application that uses DM to send notifications to users > based on real time events - these events being a purchase from their > hosted web store. It was only aimed a low-volume merchants, but even > if they each only have one transaction a day (and they get more than > that) then we would run out of the 250 message limit. > > This decision to not entertain any form of whitelisting in the future > seems to me like it is going to impact a lot of developers. This is > not something we can use the streaming API for as we only send > messages, which the streaming API can not do. So we are stuck with > REST, and therefore stuck with an enforced extremely low limit on > messages. > > As a direct result of this, we now have to cancel the launch of this > application. It was something that a couple of merchants had requestes > and we had said we would look into it. Up until recently it certainly > looked like an option we could give them, but now we are going to have > to go to them and say that it's actually no longer possible to send > them messages on twitter, and see if they have any other platform they > would prefer us to us instead. > > Does anyone have any suggestions as to a way that it might be possible > to actually launch this app - it's something that our customers > requested, and it makes us look bad that we are going to have to say > 'sorry, not possible to send mesasges to you on your preferred > messaging platform...' -- 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-dev] Re: Looks like our application is DOA...
There's simple workaround for that. Just think about it and you'll figure it out ;-) -- 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-dev] Re: Looks like our application is DOA...
Well, guess we just have to wait and see, but to be honest I get the feeling that we are just going to have to can this project. It's a shame that this has happened, all we can do is explain to or customers that it is a situation outside of our control and that it's twitter that are preventing this from being done, not us... On Feb 12, 10:18 am, Trevor Dean wrote: > Our product is in danger of suffering the same fate. I have posted to this > group a couple of times today hoping to get a response from twitter regarding > the future of DM's but haven't got a response yet. I can only imagine they > are trying to get through all of the emails requesting the same information. > Out experience is that twitter has been very helpful and want to help > developers but they will probably continue to evaluate needs on a case by > case basis. There have been many people asking the same question so > hopefully we will see a response soon. > > Trevor Dean | Director > big time design & communication Inc. > 647 234 8198 > > Visithttp://www.bigtimedesign.cafor more information > > -- 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
