We've also shared a blog post about features that developers will want to know about coming in 4.4.

https://blog.joinmastodon.org/2025/07/mastodon-4-4-for-devs/

Now would be a great time to update any translations that you're able to help us with. See our project on CrowdIn.

https://crowdin.com/project/mastodon

If all goes well, we hope to release 4.4.0 next week... and then, it's straight on to work on what's next in 4.5!

@MastodonEngineering

#Translation

Why are there still so many posts from both individual posters and entire instances where translation is neither offered nor allowed (http 403 or 503)

Certainly if #Mastodon wants to compete as #SocialMedia on a #GlobalStage translations into the reader's stated Interface Language should be mandatory, unless explicitly prohibited on an individual poster-by-poster basis

What gives?

As it is now, I #Mute and #Block posters who will not let me translate their posts into a language I can read

Why do I want to give up my very finite screen space to posts I'll never be able to read?

I don't, and I won't

I'm on an instance currently running v4.3.7

@FinchHaven @MastodonEngineering translations go through your server and do not depend on the other user's server

they are only offered when the posting language differs from the interface language (so it has to be properly set), and the post is not private (out of privacy concerns mostly)

@ClearlyClaire

I find it counter-intuitive that all translations are handled locally only by my own instance, given that I see such widely-varying options offered and results obtained

These post are not private -- else how do I overrule that privacy setting and see these posts in my Home feed only because the poster uses a hashtag I follow?

But net-net-net the result remains the same: if I cannot translate a post (and I go to the poster's profile and see if they post that way consistently, and/or if their instance allows translations at all) for whatever reason, why should I let an untranslatable post take up my finite screen space?

I don't: Mute and Block

With all due respect, given how much I've looked into this issue (including posting an Issue on Github, which was ignored) there really seems to be more going on here than is found in your simple explanation

cc @MastodonEngineering

@ClearlyClaire

Yes, here, opened on Nov 10, 2024:

https://github.com/mastodon/mastodon/issues/32825

The issue was that, if the Interface Language was set by both the poster and the reader to the same language (EN for example) and yet the post was *written* in a different language (FR here) no option to translate was offered

I was on v4.4.0-alpha.1+glitch (don't remember instance name now, might have been Infosec dot exchange?) so this may be ancient history now

Water under the bridge now, since now I don't even seem to see either the poster's or my Interface language display on my current (v4.3.7) instance

cc @MastodonEngineering