Mastodon is a genuinely different kind of hard to block, because it's built specifically to avoid the mechanic most of this list runs on. It's decentralised — spread across independently run servers, called instances, that federate with each other — and its timelines are mostly chronological rather than algorithmically ranked for engagement. There's no single company tuning a feed to hold your attention. The pull is real anyway, and it comes from somewhere else entirely.
What actually makes Mastodon hard to close
A chronological timeline from everyone you follow, across however many instances, behaves like an inbox rather than a feed: step away for a few hours and it doesn't refill with something new and exciting, it just accumulates, and returning to a long unread backlog creates its own specific pressure to "catch up" rather than to keep scrolling for novelty. Joining a particular instance also means joining a particular community with its own culture and conversations, and checking in on that specific community can feel more like tending a relationship than consuming content — a different, more personal kind of obligation than an algorithmic app's engagement bait. And because there's no single ranking system deciding what's important, everything in the timeline carries equal visual weight, which makes it harder to skim past things than a feed that's already done some filtering for you.
The built-in iPhone route, and where it gives way
An iOS Screen Time App Limit works on Mastodon exactly as it does on any app: a warning, a lock screen, and a single "Ignore Limit for Today" button that clears it in a tap, gated only by a Screen Time passcode you set and know yourself. The mechanism doesn't care whether the timeline behind it is algorithmic or chronological — but a limit that resets nothing about the backlog waiting on the other side of it just delays the catch-up pressure rather than reducing it.
The built-in Android route, and where it gives way
Digital Wellbeing's App Timer greys out Mastodon's icon at your limit and offers to extend it the moment you tap it, with the whole system adjustable or removable from Settings at any time. As with the iPhone route, the timer interrupts when you check, not how much has piled up since the last time — which means the backlog just keeps growing quietly in the background either way.
What changes when the toll is three questions
Mr. Grummel's toll doesn't care whether what's waiting is an algorithmic feed or an honest, chronological backlog — three questions sit in front of the app either way, and answering them costs a few minutes of real thought regardless of how much has accumulated since you last checked. That's specifically useful against a catch-up-shaped pull, because the anxiety of an unread backlog tends to make opening the app feel urgent and automatic; a toll that requires actual thinking breaks that automatic reach even when there's genuinely a lot waiting.
A realistic day
Right now: a few hours away from your phone turns into forty minutes of scrolling back through everything you missed, not because any single post was that compelling, but because stopping partway through an unread backlog feels incomplete. With the toll in place: opening Mastodon after a gap still runs into three questions first. Some days you answer it and scroll through the whole backlog anyway — a real community is worth keeping up with. Other days, the few minutes of thinking are enough to notice the backlog will still be there in an hour, unharmed by you not reading all of it right now.