bash twitter ididocy
Perl C Shell
Latest commit 3f9cb71 Feb 26, 2015 @gregkh Merge pull request #36 from scop/master
Install bash completion
Permalink
Failed to load latest commit information.
scripts new version of checkpatch.pl from 2.6.35-rc1 kernel Aug 18, 2010
.gitignore add .tar and .asc to .gitignore Jan 17, 2014
COPYING meta files added (COPYING, ChangeLog, RELEASE_NOTES) May 19, 2008
ChangeLog release 034 Jan 15, 2014
HACKING HACKING: this is bti, not smugbatch Oct 22, 2011
Makefile.am Install bash completion Feb 18, 2015
NOTES NOTES: update how to upload this stuff... Jan 27, 2014
README Remove some remaining identi.ca mentions Jan 23, 2014
RELEASE-NOTES release 034 Jan 15, 2014
autogen.sh convert to use autotools Apr 13, 2009
bti-bashcompletion Add direct message action. May 28, 2011
bti-shrink-urls Add XDG compilance (~/.config/bti) support Mar 30, 2013
bti-shrink-urls.1 updated man pages generated from the docbook source Jan 12, 2011
bti-shrink-urls.xml Add documentation for new shrink_host feature in bti-shrink-urls. Jan 12, 2011
bti.1 bti.1: update manpage with typo fix from .xml template Jan 27, 2014
bti.c remove group support Jan 23, 2014
bti.example
bti.h
bti.xml bti.xml: fix typo Jan 23, 2014
config.c remove group support Jan 23, 2014
configure.ac Install bash completion Feb 18, 2015
oath.keys add oath.keys from twitter.com May 24, 2010

README

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.

USE AT YOUR OWN RISK!

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

bti is developed using git and the tree can be found at:
	git://github.com/gregkh/bti.git
and browsed at:
	http://github.com/gregkh/bti/


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:

---8<-------------------
# Consumer key
consumer_key=cZy8DdioswAfu3LJYg6E2w

# Consumer secret
consumer_secret=fnIGGU0T12mMWKjmThUdSeKN32NLWfmnwapwubVQ
---8<-------------------

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.