25 karma · joined July 19, 2026
He said „The majority of the kids shouldn't learn”, not everybody. I listened to that pod and was under the impression that he wants to be portrayed as a "grounded" person and i didn't find his takes to be out of touch.
How? QUIC is easy to fingerprint and flow classificate:
https://datatracker.ietf.org/doc/html/rfc9000#section-12.1
Speaking of bold claims, Iroh, just like Radicle, are overselling themselves:
>iroh's QUIC multipath implementation automatically switches between Wi-Fi, cellular, ethernet, LAN, LoRa, HaLow, Tor, Bluetooth—or bring your own transport.
The thing is, QUIC multipath isn't standardized.
Adding a cert to my Android phone was a huge pain in the ass. Most homelab apps like Jellyfin don't support it. The homelab space is so buck broken it assumes i don't have a public IP address to just expose things without going through the convoluted VPN setup.
I needed to temporarily move off 20TB from my NAS and bought a Hetzner storage box.
I wanted to encrypt the data before sending it so i went with the borg ssh mount. Long story short, borg failed a couple of times due to https://github.com/borgbackup/borg/issues/7672, i resumed it per documentation and got 2gb of silently corrupted data. There was no way to do data integrity checks due to broken pipes and there was no option to resume the job from the previous point either. I couldn't afford to go with the s3, backblaze wasn't an option due to placing trust into their proprietary client doing the encryption and i got majorly screwed in the end.
and a privesc also.
I was taught to be skeptical of objective benchmarks; Why should we trust them when people are benchmaxxing?
I was unpleasantly surprised when jxl's reference encoder dropped critical exif tags for no reason whatsoever from my personal archives. Turns out their lossless preset wasn't really lossless.
And then webp to JXL conversion also produced different viewing experience results as ffmpeg's webp decoder wasn't handling ICC correctly.
I'm now very cautious of any "lossless" re-encodes.
Those requests aren't useless; They clearly optimize. What a silly take.
>to your servers
To their customer's servers, right! Most people turn on other CF optimizations like h2/h3 to origin.
Yeah, i was very confused by that, especially after they invited them to post publicly/privately. They love controlling the public communications when it comes to researchers. I remember ryrona, a guy who found VPN leaks, being censored for no reason whatsoever in their public GitHub issue tracker.
I want to discuss actual facts, observations and not your shallow social signaling replies of 0 value.
Like my personal phone?)
Installing Google Play service is in itself a privacy downgrade.
I hate this piece of shit with a passion. But hey, at least they gatekeep the worst kinds of firmware updates in their OEM pages!
https://github.com/BillyCurtis/Intel-I226-V-NVM-Firmware
I'm honestly surprised Intel doesn't provide do fwupd crate, it's such a blow to their reputation considering how popular 22x NICs are in Mini PCs and even ASRock mobos
If you're reading this - go ahead and see HOW Linux Foundation spends their money.
>RustDesk is a single open-source application (AGPL) with its own architecture. Clients connect outward to an ID/rendezvous server, which brokers a peer-to-peer or relayed session. Per the RustDesk documentation, traffic is end-to-end encrypted (built on NaCl)
Factually incorrect. If you self host a relay/coordination server - encryption works as documented.