Twitter is suited for short statements and back-and-forth conversation.

It’s terrible for anything long-form.

Long Twitter threads* and images filled with text remind me of the old tech support days when users would paste screen shots of error messages into Microsoft Word documents and email me the document. It was a terrible tool for the job, but it was the one they knew.

Once you get past two or three tweets (doesn’t matter whether they’re 140 characters or 280, it’s the structure that matters), your ideas will hang together better and be better understood if you write an actual article somewhere. Sadly, Twitter has trained people to stay in Twitter instead of going outside to read the %#$ article**, because you won’t be able to get back to where you were in your timeline, and besides, that’s just too long to read right now.

And that would require you to have, like a blog or something, and what sort of weirdo has one of those? 🙄

So people use what they know, and we get screenshots of long paragraphs that are awful for accessibility. And we get 40-tweet threads that people only see fragments of and take bits out of context. And they’ll reply to tweet #5 complaining about something that’s addressed in tweet #12, but they didn’t see it, because that was hidden behind the “read more” link, and how long does this thread go, anyway? (Scroll bars solved this problem decades ago.) And we get links to articles that people don’t read, but they reply to them anyway — or rather they reply to what they assume was in them.

Which I suppose is what we had in the old days, I mean “nobody reads the articles” was a joke on Slashdot 20 years ago. But it’s still frustrating.

Update: I realized I don’t see this so much on Mastodon. I wonder if that’s one of the ways the culture is different, or if I just happen to not be following anyone who writes/boosts long threads on a regular basis, or if 500-character posts give people enough room to breathe that they don’t feel like they’re already writing a long chain, so why worry about keeping the number of posts down, what’s the difference between 10 tweets and 15?

Update March 2024: Apparently it was a posting culture thing, because it’s common on the Fediverse now too. At least on platforms like Mastodon that maintain a smallish size limit.

*To clarify, I’m talking about long threads that are effectively one piece of writing, not a series of “oh, and another thing” follow-ups, live-tweeting as things come up, actual conversations, etc.

**This part is true of Facebook as well.

Update March 2023: If you want to cross-post from something supported by, I recommend using that service since it’s a lot simpler to set up. But if you want to pull from an RSS/Atom feed, or anything else that doesn’t support, or customize features like post visibility, this will let you connect just about anything.

*****IMPORTANT UPDATE NOVEMBER 29, 2022: I gave the wrong directions on what to put in the Application Website field in Mastodon. It just needs to be It isn’t used for identifying the source to your Mastodon server as I thought it was, but appears as a link when the post is viewed by itself on the web. If you followed on my mistake, I highly recommend (1) removing the URL from your Mastodon config and just putting in and (2) going into your Webhooks settings at IFTTT and generating a new key. I feel horrible that I messed this up, and I am so sorry to everyone I steered wrong.

I finally managed to hook up IFTTT to Mastodon to auto-post from another site! I use IFTTT as glue for linking several services together including sharing interesting links from Pocket when I’m offline: I can add a tag in the app on my tablet, and then when it syncs that tag up to the cloud, IFTTT will pick it up and create the share post on whichever service I’ve tagged it for.* I also use it to post from RSS and WordPress to publish new blog posts to services that aren’t available in Jetpack.

My main source was this post by It’s a bit out of date, but it pointed me in the right direction.

Note: I’ve updated this article several times (most recently November 2022, when I finally added screenshots and some troubleshooting tips) to add more information, clarify some issues, respond to changes in IFTTT’s layout, and make additional suggestions.

Before we go any further, if you’re hooking up something that’s totally automatic, rather than something triggered by your own actions on another site — especially if you don’t plan on posting to the same account manually — I’d recommend looking for a bot-friendly Mastodon instance like BotsIn.Space. That’s where I set up @SpeedForce@BotsIn.Space to post every time there’s a new blog entry on Speed Force.

1. Set up IFTTT’s Webhooks

On IFTTT, go to Webhooks. Activate it by clicking on the Connect button. Update 2024: As Alan points out in the comments, webhooks is now only available with an IFTTT Pro plan.

2. Set up Mastodon to allow IFTTT as an application

Go to Preferences/Development/Your Applications on your Mastodon instance (ex: on it’s here). Click on New Application. Enter the following:


UPDATE November 2022: When I first posted this article, I thought you only needed to match the source of the API calls. In April/June 2022, I updated the article under the mistaken impression that Mastodon now needed the full URL generated by the IFTTT webhook service, like IFTTT needs the API key from Mastodon. This was wrong. I didn’t test it properly, and didn’t notice that this field isn’t for authentication, it’s exposed in a link when a post is viewed by itself on the web. If you followed on my mistake, I highly recommend (1) removing the URL from your Mastodon config and just putting in and (2) going into your Webhooks settings at IFTTT and generating a new key.

Thank you so much to @h3rb1 for pointing out my mistake.

Scopes: write:statuses

Screenshot of the write:statuses box checked.

Submit the app.

Now open the new app you’ve created and look up the access token for the next step.

Screenshot of Mastodon app settings including Client key, Client secret and Your access token. You want the last one.

3. Create an IFTTT app!

Go back to IFTTT and create a new app. For example, I created an app triggered by Pocket, whenever an item is tagged share-mastodon. You could also set it up to autopost every time you blog with a specific tag, or every new item in an RSS feed, or all kinds of things. Even cross-post from Facebook or “the birdsite” (Twitter).

Since IFTTT has rearranged their site to make it easier to use pre-built recipes — sorry, apps — here are the steps to get to the point where you can build your own.

  1. Click on the “Get More” button at the top of the IFTTT page.
  2. The first bar should say “Make more Applets from scratch.” Click on the “IfThisThenThat” button in that bar.
  3. Click on “This” in “If +This Then That”
  4. Search for the type of service you want to hook up — RSS for a feed, or Pocket, or Facebook, etc. and choose the type of event you want to use (ex. “New feed item” or “New item tagged…”)
  5. Enter the info needed for the event — your feed URL, the tags you’re looking for, etc, and click on “Create Trigger.”
  6. Click on “That” in “If [rss] Then +That”
  7. Search for Webhooks and click on it.
  8. Choose “Make a Web Request”

And now you’re ready to configure how IFTTT will actually talk to your Mastodon app. Enter the following settings:

URL: (replace with your server)



Content Type:


Additional Headers: (replace 1234567890 with the access token you got from Mastodon, and make sure there’s only a space between “Bearer” and the token.)**

Authorization: Bearer 1234567890


status=Whatever you want to post

Screenshot of IFTTT webhook action, repeating the text above.

Screenshot of the message body, repeating the text examples below.

For example, to share a link from Pocket you might want the body to be

status=<<<{{Title}}>>> <<<{{Url}}>>>

Or for posting from WordPress, you might want it to be

status=New blog post: <<<{{PostTitle}}>>>

Or from an RSS feed, you could use

status=New post: <<<{{EntryTitle}}>>>

The “ingredients” available (Title/PostTitle/etc.) will depend on the source you’re using, and you can get them from the IFTTT user interface. RSS feeds will have EntryTitle, EntryUrl, etc., WordPress will have PostTitle and PostUrl, and so on. You can click on the “Add ingredient” button to see what’s available.

Watch out for ampersands and single quotes, because the API handler treats them as separators. Even if they’re in the source material! When I first set this up, I ran into problems where single quotes in the original post would cause the Mastodon post to break. Wrapping the ingredient like this <<<{{Title}}>>> will prevent that.

Be sure to include the status= at the beginning! You can also add optional parameters for the Statuses method of the Mastodon API to add spoiler text, mark it as sensitive content, change the visibility (public, followers-only, etc), and so on.

To post an excerpt in a CW that doesn’t show up in local/federated timelines or hashtag searches, you would do something like this:

spoiler_text=Link: <<<{{Title}}>>>&visibility=unlisted&status=<<<{{Url}}>>> <<<{{Excerpt}}>>>

Or you could auto-generate a private draft, which you can go back to manually and fine-tune using Mastodon’s “Delete and re-draft” feature.

visibility=direct&status=<<<{{Title}}>>> "<<<{{Excerpt}}>>>" <<<{{Url}}>>>

Unfortunately, this method can’t post images because uploading images to Mastodon is a two-step process***. You can use something like (Twitter, Instagram, Tumblr, Flickr and more) or (Twitter/Mastodon). And if you want to go full Rube Goldberg, you can hook up a chain like Instagram→ IFTTT→ Twitter→ Moa→ Mastodon.

Click on “Create action.”

Add a title and click on “Finish.”

4. Test it out!

Go and post something that should trigger the rule, then come back and click “Check Now” on the IFTTT applet. Make sure it comes through the way you want it to. Adjust it as needed, using “Check Now” to verify each change, until it’s working the way you want it.

If you get a 422 Error in the IFTTT logs, that means something in the message body is wrong. Make sure you

  • Included status=
  • Didn’t post something too long for your instance. (Usually 500 characters)
  • Used <<<>>> around any ingredients that might have apostrophes, or ampersands, etc. in them.

If you get a 401 Error in the IFTTT logs, it’s probably an authorization issue. Check that

  • Your IFTTT app has the right access token
  • There’s only a space and not an actual line break or a double-space between “Bearer” and your token. IFTTT’s narrow layout makes this hard to see because it always wraps, and if you copy the entire line from Mastodon, it’ll sometimes introduce an extra space at the beginning.
  • Your Mastodon app config allows write:statuses

Once you’re done, let it go! Over time, IFTTT will adjust its checking frequency based on how often you post to the source feed. I’ve got some that it usually catches within 10 minutes, and others that it takes a few hours.

You can follow me on Mastodon at If you’re not on Mastodon, but would like to check it out, start at It’s a quick overview of what Mastodon is, how it’s different from Twitter, how different instances work (think of them as different servers on an MMO game, or different email services), and how to pick an instance that suits you.

*The day after testing the Pocket-to-Mastodon connection with a few links, I discovered something interesting about IFTTT when it re-posted one of those links to Buffer. Apparently IFTTT doesn’t know which tags are new, only which bookmarks have been updated and what the current tags are. My new Pocket-to-Mastodon applet picked up the share-mastodon tag I’d just added, and my Pocket-to-Buffer applet picked up the old share-buffer tag that had been on there since I first shared it last month.

**Previously the authorization token would be appended to the URL, like this:
My recipes using that method still work, but maybe that’s because the tokens are older. (Thanks for the update, Sven!)

***The Mastodon API needs the image to be uploaded first. It sends back the image’s ID, and then you attach that ID when you make the post. Multi-action IFTTT apps aren’t really chains – every action has the same set of ingredients from the trigger, and you can’t add the result from one action to the input on another.

I don’t like Twitter threads.

In most cases, if something takes more space than one or two tweets to say, it’s easier to read as an article. It’s especially bad with very long threads, and those that aren’t crafted to make each tweet a unit. When sentences continue on from one tweet to the next as if they’re only line breaks, it makes it hard to pick out a statement to highlight, or where to start.

On the plus side: Tweets are more likely to be seen, more easily shared, and people can interact as they’re posted, like a live conversation. A thread that’s crafted to fit in 140-character chunks has a rhythm to it, like a daily comic strip collection vs. a comic book. And an unplanned tweetstorm gives both the writer a chance to get their ideas down quickly and the reader a chance to see them unfiltered.

Compared to an article, a tweetstorm provides immediacy, and any Twitter thread provides reach. But they’re still a pain to read.

Originally written (of course) as a Twitter thread.

This blog has been around 15 years. Social media has mostly moved on, to silos like Facebook and Twitter. People don’t follow random personal blogs. Topic-focused sites are what people actually read, and even that mainly following links from silos.

Meanwhile there are so many major things going on that make the things I post about here — comics, fandom, photos of things I found interesting, random tech thoughts — seem trivial.

So why keep a blog going? And why write about trivialities, and not big things like the battles over civil rights, healthcare, environmental protections, war?

As for the first: Some of it is stubbornness. And some of it is wanting to keep part of my writing/photo presence somewhere “permanent” (to the extent that anything online is).

As for the second: I’ve never really liked talking news and politics online. I rarely feel like I can add anything that hasn’t already been said (probably better) by someone else. Also, online conversation has gotten way too toxic. On the other hand, while the little things may be trivial, they add up. They add up to your life. It feels like I might actually have something to say that’s not already been said a thousand times by people more familiar with the issue than I am.

Plus it’s a way to assert some normality in a world that feels decidedly abnormal.

I’m not likely to come up with anything super-profound on the most important topics, but I can make short statements, and I can amplify other voices. And I’m trying to come to grips with the fact that that’s important. I’ve been reading a lot more and posting a lot less over the past year or so, but even if I can’t say anything profound, I shouldn’t stay silent.

So I’ve been microblogging, and linking, and reposting — all things that are better suited for a service that’s built around those use cases. When I have something longer to say, I do try to pull it in here, because a blog post is better than a Twitter thread… But I think more people probably see my retweets than my blog posts, anyway.

Portable cellular phone tower on wheels.I believe that any network-aware mobile app should assume network access will be spotty. People step into elevators, ride buses through tunnels, attend large events where they’re competing with thousands of other phones…there are all kinds of reasons you can lose your connection.

That’s why I like the sync approach taken by Gmail on Android. Read, write, label, file, reply…pretty much anything can be done without a connection, and it’ll push your changes as soon as you get back into range of a signal. That’s also why I’m more likely to skim Twitter than Facebook while waiting for the elevator at work – Ubersocial has already synced recent tweets for me to read, but Facebook usually can’t even load until the doors open and I lose all access.

Right now, though, I’m looking for an offline posting app. I’m planning for Long Beach Comic Con next month, and I know from experience that T-Mobile has no signal at all on the main floor of the convention center. I’d like to be able to tap out a tweet when I think of it, hit send, and have it queue up the post until the next time I make my way up the escalator to the lobby. (Ubersocial used to do this, but doesn’t seem to anymore.)

What I’d really like to do, though, is upload photos offline to Twitter, Instagram or Tumblr. It’s not a huge deal, since I can still post when I surface for lunch or coffee — that’s when the photos would actually go out after all — but if you’re going to make a point of posting things in the moment, it helps if you don’t have to hold that moment in your mind so long that it distracts you from experiencing the next one.

Any recommendations?