lieuwex

> something which George himself opposed.

Do you have a source on this?

I don't see what JS code would provide this?

Previous discussion: https://news.ycombinator.com/item?id=10722536

This function is user contributed. It's not official.

What kind of risk profile does one have when it is likely that both the password is known and malware has been installed on the phone, but also just access to an ephemeral login session by the attacker (which could be obtained even when using a secure enclave by waiting for the user to authenticate by themselves) would not be enough?

This is the exact same as DigiD, except that there is no cost per-auth, only per-sms. The parent comment is saying that Amsterdam wanted the users to install the DigiD app instead of relying on SMS authentication.

> recently iOS started using it although I don't know what server they attach to.

According to Wikipedia, only the carrier's RCS server is used [1]

[1]: https://en.wikipedia.org/wiki/Rich_Communication_Services#So...

HTTP/3 even more so due to QUIC's shorter handshake process.

For fun I suppose? See: esoteric programming languages

> This addresses one of the longest standing complaints about SQL, and the DuckDB team implemented it in 2 days.

what a weird thing to say.

no

Are you sure? I think the computed tab in Chrome devtools shows the actual used font.

Why is that?

I don't get why Meta’s Ads Manager platform would bring down WhatsApp, which doesn't have ads?

You are still in luck! https://redirect.invidious.io/watch?v=qwjEeI2SmiU

What? npm doesn't provide site hosting of any kind. Apart from just using the ~ convention this is not relevant at all.

For the UNIX world you'd have Midnight Commander

In drive&icloud(?) AFAIK, so that would be linked to the owner of the phone at that time.

If you really mean conversations of the original owner, I can't believe that's true after e2e has been enabled.

But it could be that messages sent to the original owner are received, since WhatsApp automatically re-encrypts and sends messages if the message has not been received yet and the key has been changed. So basically that would mean the message would be sent when the previous owner already changed their number. So the people shouldn't have sent the messages at all.

WhatsApp e2e encryption just makes sure that the only person that can read the message is the owner of the number, not necessarily the person you want to send it to.

I wanted to chat using WhatsApp comfortably using my Weechat setup.

That specific classname didn't change since the beginning of the project, I had a breaking change on WhatsApp's side one time (was several months ago already).

I'm aware of https://github.com/tulir/mautrix-whatsapp which I'm personally interested in, which uses a reverse engineered implementation of the WhatsApp web protocol.

I think "kak" still would be translated better as "shit", you wouldn't curse with "POO!". But in Dutch you can curse with "KAK!", just as 'SH*T!' in English.