@lukem @endali So, we have two problems here.
1. Poor UX design of Mastodon (and, possibly, its clients).
and partially being a result of it:
2. People are not aware about the functionality of the tool they are using.
Using CW for non-default-language is not a solution for any of them.
@agturcz Possible. But Mastodon has enough culture and UX problems for me not to care about one particular case for using / not using CW (especially a very niche one in my book). @endali