Changeling’s Guide to Mastodon for Screen Reader Users: Chapter Two. A Closer Look, Joining Instances, and signing up
What is This?
This is the second in a series of posts that explains how to use Mastodon if you use a screen reader. It is an alternative form of the already existing documentation for Mastodon, subject to my interpretation of concepts. Therefore, I suggest that you use this guide in conjunction with the official documentation, linked to later in this post. I also suggest that you go back and read Chapter One. Once you’ve done that, continue reading this chapter.
What is Covered in This Chapter?
This chapter takes a closer look at what Mastodon is, deals with the concept of instances, explains the differences between Mastodon and other platforms, offers suggestions on choosing an instance, and concludes with a brief description of the signup process. If you’ve already done these things, go on to Chapter Three.
Terms in This Chapter (in order of discussion)
- Federation, fedeverse
A Closer Look at Mastodon
You probably have an idea of what Mastodon is by now, or else why would you be reading this? Just to make sure I’m covering my bases, however, let’s take a closer look. Mastodon is a service that offers its users a microblog, a space to share short posts with no title, and the option to attach media such as pictures and videos. Other users can then interact with these posts in a number of ways, discussed in chapters and Five.
Doesn’t That Already Exist?
It sure does. These days, Twitter is synonymous with microblogging, because it’s the most popular. This is similar to how America Online (AOL) was once the most popular form of Internet access, but it was not the only service like that, and it certainly not the Internet. Just like forms of Internet access, email, and many other services, it is to be expected that different microblogging services would have some features in common. I’ll briefly discuss some of those now.
Common Features Between Twitter and Mastodon
- The primary form of communication is short statuses. On twitter, this limit is 280 characters, and 500 on Mastodon.
- The ability reply to, like/favorite, and repost posts. (More on this in chapter Five.)
- Being able to follow and be followed by other users. (More on this in Chapter Four).
- The ability to create custom timelines by creating and adding users to lists. (More on this in Chapter Six, coming soon).
- The ability to filter out unwanted content. (Also discussed in chapter Six.)
With So Many Similarities, Why Not Just Stay on Twitter?
Let me take this opportunity to tell you that I have no special reason for you to leave Twitter if you’re happy there. I mean, we’re in Chapter Two of this guide, clearly there is more to come, and if you’re still reading up to this point, it’s because you’ve already made the decision to at least consider having a presence on Mastodon. With that said, there are plenty of differences between the two services, but we need to take a look at a few concepts before we can discuss them. This is a lot like how when you got your first email address, you probably read the documentation of something like Gmail before you decided to switch providers, or at least that you needed a second email address.
The Argument I Refuse to Make
The most common argument I hear for using mastodon is something to the tune of everybody is so friendly on Mastodon. I’ve never had a bad experience on Mastodon, but the fact of the matter is Mastodon is a place for people, and people have the capacity to be hostile regardless of the platform. The most infamous example of this is the situation concerning Wil Wheaton from last summer, followed immediately by many users’ decision to block one Instance when they found out it was admined by someone who had done work for the FBI. In both cases, people had their own reasons for behaving the way they did, but it was still aggressive behavior. If you’re going to be online, if you’re going to interact with people, there’s a chance you may experience some form of hostility.
Don’t Let Me Scare You off
If you’ve come this far, don’t let me scare you off. If you choose your instance carefully, you can minimize the chance for hostile encounters. As you’ll see in the next section, it’s a lot like picking a neighborhood to live in.
Before you can find out what an instance is, you need to know how Mastodon works. With a service like Facebook or Twitter, you and I, the users, sign up for an account, managed by one central server, accessed when we open our browser and log on to something like twitter.com. To find a user, you put a slash after the web address, so if you wanted to find me on Twitter, you’d go to twitter.com/changelingmx. From there, you can click the follow button, and if I can verify that you aren’t a porn bot, won’t clog my timeline with Bible quotes, etc., I’ll probably follow you back, and we’re connected. We’re interacting within one ecosystem. This is just fine until the ecosystem dies (looking at you, Google+!), in which case we all die, digitally speaking.
As explained on joinmastodon.org, rather than being one website, the Mastodon network is a collection of websites powered by the mastodon software, which enables them to interact with each other. Each of these websites is called an instance.
You pick your instance the way you choose your email address. In fact, my Mastodon address looks like ChangelingRandy@mastodon.social. If you’re reading this on an iPhone and click that link, you’ll actually launch the device’s Mail client. If you want to find me once you join your chosen instance, click here, or see the H-Card widget in the sidebar of any starshipchangeling.net page, which has every link for every service i actively use. If you don’t want to see all of my Mastodon interactions, but want to follow this blog, you can follow it via Mastodon by typing “firstname.lastname@example.org”, minus the quotations. All of these websites together form the fedeverse, or, as Mastodon calls itself, a decentralized, federated social network. This detail becomes particularly important starting in Chapter Four. For now, what you need to take away is that instances can interact with each other, meaning that some on mastodon.cloud can follow me on mastodon.social. It’s also important to understand that instances can block each other, which happens from time to time since anybody can run a Mastodon instance, regardless of whether or not their opinion is a popular one.
How Do I choose My Instance?
To paraphrase a passage from Ernest Cline’s Armada, this is an objective, rather than a subjective task, so there is no right way to do it. It’s not uncommon for someone to join an instance, realize it’s not a good fit, and change instances. You may go through that process, and there’s nothing wrong with that. Here are some suggestions to guide you.
Choose Based on Interest
Anybody can run a Mastodon instance. This means if you can think of it, there’s probably a community for it. The “Getting Started” section of joinmastodon.org has a form you can fill out to get server suggestions. Parameters include everything from what language you speak, to your hobbies.
Choose Based on How You Feel About Rules
Since anybody can run a Mastodon instance, the code of conduct from instance to instance varies. Theoretically, I could start an instance that requires users to be able to quote every line from Disney’s “Aladdin” upon request. Realistically I’d be the only member of that instance. Seriously, though, pay close attention to the rules of the instance. Each instance has them. Here is the code of conduct for mastodon.social. Please believe me when I tell you that these rules are usually strictly enforced.
Considerations for Screen Reader Users
The following is a list of questions a screen reader user should consider before joining an instance.
- What version of the Mastodon software does the instance run? Newer versions often have accessibility improvements.
- Does the instance run beta versions of the mastodon software? If so, make your life easier by considering the following:
- Have a backup of your data in case you need to leave. (described in Chapter Six).
- Have a backup account on a stable instance. This will help you troubleshoot any problems you may have by enabling you to distinguish between caused by beta software and bug in a stable release.
- Do uploaded images appear as links you can click? This will make it easier to download images for further analysis by AI.
In Chapter Three, we’ll be looking at how to complete your profile, as well as send that first post. In the meantime, go ahead and pick your instance and join it, so you will be ready for the next installment.
Awesome, thanks lots, will bookmark these.
Those will update when future chapters are published, and both of those have links to each other. I’m looking at 6 or 7 chapters, but most people will have what they need by chapter 4.