@cheeaunChee Aun 🤔 That ruby annotation approach is interesting! It's a creative solution for inline translations.
I agree though—it's frustrating that despite ActivityPub having built-in support for multilingual content through contentMap
, major implementations like Mastodon don't properly display this content. If they did, we wouldn't need these workarounds.
The language filtering feature in Mastodon profiles that you mentioned is useful, but it only works well with separate posts. It's a trade-off between user experience (reading only preferred languages) and maintaining content relationship (keeping translations connected).
I'm thinking of implementing multiple approaches to give our users flexibility while we wait for better contentMap
support across the fediverse. The ideal solution would be for more ActivityPub servers to properly implement the multilingual features already in the spec!