Twitter canceled Twidge's API keys because they were published in source. They appear to have a seriously misguided API policy.

You can work around this by obtaining your own API keys from them and putting them in the config file. I will address it tomorrow.

-- John

On 10/25/2010 07:26 PM, Ernesto Hernández-Novich (USB) wrote:
Package: twidge
Version: 1.0.5
Severity: grave
Justification: renders package unusable

I started getting

twidge: user error (Bad response: 401)

while trying to use twidge to access my Twitter account.

I modified my .twidgerc according to the Twidge FAQ [1] to no avail.

I then tried to start from scratch by removing .twidgerc altogether,
and doing a 'twidge setup' but got the same error

$ twidge setup

Welcome to twidge.  We will now configure twidge for your
use with Twitter (or a similar service).  This will be quick and easy!


Please wait a moment while I query the server...


twidge: user error (Error from oauthRequest: "HTTP/1.1 401 Unauthorized")

[1] http://github.com/jgoerzen/twidge/wiki/FrequentlyAskedQuestions

-- System Information:
Debian Release: squeeze/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-core2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages twidge depends on:
ii  curl                      7.21.2-1       Get a file from an HTTP, HTTPS or
ii  libc6                     2.11.2-6       Embedded GNU C Library: Shared lib
ii  libcurl3-gnutls           7.21.2-1       Multi-protocol file transfer libra
ii  libffi5                   3.0.9-3        Foreign Function Interface library
ii  libgmp3c2                 2:4.3.2+dfsg-1 Multiprecision arithmetic library

twidge recommends no packages.

twidge suggests no packages.

-- no debconf information







--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to