Skip to content
A Twitter bot that posts interesting bounty questions from Stack Overflow.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.gitattributes Initial commit of all BountyBot files. Mar 10, 2013
.gitignore Initial commit of all BountyBot files. Mar 10, 2013
app.yaml Added weekly bounty stats tweets. Jan 26, 2014
bounty_bot.py Imroved hashify Jan 31, 2015
cron.yaml Added weekly bounty stats tweets. Jan 26, 2014
favicon.ico Added files needed to run BountyBot in Google App Engine. Dec 27, 2013
index.yaml Added files needed to run BountyBot in Google App Engine. Dec 27, 2013
license.txt Initial commit of all BountyBot files. Mar 10, 2013
main.py
readme.txt Included information about Stack Exchange OAuth. Mar 10, 2013
tweepy_test.py
tweet_bounty.py

readme.txt

About:

BountyBot downloads 'featured' (bountied) questions from Stack Overflow, picks 
the most interesting one based on the amount of the bounty and the score of
the question, then posts a link to the question on Twitter.

Example account updated by this script: https://twitter.com/BountyBot

Scheduling needs to be done by an external process like cron or Windows Task Scheduler.

Author: Bill Cruise
(Bill the Lizard on Stack Overflow, @lizardbill on Twitter)

Dependencies: tweepy (https://github.com/tweepy/tweepy)
Stack Exchange API: https://api.stackexchange.com/docs
Twitter API: https://dev.twitter.com/


Configuration:

Configuration is controlled through settings.cfg which must be in the same
directory as bounty_bot.py.  Your Twitter Application ID tokens need to be
stored in this file to give the script permission to post status messages
on your Twitter account.  This section is required, so expect the bounty bot
script to throw errors if you don't include it.  The Stack Exchange OAuth
section is optional, but you may run into API throttling if you try to
run the script too often without it.

http://dev.twitter.com/apps/myappid
http://dev.twitter.com/apps/myappid/my_token
http://stackapps.com/apps/oauth/register

Example settings.cfg
--------------------

[Twitter OAuth]
CONSUMER_KEY: Your Consumer Key
CONSUMER_SECRET: Your Consumer Secret
ACCESS_TOKEN_KEY: Your Access Token Key
ACCESS_TOKEN_SECRET: Your Access Token Secret

[Stack Exchange OAuth]
KEY: Your Stack Exchange OAuth Key


Logging:

Status messages will be saved in a file named status.log in the same directory with bounty_bot.py.  The target window for bounty expiration, the status message posted to Twitter, and the bounty expiration time are all logged to this file.

Error messages will be saved in error.log.
You can’t perform that action at this time.