YMMV, I think I only tried to sign up on 3 websites where it was not working. You can fallback to the original email address in those case.
The funniest part was that for one it work great for the signup part, but they used a third party tool for licences that broke because of my e-mail.
For another, only the js code was verifying the e-mail, and I could push it by removing the validation. When the owner had to validate my account, they got a message that the e-mail was incorrect when they tried to submit the form. They called me and had a great discussion about web apps security. We had a good time.
I would point out that it kind of prevents you from checking if your email is in a leak database as you need to test each aliases you used.
YMMV, I have 2 headsets I've never been able to make working reliably under windows 10 and 11. Cheap stuff, but they are are flawless under linux and with my phone on android.
Not to say there are no issue on Linux, but these days it's way better than 15 years ago.
Oled pc screens have a terrible reputation for text. Some more than others, but it seems it's better to stick to lcd if you happen to read or write a lot.
Interesting, my path is a bit like the opposite. I tend to avoid categories of tools that abstract too much the problem in a "magic" way for the same reason: you can't easily understand what's going on behind the scene, and you have to dive in each time you enter a corner case. If you can't control what it is doing on each step, then you can't be sure it will be doing what you expect and this can become a mental effort that outweight the tool benefits.
I would not call apps built statically "the correct way". It offers benefits but also drawbacks. One of them being that you can't update statically linked libraries in it with security fixes without replacing the binary completely, which can be an issue if the context does not allow it (unsupported proprietary software, lost dependency code, ...). It can also lead to resource consumption faster, which can be an issue in resource constrained systems.
I tend to think that they mostly should be using their own user agent, and if not be desguised as the most common ones to avoid being detected too easily. Web scaping probably has been mostly running under Linux before the age of AI anyway. I'm not in the field, so if anyone more trustworthy info on that...
As a end user, I find it quite restrictive. There might be some software I won't be able to fork/modify because they were MIT. I'm not the owner of the software anymore.
I don't see how "return (key, value)" is less readable than it's list counterpart. Now, why using a list that can grow, and so takes more space and maybe less efficient, for something that should not?
I read somewhere here that, in the case of what's app more metadata is shared with meta, and telegram doesn't have E2EE by default for groups.
Didn't check though.