My first month on Mastodon

I signed up for Mastodon a month ago. Ok, fine. I month minus two days. It’s been long enough that I’m relying on it now and check it more often than Twitter. This blog shows up my impressions and learnings.

I signed up for three accounts.

Overall

I’m happy with Mastodon overall. With two caveats

  1. A social network is only useful if the people you want to interact with are on there. A good percentage of the people I follow are now on Mastodon (or both Mastodon and Twitter).
  2. It took a while to get settled. Granted Twitter had a learning curve too. But it was a long time ago. (My first post was in 2009). Some of it is forgetting. Apparently, I used to use the TwitterFox browser extension. And some of it is because the unofficial apps are better than the “official app”

Signing up for Mastodon

Signing up for Mastodon isn’t particularly user friendly. First you have to pick a server. Before you know much about the service.

A server is kinda like an email provider. You get a different domain name @gmail.com, @yahoo.com, etc. You can still talk to people on other servers, just like email. But that’s where the comparison ends. You don’t get a different user interface or special email user features. So what is different by server

  1. People can learn something about you from just looking at your name. For example, fosstodon supports free and open source software.
  2. Mastodon has a local timeline to see things other people on the server posted (regardless of whether you follow them).
  3. Different servers have different moderation rules. For example, I wanted one that was ok with non-human accounts for NYJavaSIG and CodeRanch.
  4. Servers are volunteer run and can close up shop. If that happens, you have to move.
  5. Servers can be banned by other servers. (ex: one with terrible moderation)

For my personal account, I chose mastodon.social because it was one of the two main ones and I didn’t know what I was doing. I later learned that people are encouraged to do choose different ones to spread the load. I chose to not to move at this time partially because it is cool to see the big timeline while I’m getting my bearings and partially because new servers keep getting stood up and switching after things stabilize reduces hops.

For NYJavaSig, I was interested in hackyderm.io and fosstodon.org because they are tech in nature. Fosstodon seemed more open to non human accounts. For NYJavaSig, I was able to register immediately. By the time, I got to doing registring for CodeRanch, you had to fill out a form saying why you wanted an account and have someone approve it. That took about a day.

Speaking of switching, you keep your followers/followings. Your toots (like posts) don’t move as far I can tell. That’s not important to me though.

Ultimately, it isn’t that important which server you choose. It is the accounts you follow that matter. Which brings us to….

Finding people to follow

I started out finding people on twitter who posted that they moved to Mastodon. Then I followed people I saw via boosts (like retweets)

After that, I learned that Marc Hoffman created JavaBubble for the Twitter/Mastodon/GitHub handles of Java folks. Non human entities are allowed like the NYJavaSig. He has good quality control. My contribution of CodeRanch to the list got rejected because almost our all tweets are about our free book promos. (Which is fair. We should post more outside of the promo).

I didn’t import the whole list for my personal account because I want my feed to be mostly English. I did add a bunch of people from it though. And it serves as a great lookup table. I did import the whole list for CodeRanch so I can look at the feed from there if I want.

There’s also websites, described by this blog post to help automate finding folks you follow.

Buttons when tooting (posting)

There’s a few interesting buttons when creating a toot.

  • World icon – you can control the access of your posts to public, unlisted (anyone with a link), followers only and visible to only people mentioned. The later being a direct message. More on that in a minute
  • Content warning – Mastodon encourages a content warning for certain topics. Even neutral ones. Like “politics neutral”. The idea is to give people a clue what is inside and let them click if they want to see it. I like this idea. Also could be useful for tv/movie/book spoilers :).

Mac Apps

There’s no official Mac app. The browser approach isn’t bad. I like the notifications view shows you how many there are. However, I have three accounts. Two of which are on the same server. An app would let me have a better experience across the three.

First I tried Mastonaut. Switching between accounts wasn’t bad. You can have multiple columns for different timelines (home/local/federated). I didn’t like that because it auto refreshes. And the local/federated timelines are busy places. The big problem with this app is that it didn’t let me add two sites from fosstodon. So I have my personal account and two of nyjavasig. Between this two problems, I kept researching.

Next I tried Whalebird, which I like. It’s a lot like slack. You have to choose which account you want at a given moment, but it is one click. And like Slack so feels familiar. Like Slack, it has channels, you get choices of: home, notification, mention, direct messages, favourite, bookmark, local timeline (your server), public timeline (local + all accounts someone on your server follows), and search.

Remember I was going back to DMs. The apps to a good job separating them out. So even though they are “just posts”, they feel like a native concept. I’m happy with Whalebird and sticking with it. At least for now.

iOS apps

There is an official app for Mastodon for iOS.It only supports one account so not very useful to me. I then read this comparison of 8 apps. I decided to try Toot! I paid the $4 and learned that I didn’t like it. First, the sign up isn’t intuitive. You sign up as anonymous to the server and login. Ok fine, setup is one time. However, the app doesn’t show how many comments there are on a toot. I really wanted that feature so I tried Metatext.

I’m happy with Metatext so far. It is open source with the code on GitHub. It’s basically maintained by one guy. But it’s free. So I can always switch in the future if another one becomes better for my needs.

To switch between users, you hold the user icon in the top left to get the other choices. There are home/local/federated timelines on top. And search/notifications/messages on the bottom.

Verification Links

In your profile, you can enter up to four links. They give you a URL to include that includes rel=”me”. Resave your profile after adding the link to your page to show you control it and the links show up as green/verified.

You can definitely change the body of the link to something other than “Mastodon.” And I think the link it is a one time check. I deleted one of them a while ago and it is still there. For github, there is a hack to get the verification link to work.

Cross posting

I used this crossposter to have my posts automatically go from Mastodon to Twitter. (It might be closing to new users due toa 300 posts/hour across all users limitation. Details and updates here.

Paying

Mastodon is free. However, the servers are paid for with donations as this is not a for profit endeavor and there are no ads. I signed up for the $10 a month Mastodon plan (which includes mastodon.social) and $5 a month Fosstodon plan.

Both also have $8/month plans now that Twitter has set $8 as the appropriate price for social media. Mastodon’s is called “8 dollars count too” with a description of “People have asked for this tier”. Fosstodon’s is called “Elon Tier” with a description of “Forget Twitter blue and stick it to Elon by supporting Fosstodon instead/”

What don’t I like (or haven’t figured out yet)

With just under a month of experience, I don’t know yet if these are dislikes or not having found a better way yet.

  • I haven’t found a mobile app that notifies me about direct messages
  • I get a number of posts in other languages. There’s a bug on github so this one isn’t just me.

How I recommend studying for the Terraform Associate exam

Related pages:

First of all, the exam is $70 and change. This means there is no need to spend much (or any) money studying or to overstudy. You can always take it again without laying out a lot of money if needed.

There are a number of ways to study depending on your preferences and what you have access to. Regardless of what you choose, read the official exam page so you know what to expect.

Option 1: Resources from HashiCorp

HashiCorp has web pages references that they say are useful for the exam.

All three are fine for learning. Just be aware they have a lot of info you don’t need to know. I recommend using another resource for review the day before even if you use this initial.

Option 2: If you have access to ACloudGuru

There is an ACloudGuru course online. It is about 8 hours of content including labs/quizzes. I didn’t try it because i was studying mainly offline. However, I did use them for the AWS cert. The material was good/consistent enough that I feel comfortable recommending site unseen. There’s a free one month trial if you aren’t a customer.

Option 3: Whizlabs/IPSpecialists

There are 25 questions online for free. This is a subset of what is in the book. The quality/lack of consistency is representative of the book. You can see if that bothers you before spending any money.

Option 4: Medium blog post

The title of this medium post says this is 250 practice questions. It is in the sense that there are question marks. Not in the sense of practice questions. What it does do well is serve as an awesome review of what you need to know for the exam.

Option 5: My study notes

Like option 4, this is a good way to review.

How I studied for the Terraform Associate Exam

Related pages:

I passed with a score of 75%. (70% is passing.) I didn’t review all my answers because I was starting to feel dizzy. I might have gotten one or two questions right had I finished review. But passing is passing, so I’ll call it a win.

Also see my experience taking the exam online.

My overall exam impressions

Putting aside the discomfort with taking the exam from home, I think it is a good exam. There’s a lot of testing of concepts/understanding and not a lot of memorization. For example, there was no need to memorize the command line options for each command; something I wasted time on. There were a number of questions about the best way to do something in a scenario. Most of the questions were pick one of four. A few were pick 2 or 3. Some were true/false. And two were typing in the answer. Both were things that one could reasonably be expected to know.

Studying for this exam definitely got me to understand Terraform and I have confidence next time I write/edit/review scripts, I’ll know what I’m doing. Another nice thing about cert exams is questions that I’m unsure of (and I can remember) I look up the answer to and remember for a long time. I still remember something I got wrong on the Jenkins exam and I took that 6 years ago! I do know what I got wrong on 2.0 and 7.0 so that was effective.

Status: Pass 

Overall Score: 75% 

Breakdown by content area: 

1.0  Understand infrastructure as code (IaC) concepts: 100%
2.0  Understand Terraform’s purpose (vs other IaC): 50%
3.0  Understand Terraform basics: 71%
4.0  Use the Terraform CLI (outside of core workflow): 66%
5.0  Interact with Terraform modules: 83%
6.0  Navigate Terraform workflow: 83%
7.0  Implement and maintain state: 50%
8.0  Read, generate, and modify configuration: 81%
9.0  Understand Terraform Cloud and Enterprise capabilities: 100%

My score report

My experience with Terraform before starting studying

I reviewed a Terraform script for one of our systems and “paired” with a teammate on parts of another one. Both of them happened during the “mandatory full time work from home” for over a year experience. My brain wasn’t in great shape for a lot of that period so it didn’t click. My goal of taking this cert was to understand the principles and re-learn everything.

Offline studying

My ideal was to do as much of the studying as I could offline on the subway on a plane. (I had two round trip flights in the last two months.) This meant books were ideal.I had read Terraform in Action earlier in the year so re-read the relevant parts.

IPSpecialist has two $10 books – the study guide and 150 extra practice questions. Both were listed as 2022 (which is important because the exam changed recently.) The books had a ton of errors and looked like they were written by committee. But they were cheap and let me study a lot offline so I’ll call them worth it. (I also hadn’t realized IPSpecialist and Whizlabs were the same company.)

Online studying

I did the 6 official practice questions. (got 5/6 day of the exam, but that was the second time I’d seen the questions). I also skimmed the official review docs the day of the exam.

Running Terraform

Other than watching my teammate run Terraform, I have no hands on experience. (That will change soon.) I took the exam without ever directly running Terraform.