So that's interesting: Mastodon's "Translate post" feature doesn't cache the translation result, so if you want to switch back and forth it makes fresh requests to DeepL each time.
Wonder how much of a pain it'd be to cache that clientside? Unless it's already cached serverside, and /translate only calls out to DeepL if it hasn't already done so for this status?