I actually got almost half of my colleagues to use Signal. Well maybe they probably still use another chat app even when talking to a fellow colleague who has Signal, but at least I got them to register an account.

I fail to see any reason for hating a chat app so passionately except possibly for privacy concerns, which is definitely not the case here.

Mine is not blocked yet. I am definitely worried about this though. I am in East Asia.

Wonder how much YouTube is going to squeeze out of this ad blocker blocking.

Try https://github.com/osfans/trime. It has multiple input schemas (i.e. pinyin, zhuyin, cangjie, etc.) to choose from, and they are great for typing Chinese. Admittedly it only supports the C in CJK, but it is absolutely worth a try if you don’t need Japanese or Korean.

Try Thumb-Key. It’s a keyboard made by Lemmy’s main developer. It uses a rather exotic layout, but once you get used to it, it is so much better than qwerty.

What is the main reason you (presumably) use Chrome over Firefox? People here might be able to help you solve the problem.

I agree with your point and really want to upvote it, but to be honest the way you put it was kind of rude. I’ll hold my upvote for now.

Thanks for the suggestions. I already use BitWarden, but I use the free tier and sadly self-hosting is not really an option for me (for now). I decided to use Authenticator Pro as suggested by @isolatedscotch@discuss.tchncs.de, and I’ll import the accounts maybe this weekend.

By the way I think I should clarify that I’m not a libre extremist trying to avoid everything Google (yet. maybe I’ll become one in the future) I just want to slowly move away and also not start using Google services that I don’t already use.

Thanks! I’m gonna try out Authenticator Pro.

Ahhh, thanks! After closer inspection of the link otpauth://totp/lemm.ee:randint?secret=[redacted, 64 characters]&algorithm=SHA256&issuer=lemm.ee, it does indeed specify SHA256. Looks like Authy just uses SHA1 regardless. Maybe I should switch back to GAuthenticator, but you know, Google…

Ah, ok. Thanks!

Edit: I just read the comment by @gnzl@nc.gnzl.cl, and apparently the root cause is that Authy uses SHA1 despite the link clearly specifying SHA256. Now I wonder what you mean by 2FA doesn’t completely work yet?