Skip to content
bash twitter ididocy
Perl C Shell
Find file
Latest commit 3f9cb71 @gregkh Merge pull request #36 from scop/master
Install bash completion
Failed to load latest commit information.
scripts new version of from 2.6.35-rc1 kernel
.gitignore add .tar and .asc to .gitignore
COPYING meta files added (COPYING, ChangeLog, RELEASE_NOTES)
ChangeLog release 034
HACKING HACKING: this is bti, not smugbatch Install bash completion
NOTES NOTES: update how to upload this stuff...
README Remove some remaining mentions
RELEASE-NOTES release 034 convert to use autotools
bti-bashcompletion Add direct message action.
bti-shrink-urls Add XDG compilance (~/.config/bti) support
bti-shrink-urls.1 updated man pages generated from the docbook source
bti.1 bti.1: update manpage with typo fix from .xml template
bti.c remove group support
bti.example was renamed to StatusNet
bti.h remove group support
bti.xml bti.xml: fix typo
config.c remove group support Install bash completion
oath.keys add oath.keys from


bti - bash twitter idiocy

Allows you to pipe your bash input to twitter in an easy and fast manner
to annoy the whole world.

See the man page bti.1 for how to use it and more information.

Be careful if you use this, it is quite easy to end up sending sensitive
data to the world with it.


Any questions, contact Greg Kroah-Hartman <> or @gregkh
on twitter.

bti is developed using git and the tree can be found at:
and browsed at:

About OAuth configuration

If you want to use an OAuth-enabled service (like twitter), you should
configure bti to use the consumer key and secret shipped with the source
code (check the oath.keys file).

For example, you should add the following two lines to your ~/.bti
configuration file:

# Consumer key

# Consumer secret

The next time that you run bti, you will be told to visit an URL that
will provide you a PIN number. You should then input that number in the
bti prompt, and you will be given two new configuration values
(access_token_secret and access_token_key) that you need to add to your
bti configuration file to authenticate requests from bti.
Something went wrong with that request. Please try again.