Problem to register bti with new twitter account
Closed this issue · 6 comments
Frank Jeschke reported a problem in the Debian BTS at http://bugs.debian.org/706104 ; looks like registering bti with twitter doesn't work anymore.
Since I don't have a Twitter account I'm afraid I can't debug this further ...
I can't setup bti with twitter :(
root@melroy-server:~# bti --debug --verbose
bti: session_readline_init: Using libreadline.so.6 for readline library
bti - version 032
My config:
account=big_col_storage
password=xxxx
host=twitter
logfile=bti.log
consumer_key=xxxxxxxxx
consumer_secret=xxxxxxxxxxx
I have set my Twitter application with Access level to: Read, write, and direct messages.
What can I do to help debug this further?? It seems to hang at session_readline_init?
Twitter has now switched over to https: for authentication. A very small change in bti.c will allow authentication to work again s/http/https/
for twitter authentication. This works.
(Unchanged, the current code falls out on receiving the 301 redirect to the https: page)
But even better, this step can be skipped as you are able to generate the authentication strings (all strings) from the webpages. (Button at bottom of details page for you "app" saying Create your Access Tokens). Create the parameters in your config file and paste them in (all 4) and everything now works in one step!
consumer_key={copy/paste appropriate string here} consumer_secret={copy/paste appropriate string here} access_token_key={copy/paste appropriate string after generating access token here} access_token_secret={copy/paste appropriate string after generating access token here}
I don't think simply switching to https or dumping the assorted tokens in ~/.bti will be sufficient. In the past week, twitter turned off all APIv1 support. I had bti working fine until about a week ago, and now, everything fails with the following error:
bti: send_request: http://api.twitter.com/1/statuses/update.xml
bti: send_request: The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.
I guess this should be updated in the README.
Should now be resolved with the 033 release.
Thanks