The amount of negativity your positive comment has received looks almost overwhelming. I remember HN being a much happier place a few years ago. Perhaps I should take a break from it.
People working in one of the coolest industries on Earth really do not appreciate their lives nowadays.
I think you haven't used .NET in a while. Nowadays, logging is absurdly easy to configure. Heck, you usually don't even need to configure it, because the basics are already included in most templates. You just use the Logger class and it works.
The only time you have to spend more than 30 minutes on it is when you use some external logging libraries. And most of them are quite sane and simple to use, because it's so easy to create a custom logging provider.
Java, .NET and nodejs are all over the place around here.
The point was without configuration.
Logger class doesn't do the work for production monitoring, without additional configuration so that its output appears on the necessary production dashboards.
Where did you get those numbers from? 10k words is generally considered a CEFR B2/C1 level which already is a fluent level.
Semi-fluent, depending on how you describe it, is anywhere between 1k and 5k words. To comfortably communicate with native speakers about simple topics you need 1000-2000 words.
Signal does not know who you correspond with. The only information they keep is the account creation timestamp, and the date that the account last connected to the Signal service.
You may have confused this information with WhatsApp which indeed keeps a lot of metadata on each user.
Signal absolutely knows who you correspond with. How could they otherwise route your chat messages?
They promise to throw this information away, which is nice but not possible to verify.
They also employ a roundabout way of encrypting this data, but as they rightly point out in their article that describes the scheme, encrypting or hashing phone numbers is not safe from a malicious attacker. The space of all possible phone numbers is so small that it could be brute forced in the blink of an eye.
You place all your trust in Signal (and Google/Apple) when you use them. That may be better than the alternatives, but it's still something we should be honest about.
That said, keep in mind that Signal and Google/Apple can also trivially backdoor your software, so unless you take specific precautions against that, the details of their middleman protection isn't terribly important.
I guess you are right. It's trust-based. For an actual obfuscation Signal would need to implement something like onion routing, right? I think Session does it.
Well, TIL. That does not refute my comment, though. Signal still does not know who you chat with. It's the cloud provider who might log the IP address of the sender. Identifying the person based on that information alone would be non-trivial if not simply impossible.
It actually is. The design is just a small part of the control's cost. Then it has to go through a lot of compliance tests (the controls can't be flammable, can't break easily into shards, and so on). You have to do those tests for every car's interior part. When you squeeze everything into a touchscreen, you have to make the whole screen compliant only once.
People working in one of the coolest industries on Earth really do not appreciate their lives nowadays.