A step-by-step guide on installing Mastodon via Docker, configuration tailored especially for 2024
This is the first in probably a series of posts as I dig into the technical aspects of mastodon. My goal is to get a better understanding of the design of ActivityPub and how mastodon itself is designed to use ActivityPub. Eventually I want to learn enough to maybe do some hacking and create some of the experiences I want that mastodon doesn’t support today.
The first milestone is just getting a mastodon instance set up on my laptop.
Nah, nevermind. I think it was a matter of ACL. Wasn’t able to adjust ACL after my Pi-Hole IP address changed.
The Bluesky PDS server can go well with Tailscale in the same system, provided that you don’t use the Tailscale MagicDNS, by running sudo tailscale set --accept-dns=false
It appears the PDS doesn’t go well with Tailscale.
It’s crontab but in a container. No ports. No GUI. No BS. Just cron in a container. Why? Because someone decided that setting up cron jobs the normal way wasn’t edgy enough. Now you get to deal with Docker AND cron at the same time. You’re welcome.
Two days in, and my Github issues on PDFDing remains unanswered: github.com/∞
This just goes to show how much of a mess it is maintaining a #Mastodon instance. Relays? FakeRelays? Sideqik? Not that I’m discouraging anyone, but be sure to allot time for these stuff: blog.thms.uk/∞
The Wallabag Chrome Extension is so useless, I can’t obtain the token from my instance. Provided the correct client ID, client token, username and password, but it just won’t push through.
For further reading.