Twitter suite for Weechat.
Welcome to the wonderful world of weetwit, a plugin that will transform weechat to a (soon-to-be) fully-featured twitter client.
Before you can use it, you have to “create” a new application at twitter, the reason for this is that I can’t include the application keys without them becoming public knowledge. You can create the application at Twitter. The application needs read/write access.
First we need to install the module:
Installation through pip, note that you must get the plugin seperately.:
# pip install weetwit $ Copy the plugin to ~/.weechat/python
Installation from source:
# cd /path/to/source/files # pip install tweepy # python setup.py install $ cp plugin/weetwit.py ~/.weechat/python
Configuration of weechat:
] /python load weetwit.py ] /set plugins.var.python.weetwit.access_token access_token_goes_here ] /set plugins.var.python.weetwit.access_token_secret access_token_secret_goes_here ] /set plugins.var.python.weetwit.consumer_key consumer_key_goes_here ] /set plugins.var.python.weetwit.consumer_secret consumer_secret_goes_here ] /python reload weetwit
You should now have a running weetwit.
There are multiple configuration parameters you can alter, here is a short description of them.
Many commands take <status identification> as argument, this can either be the ID of the status or a screen_name. In case of the screen_name, we will use the ID of last status by screen_name. (Note: if screen_name hasn’t showed up in your timeline, this won’t work.)
Q: Why does your script spawn an extra python process? A: Because weechat doesn’t support background threads, and blocks on long running operations, this process is what monitors your timeline. Q: I don’t want those ugly STATUSIDs in my weetwit buffer. A: Add a filter like this: “/filter add statusid python.timeline * \[#STATUSID:” now you can toggle between them hidden and visible, depending on your needs.