Thank you for your write-up, I ran into similar issues a couple of months back.
Another gripe with the technical implementation of mastodon is the CORS headers required to access the ActivityPub API [0].
Because of this issue, an activitypub-aware frontend for mastodon has to have its own mastodon server running, which adds a whole bunch of hurdles.