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

Intel mentions requiring support on their quickstart guide: https://www.intel.com/content/www/us/en/support/articles/000091128/graphics/intel-arc-dedicated-graphics-family.html

You mention in one comment that you want to use an Intel Arc. Those require resizeable BAR support on the mainboard/CPU. Search the manuals of your Mainboard/CPU. If it isn’t mentioned, then the GPU will not work

That’s why you need backups. If you wipe your phone and only have a single other copy of your data, you do not have a backup.

I like it. This action is inevitable in my opinion, and there will always be legacy systems regardless of the timeline, better start sooner than later.

Node exporter, Prometheus and grafana

With you on that. At first I thought the list was some kind of satire…

Könnte der Enthärter sein. Wenn du die Maschine jahrelang nur mit Tabs verwendet hast und kein Salz eingefüllt hast, dann ist der Ionentauscher hinüber. Dann auf Pulver umstellen, was keinen Enthärter mit drin hat, ist schwierig.

I read somewhere, that the dye is either poisonous or carcinogenic (sorry, no source, I have to search for it again). So I am not sure if putting it in the microwave is the best idea.

This is outdated, since /bin, /sbin and /lib now should be merged with their /usr counterparts

Actually, a few moments before this shot, you see the tables from above and his robe is lying next to him

based on the historical data

https://github.com/corollari/linusrants

You should think about selling the components if the condition allows it. Even if you decide to build a second computer, you probably get better used parts in a year or later for the money you now make on selling your old components.

I would avoid the userbenchmark site, the owners are heavily biased against AMD, so their benchmarks cannot be trusted

Immer noch besser als bei den Schwaben (Ludwigsburg), hier wurde bis vor kurzem noch Flach- und Rundmüll unterschieden.

Google keep

https://wiki.archlinux.org/title/Network_configuration#Revert_to_traditional_interface_names