I am the author of Quitter.  Quitter is a desktop app for Windows.  It
runs in a Command window.  The idea was to give folks access to
Twitter without all of the graphical overhead of a web interface.

I am receiving a lot of emails from my users because Twitter revoked
my application's access to direct messages.  An example email is

"You must know that Quitter is the ONLY client that I can trust
to read my tweets due to an internet connectivity issue, in my
case I moved to a town called GAN GAN here in Argentina
where people can only access the internet through dial-up 2G
mobile technology and speed rate is 14kbps average! Well,
its impossible to read any tweet using the Twitter webpage
with this speed but Quitter works like a charm!"

This user and every other Quitter user like him has had their access
to Direct Messages taken away for reasons that (like every other
policy change Twitter makes) are obtuse, unclear and arbitrary.  My
client would keep these users -more- involved in the Twitter
ecosystem, but now their access to it reduced.

This isn't a business.  I'm not in it the for the money.  Quitter is a
free and open source product that I wrote because I loved Twitter and
thought it would be a neat client.

I would be very grateful if someone from Twitter could explain the
benefit of taking Direct Message access away from desktop clients.  It
makes no sense.

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: 

Reply via email to