Nice analysis. That helps clarify how mptcp is involved. At first I thought your response was total nonsense because I have no idea what "hungry ghosts" have to do with anything.
This isn't a theoretical problem either. My employer's website was being hammered by residential proxies a month ago. It wasn't until we setup WAF captcha rules that they mostly subsided. It wasn't even the typical exploit scanner. I don't know what the purpose was but it was effectively a DDoS.
My past experience with Debian was running it as a desktop distro on laptops which required proprietary drivers for GPU and wifi. I haven't had trouble in containers or VMs. Though I am considering switching my homelab servers (repurposed desktops running DE-less) from Ubuntu LTS to Debian testing or stable.
I guarantee it's a convenience feature. Having a Github token available make using Github significantly easier for Claude. I only use the web interface, and Claude frequently cannot access Github repos or issues, or gets rate limited. If Claude has a token, it can authenticate and not run into this annoying problem.
Really Ubuntu? They released a broken Nginx back in June that would cause workers to constantly segfault when using common modules available in the repo.
I'm running an RTX 5090 (32gb VRAM) and Strix Halo (128gb unified memory). I haven't had much time to tinker with my AI setup so I'm still running Qwen3.6-27B (NVFP4 quant) on the 5090. The prices today are just insane.
This is exactly how I write my Python. I'm currently debating between going in deep and transitioning to either TypeScript or Rust. Go's object system and error handling is too weak. Java is too verbose, but I have a soft spot for it.
The problem with PyPy, which I'm a huge fan of BTW, is it's on life-support. The only reason the past couple major versions were released was due to a few small companies or individuals directly implementing the updates themselves. That's my understanding at least. It's disheartening because I've been primarily using PyPy for 5 years, advocated for it, and was looking into contributing more to it before finding out about its state.
I have no doubt Julia's far better with this. I just wanted to point out Python does have a similar precedence for ahead-of-time compilation, albeit with byte-code only. If the Python steering council ever gets its act together, maybe Python could have real AOT and JIT.
I've never bought this argument. Underneath all of the magic inheritance in Python is just the MRO (method resolution order). That's not characteristically any different from JavaScript's prototype chain. There's no reason a Python JIT couldn't optimize everything JavaScript does, and if you do specifically access `self.__dict__`, that can be a cold, unoptimizable path.
Quite simply the audio mixing for TV and movies is utter shit. You shouldn't need a 7.3 sound system to potentially hear the actors legibly. The stereo speakers built into my TV should be adequately supported, and it is frankly the default set up for most people including myself.
What's bad about using them as opaque public ids? The only information that's leaked is approximate time of creation which is moot for most applications.
ULID is what I use. I convert it to UUID before storing in PostgreSQL. Technically it's an invalid serialization but it works. The system predates UUIDv7. I also like ULID's shorter representation.
Only decompression with Google's brotli library is affected. So if you use "Brotli" or "brotlicffi" in your Python app to decompress brotli, you're vulnerable. Compressing responses with brotli from Apache is safe.