table of contents
BTI(1) | bti | BTI(1) |
NAME¶
bti - send a tweet to twitter.com from the command line
SYNOPSIS¶
bti [--account account] [--password password] [--action action] [--user screenname] [--host HOST_NAME] [--proxy PROXY:PORT] [--logfile LOGFILE] [--config CONFIGFILE] [--replyto ID] [--retweet ID] [--page PAGENUMBER] [--bash] [--shrink-urls] [--debug] [--dry-run] [--verbose] [--version] [--help]
DESCRIPTION¶
bti sends a tweet message to twitter.com.
OPTIONS¶
--account account
--password password
--action action
--user screenname
--host HOST_NAME
If no host is specified, the default is to send to twitter.com.
--proxy PROXY:PORT
If --proxy is not specified but the environment variable 'http_proxy' is set the latter will be used.
--logfile LOGFILE
--config CONFIGFILE
--replyto ID
For twitter, this is ignored unless the message starts with the @name of the owner of the post with the status ID.
For status.net, this can link any two messages into context with each other. Status.net will also link a message that contains an @name without this without regard to context.
--retweet ID
--shrink-urls
The following URL shrinking services are available: http://2tu.us/ (default) and http://bit.ly / http://j.mp
See the documentation for bti-shrink-urls for the configuration options.
--debug
--page PAGENUMBER
--dry-run
--verbose
--bash
This option implies --background.
--background
--version
--help
DESCRIPTION¶
bti provides an easy way to send tweet messages direct from the command line or any script. It reads the message on standard input and uses the account and password settings either from the command line options, or from a config file, to send the message out.
Its primary focus is to allow you to log everything that you type into a bash shell, in a crazy, "this is what I'm doing right now!" type of way, letting the world follow along with you constant moving between directories and refreshing your email queue to see if there's anything interesting going on.
To hook bti up to your bash shell, export the following variable:
PROMPT_COMMAND='history 1 | sed -e "s/^\s*[0-9]*\s*//" | bti --bash'
This example assumes that you have the ~/.bti set up with your account and password information already in it, otherwise you can specify them as an option.
CONFIGURATION¶
The account and password can be stored in a configuration file in the users home directory in a file named .bti. The structure of this file is as follows:
account
password
--action action
--user screenname
host
proxy
logfile
replyto
There is no sane reason for a need to have this set in a config file. One such reason is to have all your messages as children to a particular status.
shrink-urls
verbose
There is an example config file in /usr/share/doc/bti/examples/bti.example that shows the structure of the file.
Configuration options have the following priority:
For example, command line options always override any config file option, or any environment variables. Unless a config file is specified by the command line. At that point, the new config file is read, and any previous options set by a command line option, would be overridden.
AUTHOR¶
Written by Greg Kroah-Hartman <<greg@kroah.com>> and Amir Mohammad Saied <<amirsaied@gmail.com>>.
May 2008 | bti |