bleeter will seek authorisation when initially run. As twitter uses OAuth this process is a little more cumbersome than it should be.
If you wish to create a new authentication token, or need to regenerate it, you can be doing one of the following:
$ bleeter --get-token
$ rm ${XDG_DATA_HOME:-~/.local}/bleeter/oauth_token
show program’s version number and exit
show this help message and exit
timeout for notification popups in seconds
update frequency in in seconds
generate a new OAuth token for twitter
use SSL to connect to twitter
don’t use SSL to connect to twitter
users to watch without following(comma separated)
don’t check stealth users for updates
keywords to ignore in tweets(comma separated)
don’t test for ignore keywords
disable the system tray icon
expand links in tweets
don’t expand links in tweets
open links in lighter mobile versions
don’t open links in lighter mobile versions
open geo links using specified site
maximum number of timeline tweets to fetch(max 200)
maximum number of stealth tweets to fetch
maximum number of tweets to fetch for searches
maximum number of tweets to fetch for lists
fetch user’s lists
don’t fetch user’s lists
fetch user’s saved searches
don’t fetch user’s saved searches
don’t cache twitter communications
produce verbose output
output only results and errors