On 06/30/2011 05:51 PM, Aaron Howell wrote:
Now that Twitter has implemented the new restrictions on access to direct messages, Twidge is no longer able to interact with dm's. The application needs to be reregistered with twitter followed by users needing to reauthorize. I have attempted to reauthorize but still have not gotten direct message functionality back so I'm assuming twidge hasn't gone through the reregistration process. Details of what's happened are at http://blog.twitter.com/2011/05/mission-permission.html
Sigh @twitter. Hard to keep a stable app working with their ever-changing API.
Anyhow, I've gone in and edited the settings for twidge. Give it a try and let me know how it works for you.
-- John
-- System Information: Debian Release: wheezy/sid APT prefers oneiric APT policy: (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0-1-server (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages twidge depends on: ii curl 7.21.6-1ubuntu2 Get a file from an HTTP, HTTPS or ii libc6 2.13-6ubuntu2 Embedded GNU C Library: Shared lib ii libcurl3-gnutls 7.21.6-1ubuntu2 Multi-protocol file transfer libra ii libffi5 3.0.9-7 Foreign Function Interface library ii libgmp3c2 2:4.3.2+dfsg-2ubuntu1 Multiprecision arithmetic library twidge recommends no packages. twidge suggests no packages. -- no debconf information
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
