The addon version works on Android.. There’s an issue/“idea” for Chinese support as well. If I recall correctly, though, one of the problems is tokenization (the languages currently supported for example have spaces to separate words).
Invidious and NewPipe/Piped aren’t affected as far as I know, since they use YouTube’s internal APIs directly. They’re mostly only affected by changes to the API itself, and IP ratelimits/blocks.
In my opinion, such bots indicate more of a need for some kind of easy “pipe” feature to integrate tools to transform a post before publishing, so that all of the tweaks can be done within the post instead of as a bot reply. For example, there could be a “MTG-ify” button that takes the text in the input box, turns the double bracketed names into CommonMark links, and then puts the modified text back into the input box.
My opinion is that bots should be classed by how they operate.
Summoned bots should be mostly free of restriction. If it needs someone to explicitly summon it, then the onus is on them to not needlessly summon bots. Requiring explicit
Keyword/auto-summon bots should at a minimum be required to implement easy user/community/instance opt-out. I think the most viable would be allowing auto-summon only when explicitly allowed by the user, community, or instance, but allow them to reply to manual summons without restrictions.
So how it would work is if someone had a bot that would, for example, post Nitter links in response to Twitter links, it would be allowed to:
Used US and JP qwerty, both are fine after a while, but switching can be annoying (mostly I mix up whether " or @ is Shift-2).
The one thing I hate is the fragmentation of the bottom left cluster. I started out on keyboards with Ctrl Fn Super Alt, but now I much prefer Fn Ctrl Alt Super.