Posting text and images to Mastodon

Tutorial – Mastodon

Article from Issue 231/2020

Creating a custom application that toots text to Mastodon (the Fediverse's version of Twitter) is simple and straightforward. But we can mix it up by adding images and video, scheduling posts, and changing privacy settings.

If you haven't read the prior article in this series [1], you may want to do that now. There, you will learn how to read from a Mastodon feed and print out the toots (the name Mastodon gives its posts) onto the command line. You can do that quite easily with Python, because the API for Mastodon is open and well documented, and also because there is a comprehensive Python wrapper [2] that makes building ad hoc clients a breeze.

In this article, we're going a step further, and you will see how to create an app that posts your toots. Before you start, and just in case you haven't already, install the module with

pip install

and let's get started.


As with your reading application, the first thing you have to do is register your application with Mastodon (Listing 1).

Listing 1

01 #!/usr/bin/env python
03 from mastodon import Mastodon
05 Mastodon.create_app(
06      'posttoots',
07      api_base_url = 'https://your.mastodon.server',
08      scopes=['read', 'write'],
09      to_file = '.secrets'
10 )
12 mastodon = Mastodon (
13     client_id = '.secrets',
14 )
16 print ('Mastodon version: ' + mastodon.retrieve_mastodon_version())

You only have to run this once. It registers the posttoots application (line 6) with https://your.mastodon.server (line 7 – insert the server hosting your account here), sets its scope to 'read' and 'write' so you can both post to an account and also read information off the server (line 8), and grabs some credentials and stores them in a hidden file called .secrets (line 9).

Although it does not affect the registration, you can tack on lines 12 through 16. Lines 12, 13, and 14 check to see if the app can be activated using the downloaded credentials in .secrets and line 16 tells you what version of Mastodon your server is using. This can be useful if your program relies on features available on the very latest Mastodon, but your server has not updated yet.

You only need to run once as you can use the credentials stored in .secrets over and over. .secrets (Listing 2) contains a client_id (line 1) and a client_secret (line 2) that you will be able to use to identify your application each time it has to interact with the Mastodon instance. On line 3 you also have the address of the instance the app is registered with, which is convenient as you will see later on.

Listing 2


01 53eM1n9lyHR4nd0mUnUMB3r5vAN6G133TeR5X4g
02 KM0r340FdTh3p54M3A60nTnUkKN0WC0hweMigLcng6U
03 https://your.mastodon.server

So, posting is very straightforward. Consider Listing 3.

Listing 3 (Basic)

01 #!/usr/bin/env python
03 import sys
04 from mastodon import Mastodon
06 mastodon = Mastodon (
07     client_id = '.secrets',
08 )
10 mastodon.access_token = mastodon.log_in (
11     username = sys.argv[1],
12     password = sys.argv[2],
13     scopes = ['read', 'write']
14 )
16 mastodon.status_post (sys.argv[3])

After pulling in sys (to process the command-line arguments – line 3) and Mastodon (for everything else – line 4), you activate your app with the Mastodon server (lines 6 through 8). You could insert here the client_id, client_secret, and the host, but we have all that in the .secrets file, remember? So all you have to do is point to that (line 7).

Then you need to log in with your username and password so the application posts to a specific account (lines 10 through 14). Pass your username and password to the application and the value of scopes. I am not sure why you have to add the latter, but if you don't, the login fails. The value of scopes must be the same as what you used when registering your application in Listing 1. Finally, on line 16, you post a message using's status_post() function.

You can use like this:

./ "Your awesome password" "Tooting from the command line with my own app!"

And "Tooting from the command line with my own app!" will pop up in your feed (Figure 1).

Figure 1: Tooting plain text to your account requires a simple Python program.

That's it. The end. See you next issue…

Beyond Simple

Well, not really, because there is so much more you can do when posting. You can, for example, append an image or a video, schedule your toots so they are posted automatically at a later date (easier said than done), set the visibility of each toot, and quite a bit more. To see how all of the above is achieved, consider Listing 4.

Listing 4 (Advanced)

01 #!/usr/bin/env python
03 import datetime
04 import cv2
05 from optparse import OptionParser
06 from mastodon import Mastodon
08 class post:
09     def __init__ (self, vUser, vPassword):
10         f_read = open(".secrets", "r")
11         instance = f_read.readlines()[-1].strip(" \n")
12         f_read.close()
14         self.mastodon = Mastodon(
15             client_id = '.secrets',
16             api_base_url = instance
17         )
19         self.mastodon.access_token = self.mastodon.log_in(
20             username = vUser,
21             password = vPassword,
22             scopes = ['read', 'write'],
23             to_file = '.token'
24         )
26         self.post_date = None
28     def send (self, vToot, vMedia, vVis):
29         self.mastodon.status_post(vToot, media_ids = vMedia, scheduled_at = self.post_date, visibility = vVis)
31     def add_Media (self, vMedia):
32         return (self.mastodon.media_post (vMedia))
34     def set_date (self, vDate):
35         try:
36             self.post_date = datetime.datetime.strptime(vDate, '%b %d %Y %H:%M %Z')
37         except:
38             self.post_date = None
40     def show_scheduled (self):
41         print (self.mastodon.scheduled_statuses())
43 if __name__ == '__main__':
44     parser = OptionParser()
45     parser.add_option ('-a', '--action',    help = '"post", "schedule" or "list"',  dest = 'vAction',   default = 'list')
46     parser.add_option ('-u', '--username',  help = 'user\'s email',     dest = 'vUser')
47     parser.add_option ('-p', '--password',  help = 'user\'s password',  dest = 'vPassword')
48     parser.add_option ('-t', '--toot',      help = 'toot text',         dest = 'vToot')
49     parser.add_option ('-m', '--media',     help = 'media ("cam" or image, video, etc.)', dest = 'vMedia', default = None)
50     parser.add_option ('-w', '--when',      help = 'when to publish toot. Format: "mmm dd YYYY HH:MM Z"', dest = 'vWhen', default = None)
51     parser.add_option ('-v', '--visibility',help = '"public", "unlisted", "private" or "direct"', dest = 'vVis', default = 'public')
53     (options, args) = parser.parse_args()
55     p=post(options.vUser, options.vPassword)
57     mmedia = options.vMedia
58     if mmedia != None:
59         if mmedia == "cam":
60             camera=cv2.VideoCapture(0)
61             return_value, image
62             cv2.imwrite("pic.png", image)
63             del(camera)
64             mmedia="pic.png"
66         mmedia = p.add_Media(mmedia)
68     if options.vAction == 'post':
69         p.send (options.vToot, mmedia, options.vVis)
71     elif options.vAction == 'schedule':
72         p.set_date (options.vWhen)
73         p.send (options.vToot, mmedia, options.vVis)
75     else:
76         p.show_scheduled()

You can divide the program into 5 distinct sections:

  1. Line 1 sets the interpreter for the program.
  2. Lines 3 through 6 pull in the modules you'll need. The datetime module lets you convert strings to dates. You will need this when you want to parse dates passed on by the user to schedule toots. The cv2 module is the Python implementation of OpenCV [3], the library that will allow you to capture an image from your webcam. As you need to parse quite a few parameters to make life easier for the user, let's use optparse too. Finally, we import the mastodon module.
  3. Lines 8 through 41 is the class that does all the dirty work of activating the app, posting, and scheduling.
  4. Lines 44 through 53 collect and allocate all the options the user inputs from the command line.
  5. Finally, lines 55 through 76 call the functions we need depending on the input from the user.

To go into detail, let's see how we can post an image within a toot.

Posting Pictures

One nice feature that comes bundled with optparse is how it provides help for the user. Run this:

./ -h

And you'll get a summary of the possible options and hints as to how to use them.

To start with, -h tells you to input your username (the email associated with your Mastodon account) with the -u option and your password with the -p option.

The -a option tells your app what you want to do. You can choose between post (send a toot), schedule (schedule a toot for later), or list (list all the scheduled toots). As you want to send a toot with an image, use post here.

The -t option contains the text for the toot, and -m contains the path and name of the media (picture) you want to send. Given all of the above, your complete command line will look like this:

./ -u -p "Your awesome password" -a post -t "Tooting an image from the command line with my own app!" -m /path/to/image.png

Looking at Listing 4, once you hit Enter, the pairs of options and values from the command-line arguments get dumped into (options, args) (line 53), and the Mastodon object is initiated with your username and password (line 55). The initialization function (lines 9 to 26), takes the URL of the Mastodon instance, client_id and client_secret from the .secrets file (lines 10 to 17), logs the application in (lines 19 to 24), and sets the post_date attribute to None (line 26).

You will have noticed that the program gets the URL of the Mastodon instance in a very roundabout way. Instead of just loading all the values in from .secrets, including the URL, into client_id, we do this convoluted thing of opening the .secrets file (line 10), dumping the contents of the last line into instance (line 11), and then closing the file (line 12).

The reason for this is that there seems to be a bug in that appears when you try to use scheduling: If you rely on a file to load in your instance's URL, anything to do with scheduling will fail with an error complaining about the version of Mastodon running on the server, or some such nonsense. The workaround is setting the URL explicitly on line 16.

This is not the only problem with scheduling as we will see later, but let's get back down into the main body of the program where, on line 58, you check to see if the user has given a path and filename of a media file. If they have, you add the media file to the toot object (line 66 and then lines 31 and 32).

Finally the toot, along with the media, is sent on line 69 by calling the actual Mastodon sending function on lines 28 and 29 (Figure 2).

Figure 2: You can also send images and videos to your feed relatively easily.

You can add up to four images to a toot, as well as videos and other kinds of files.

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy Linux Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • toot

    If you are looking for a Twitter alternative, toot lets you interact with Mastodon from the command line.

  • Mastodon Clients Post Line

    The open and simple Mastodon API makes it easy to create applications to interact with this federated microblogging platform. Here are some of the clients that the community has come up with and how you can use them.

  • Mastodon

    Get started with free microblogging, interact with others who share you interests, and even help expand the Fediverse with your own Mastodon instance.

  • Status Quo

    Creating your own clients to interact with your friends in the Fediverse is easy. A bit of Python and an off-the-shelf module will do the trick.

  • Tutorial – Fediverse

    If you're looking for social media options where the user has more control, you'll find a range of options to explore in the Fediverse, including the popular Mastodon.

comments powered by Disqus
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters

Support Our Work

Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

Learn More