Ok, let me break it down because clearly I didn’t explain it well.

What is supposed to happen, scenario 1: the client encrypts your messages with the public key of the recipient, sends it to the servers of WhatsApp (or whatever service) along with some encrypted metadata indicating the recipient, which then forward the message to the recipient.

What could happen, scenario 2: the client does the same, but also encrypts another copy of your message with a public key that belongs to WhatsApp, and send both versions to the WhatsApp servers. They decrypt and keep the second version while forwarding the first one to the recipient.

Or, scenario 3: they just never bother with end-to-end encryption, and always encrypt it with the WhatsApp key, still sending it to their servers which then reencrypt with the recipient’s key before forwarding.

In all cases, messages are sent only to the WhatsApp servers, not two places. The only visible difference is in scenario 2 where the communication is larger. You can’t inspect the metadata of the message with your network sniffer, because it is also encrypted, so there’s no way to rule out scenario 3.

If the protocol is designed to be transparent by not encrypting the entire payload sent to the servers, and you have access to the recipient’s private key (those are big ifs) then you could show that there is indeed an end-to-end encrypted message in there. But this is true for how many of these proprietary services? Maybe for WhatsApp.

Just encrypt it before sending it to their servers. How would you tell that apart from any other traffic it sends? (E.g. to check for new messages, to update who of your contacts is online, etc)

Almost all services in that list are closed source, so even if they use end-to-end encryption nothing stops the client from sending all your messages to anyone they like after decrypting (in fact some of them already have it as a built-in feature in the form of backups).

There are definitely VSCode extensions which ask you to pay for them, like GitLens.

Constant audio buzzing and disconnect while docked. Need to enable Developer mode and change a setting to fix.

What’s the setting? I have this issue and the only thing I found online is that it was a known problem to be fixed in a future update.

There’s no restriction on distribution. You’re free to distribute the GPL software you got from Red Hat.

They’re under no obligation to ship you other, different software in the future. You’re only entitled to get the source for the binaries they distributed to you. If they never give you the next version, you have no right to its source.

They absolutely can, but RHEL Red Hat will likely stop doing business with them if they find out (and thus stop giving them new versions), hence why they would only be able to do this once.

It doesn’t. The GPL is satisfied as long as they provide you with the source code for the version of RHEL that they distributed to you. But they’re not obligated to continue distributing later versions to you.