They doesn’t use normal beta channel, and publish a new application named Bitwarden Beta.
https://play.google.com/store/apps/details?id=com.x8bit.bitwarden.beta
They doesn’t use normal beta channel, and publish a new application named Bitwarden Beta.
https://play.google.com/store/apps/details?id=com.x8bit.bitwarden.beta
Yeah. Bitwarden developed a new android client written by Kotlin to replace old C# client. This new client is in beta testing currently. The old client supports both PascalCase and camelCase but the new client only supports camelCase. And Vaultwarden use PascalCase now, so it’s incompatible with new Android client.
Hope this Pull Request could be merged soon so I can use it with new Bitwarden native Android client.
I use Yubikey 5 NFC and Canokey Pigeon, both works out of box on Linux.
Maybe you can do both: physical USIM card, but with eSIM functions. So you can move your profile from one phone to another just by plug out and plug in, and install many profiles on one phone and switch between them. There are some products can do it, such as eSIM.me, esim.5ber.com or https://github.com/estkme-group .
I use Porkbun.com. It has modern interface.
Yes unless both my phone and headphone support LE Audio.
deleted by creator
No. Just because I’m not always able to use my own device. If I use other layout and have to use other’s devices (e.g. library computer), I will be confused with normal QWERTY layout.
Canokey, there are two way:
Yeah, it works well with my Wacom CTL-671.
I prefer to use Fcitx 5 for Android instead of GBoard, not FlorisBoard. Because f5a has much better Chinese input experience than FlorisBoard, and I use Chinese.
I use the periodic table of elements to name them.
Always use absolute path. If you write some shell snippet which may be run in different environment, avoid use just command name for uncommon one.
VP9 for video and FLAC for audio. Avoid AV1 because my GPU can’t decode AV1.
That may be because the hostname can’t be resolved.
https://forum.suse.org.cn/t/topic/12280 (Chinese)
https://bugzilla.mozilla.org/show_bug.cgi?id=1296836 (upstream report)