Corbindavenport Tootbot Versions Save

I'm no longer developing Tootbot. The current version (v2.6) will be the last release from me, and I've disabled the ability to create and comment on issues. Besides some buggy behaviour with Gfycat/Imgur links, Tootbot is still functional, but I can't guarantee it won't break in the future.

If you want to take over the project, send me an email.

What's new

• Fixed bug where failed Gfycat API response would crash Tootbot.

Known issues

• Gfycat links can't always be downloaded, due to the official Gfycat library for Python being abandoned. This affects all previous version of Tootbot as well. (#85)

Update instructions (local install)

No special steps are required when updating from Tootbot 2.5 to Tootbot 2.6. Just replace tootbot.py and getmedia.py in your Tootbot folder with the latest versions.

Update instructions (Heroku)

See the wiki for help updating an existing Heroku installation.

IMPORTANT: If you currently operate a Twitter bot, you have to apply for a Developer account or you will eventually lose API access. It's free and doesn't take much time. Full instructions are here.

What's new

• The Heroku version of Tootbot can now optionally post to Mastodon. Instructions for connecting a Mastodon account are on the wiki. (#60)
• The "The access token is invalid" error when logging into Mastodon has been fixed. (#79)
• Some console messages have been rewritten to be more clear.
• Tootbot will no longer re-attempt to download media that previously failed to download.

Known issues

• Gfycat links can't always be downloaded, due to the official Gfycat library for Python being abandoned. This affects all previous version of Tootbot as well. (#85)

Update instructions (local install)

This version requires an updated version of the Mastodon.py library. Open the command line/terminal and set your directory to the Tootbot folder, then run this command:

pip3 install -r requirements.txt

If you get an error, try using pip instead of pip3.

The last step is to replace tootbot.py and getmedia.py in your Tootbot folder with the latest versions.

Update instructions (Heroku)

See the wiki for help updating an existing Heroku installation.

IMPORTANT: If you currently operate a Twitter bot, you have to apply for a Developer account or you will eventually lose API access. It's free and doesn't take much time. Full instructions are here.

What's New

• Tootbot now uploads full-quality MP4 versions of GIFs when posting to Mastodon. This feature currently works with links from Imgur, Gfycat, and Giphy. (#3)
• Reddit video links (v.redd.it) are now supported by Tootbot, but only when posting to Mastodon. (#74) Video upload support for Twitter may be possible at some point in the future, see #75.
• The codebase has been significantly reworked, with a focus on making the code easier to understand.
• Console messages have been improved.

Update instructions (local install)

No special steps are required when updating from Tootbot 2.1-2.3. Just replace tootbot.py and getmedia.py with the latest versions.

Update instructions (Heroku)

See the wiki for help updating an existing Heroku installation. Since the Heroku version of Tootbot currently only supports Twitter, and there are no major improvements for posting to Twitter in this release, there's not a major reason to upgrade existing Heroku bots at this time.

What's New

• Tootbot can now run in the cloud using Heroku! See the blog post for more information. If you're already running Tootbot in the cloud, this release fixes the reposting bug. (#52)
• Sticky posts are now ignored. (#61)

Update instructions (local install)

No special steps are required when updating from Tootbot 2.2. Just replace tootbot.py and getmedia.py with the latest versions.

Update instructions (Heroku)

See the wiki for help updating an existing Heroku installation.

What's New

• Media embedding now works with most direct image links (previously only images/GIFs hosted on Gfycat, Imgur, Reddit, and Giphy were allowed)
• Added PIP requirements file for easy dependency installation
• Added more error handling
• Started work on Heroku support (not functional yet)

Update instructions

No special steps are required when updating from Tootbot 2.1. Just replace tootbot.py and getmedia.py with the latest versions.

What's New

• Added Hashtags option in [BotSettings], where you can set multiple hashtags to be used on every post
• Added SpoilersAllowed options in [BotSettings], which allows or blocks Reddit posts marked as spoilers (default is true)
• Added SensitiveMedia option in [Mastodon], which marks all media attachments on Mastodon as sensitive material (default is true)

Update instructions

If you are updating from Tootbot v2.0, there are a few minor tasks you must do, or else the updated version will fail:

1. Add SpoilersAllowed: true to the [BotSettings] section of the config.ini file.
2. Add Hashtags: (you can leave the value blank) to the [BotSettings] section of the config.ini file.
3. Add SensitiveMedia: true to the [Mastodon] section of the config.ini file.

What's New

• API keys for Twitter, Imgur, and Reddit are now stored in .secret files
• Added PostToTwitter setting to disable or enable Twitter posting
• Fixed bug where posting to Mastodon would fail
• Fixed bug where Tootbot would post "This content is not available" on some Giphy links (#8)
• Renamed DelayBetweenTweets setting to DelayBetweenPosts
• Added comments in config.ini that explain each setting

Update instructions

If you are updating from Tootbot v1.0, there are a few minor tasks you must do, or else the updated version will fail:

1. Add PostToTwitter: true to the [Twitter] section of the config.ini file. If your bot does not post to Twitter, set it to false.
2. Find the DelayBetweenTweets setting in config.ini, and rename it to DelayBetweenPosts.

Tootbot v2.0 stores API keys in separate files, instead of in the config.ini file. When running the updated version for the first time, you will be asked for all your API keys again. This will only happen once, and you can just paste the API keys from your config.ini file.

• Initial release