nikclayton / v2-statuses.md

Created February 2, 2026 15:51

Most important

Survey what other servers have done and don't reinvent the wheel.

Support posting a thread

See mastodon/mastodon#32171. In that I suggest v1/thread, but this could just as easily be v2/statuses.

Different API routes for posting a scheduled vs. a non-scheduled status

nikclayton / pachli-current-adb-log.md

Last active November 14, 2025 10:13

Getting a Pachli Current log with `adb`

Synopsis

If Pachli Current crashes it normally allows you to e-mail a crash report to team@pachli.app which can help troubleshoot the problem. Sometimes that might not work. In this case you can retrieve and e-mail the log yourself. This document explains how.

Before reading this document you should:

Be comfortable installing and running command line tools.
Have a computer running Linux, Windows, or OS X.

nikclayton / tusky-diffs2.md

Last active February 4, 2026 12:47

tusky-diffs2.md

Snapshot (accurate as of 2025-10-01 I think) of features/functionality Pachli has relative to Tusky, since people keep asking me what the differences are. This is not exhaustive, it's just the ones I think most people are likely to be interested in.

Entirely possible there are also features Tusky has that Pachli doesn't. I can't speak to those.

Monthly release cycle, so you get new features faster
Pachli shows your whole timeline. Tusky can miss posts. See these bug reports for examples.
More features:

nikclayton / pachli-rollback.md

Last active July 30, 2025 14:17

The problem is triggered by any account on your home timeline that has a Role associated with it.

That's probably your server owner @doktorzjivago.

Options I can think of are:

Mute or unfollow

Temporarily mute or unfollow @doktorzjivago (use the web UI to do this) until I can release Pachli 2.15.1 with a fix for this.

nikclayton / purplerabbit-emoji-bug.md

Created July 5, 2025 08:38

If you're not sure about any of this you can contact the GoToSocial devs at https://codeberg.org/superseriousbusiness/gotosocial#contact -- there should be enough information here for them to determine if this is a misconfiguration of your server, a GoToSocial bug, or a Mastodon bug.

Your account name isn't displaying properly on Mastodon. It looks like this:

Note the :purplerabbit: in there.

This is because you have several emoji references in your account's display_name, but your account info doesn't include all the emoji details, so other servers can't show it.

nikclayton / debug.md

Created April 15, 2025 19:13

Step 1. Get your authorization token

Open your account in the browser (i.e., open https://hachyderm.io and make sure you're logged in).
Open the inspector (Firefox: https://firefox-source-docs.mozilla.org/devtools-user/page_inspector/how_to/open_the_inspector/index.html, Chrome: https://firefox-source-docs.mozilla.org/devtools-user/page_inspector/how_to/open_the_inspector/index.html, Safari: https://developer.apple.com/documentation/safari-developer-tools/inspecting-safari-macos, then https://developer.apple.com/documentation/safari-developer-tools/web-inspector).
Make sure the inspector is showing network requests

nikclayton / bot-tests.md

Created February 25, 2025 17:16

[napkin sketch]

Create 1-N test bot accounts that follow different subsets of each other. Have them post predictable content on a regular schedule.
Monitor the bot posting software. Have it report errors and latency, and store the ID of each post when it's generated.
Write a client that, authenticated as each bot, fetches various permutations of the bot's home timeline with/without min_id/max_id/limit set. Because each bot's posts are predictable you can predict the timeline contents for each query, using the status IDs stored earlier. Have the client report good/bad results and latency to the monitoring system.
Alert on errors, and if latency exceeds some threshold.

nikclayton / tldr.nettime.org.md

Created February 11, 2025 09:39

To: Admins of tldr.nettime.org

Your server is configured with a reference to a URL on a server with an invalid SSL certificate.

To recreate this;

Fetch https://tldr.nettime.org/.well-known/nodeinfo

At the time of writing this has the following content (prettified):

nikclayton / df-bug.md

Created February 3, 2025 19:10

Script to trigger the (possible) Dragonfly bug on a Mastodon account.

If this doesn't find any problems within the first limit=90 posts on your home timeline you can step back further by adjusting the first curl command in the script.

#!/bin/sh
#
# Assumes
#  - curl and jq are installed
#  - $TOKEN is your account's bearer token

nikclayton / Mastodon SLAs.md

Last active January 21, 2025 10:35

Mastodon SLAs.md

Note

My previous post got some feedback from junior SWEs arguing -- roughly, and I'm paraphrasing -- the costs were way off and anyway this wasn't important because last year Hachyderm had "99.996% uptime" relying on a handful of volunteers.

This feels like a teachable moment, so here's an excerpt from the discussion that followed. I'm paraphrasing and removing names because the goal here is not to call out people earlier in their career, it's to highlight some of the things you need to think about when deciding if you want to run a service that people can rely on.

99.996% uptime or something

Right, but that's meaningless without knowing what the goal was, and an agreement on what "downtime" means. If the goal was higher then Hachyderm failed.

Nik Clayton nikclayton