@polotek My apologies for the delayed reply!

I am AFK often and was kind of hoping someone more authoritative might chime in with regards to the Mastodon support in snac; since I am but a humble MacPorts maintainer down streaming snac.

"A simple, minimalistic ActivityPub instance" does sell snac a bit short, doesn't it?

Mastodon API support began with version 2.27, and the RELEASE_NOTES.md have more precise descriptions of the intention there than I can do justice rephrasing:
https://codeberg.org/grunfink/snac2/src/branch/master/RELEASE_NOTES.md#2-27

TL;DR, I think snac's Mastodon API support is there primarily to facilitate interoperability with other Mastodon-centric ActivityPub implementations and clients, e.g. @Tusky, @husky, FediLab (https://toot.fedilab.app/@apps), etc. It even supports @peertube videos as of version 2.46!

I admit, I don't have a lot of bandwidth to test all of that functionality myself, but I would guess from reading release notes that snac contributors may be testing a wider range of Mastodon clients than @Gargron ?

MacPorts does a lot of the heavy lifting from my end to test on older OSes and platforms for snac than I run personally, and the Port Health https://ports.macports.org/port/snac/details/ shows it building without issues going all the way back to OS X Snow Leopard.

Though I know @flexion tested compiling snac on IRIX vintage SGI hardware, and I'm guessing it even has a decent chance of building on much older systems with appropriate C compilers?

Out of curiosity, do you have a way of measuring the disk space utilization from your local Mastodon setup in Docker? I realize it's probably a bit of a challenge since multiple Docker instances were used if I read your write up correctly?

Food for thought: an aarch64/Apple Silicon compiled snac binary for version 2.53 is: 344520 bytes (345KiB).

Albeit that isn't representative of all the dependencies used to build it but even then I am guessing it's much lighter on resources than mainstream Mastodon + Docker, etc.?

@grunfink