As someone who has worked on IRC protocols, I wanted to understand how this actually works, but the docs are so LLM generated this is not worth my time:
Everything that carries what somebody said is written down as owed to each instance it is owed to, and delivered from there: a direct message, which has nowhere else to come from, and a channel message, which used to be offered once and forgotten.
The forgetting was not obvious, because it usually did not show. An instance that had gone away noticed on the way back and walked the feed in section 7, and the message arrived late rather than never.
Even if they are good the vulnerabilities have to be there. There's lots of things turning up like Local Privilege Escalations (LPE) in Linux, but serious people didn't expect the kernel to be a boundary for a sophisticated attacker.
A lot of the vulnerabilities LLMs are finding now are the "long tail" and affect only particular configurations, I would be surprised if e.g. a widely applicable RCE is found in Linux (but I'm also not going to bet against it).
Where this gets interesting is the long tail can be used to target a particular system and this is where defense-in-depth becomes important for every organisation.
They are QSFP56-DD which can be split using breakout cables. So it's 4 x 400GbE ports, which could in theory be split into as many as 32 x 50GbE ports. (Although whether that then ends up being an economical thing to do is a different matter.)
Ahh yeah, I've seen people using those. I was thinking you'd ideally want to connect them full speed, but it looks like they're 200gbps ports anyway, and I guess even if they were 400gpbs, you don't really need that much for cross-GPU traffic for MoE models doing tensor parallel.
I put a short link on a family thing and someone complained it didn't work. Turns out iOS OCR recognised a "-" as a "=", so this isn't just people typing it wrong.
Now my short links implement case insensitivity and striping all non alphanumeric characters, i.e. a "-" is optional and any other symbol character is also stripped.
nyc.gov seems to do case insensitivity but doesn't strip "-", so you do need the "-".
Simple -- you just add a custom SQLite VFS that ensures particular SQLite pages are mapped into underlying OS pages that are appropriately mprotect()ed. Try to modify the executable pages and you crash (W^X). Or you know, don't try to use a hack like this where security matters.
SQLite's unix VFS is actually using a mixture of mmap and write() by default[1] and you'd need to combine that with mseal() and some more pieces to actually pull it off. It would probably be possible.
