Naja, im Artikel steht, dass das Hochladen auf wegli die automatische Datenverarbeitung war, die gegen die DSGVO verstoßen hat. Nur ein Foto machen ist also immer noch ok

If we’re keeping with the movie lore: It would’ve been an interesting battle of ghosts vs Witch King, if he hadn’t been distracted by a blade to the face.

Eric Weinstein is a fraud and spews unscientific bullshit every day.

I think the idea behind opinionated cryptography is not only the idea of “We think this is the best, so you have to use it”, but most importantly it removes all requirements of the protocol supporting cipher negotiation. This makes the protocol much simpler, easier to audit and as a result more secure. And if the cryptography in the protocol ever shows a weakness, then Wireguard v2 needs to be released as a breaking change. See all the SSL/TLS versions

I think that part is correct, as in: corporations often use corporate proxies, which terminate the HTTPS connection internally and scan the content. However, I don’t know if these proxies can use QUIC for the outside connection

I have some problems with this article. I mean, it’s an ok overview, but is missing some critical things that make me think the author is not that deep into congestion control research.

• they do not mention Cubic, the current default algorithm for Linux, which scales a lot faster than Reno
• They link to original BBR paper from 2017, while in the meantime BBRv3 has gotten some significant changes
• QUIC still uses congestion control, usually in the form of BBRv… You cannot omit congestion control for QUIC, otherwise we would experience the congestion collapse all over again. QUIC must be TCP friendly after all.
• Last remark: congestion control is under the control of the sender, i.e. of the server. CDNs and big service providers are constantly tuning their setups, I do not expect that they run the default settings.

The Scrubs musical episode had some real bangers. It’s not always cringy or bad