- http://code.google.com/p/tircd/ has directions for oauth, but leaves out the fact that a (fake) password is still required, even after setting the username to "oauth". http://code.google.com/p/tircd/issues/detail?id=80&q=oauth
- The download version of tircd (0.10, although when run it thinks it's 0.08) doesn't seem to work with oauth. See http://code.google.com/p/tircd/issues/detail?id=84&q=oauth, and then download a forked version from http://github.com/drags/tircd.
- weechat expects "/stats" to be run in a window connected to the server. For twitter there wasn't yet one, because the oauth handshake still needed a PIN to be sent. As the tircd homepage suggested, I used "/quote -server twitter stats pin MYPIN", where my weechat config uses "twitter" as the internal server name for tircd configuration.
- The twitter oauth PIN seems to have been cached somewhere. I've no idea where, so I'm sure this will bite me eventually.
Thanks for this post, it was exactly the information I needed to get tircd working correctly.ReplyDelete
Hey Grant, is this still working for you? I'm trying to get weechat and tircd working and it keeps dying with this: GET https://twitter.com/oauth/request_token failed: 400 Bad Request at /usr/share/perl5/vendor_perl/Net/Twitter/Lite.pm line 212.ReplyDelete
It's still working for me. *Shrug*ReplyDelete