FreakLegion
Joined 15 years ago
Karma
2,123
Submissions
739
Member since
Mar 31
Recent submissions
Comment · 5 days ago
> there aren’t swarms of automated pwnbots out there that will insta-root your server
There are, they just didn't have a working exploit. Anyone with a honeypot can tell you attempts were widespread going back to early last week, but it wasn't until Saturday that we started to see successes.
Comment · 6 days ago
They're all CLI tools and they all support LSP. The only setup advantage here is Pylance's, by virtue of shipping with VS Code. Other tools take two clicks to enable, plus or minus typing the tool's name into a search bar.
Comment · 6 days ago
Pyrefly and Zuban are faster. Pyrefly and Zuban use less memory. Pyrefly and Zuban score higher on the type system conformance test.
Use whatever tools you want, but don't kid yourself. There's a reason Google adopted Pyrefly.
Comment · 7 days ago
No, he didn't. He was missing an address leak.
Comment · 7 days ago
There were no known breaches or end-to-end exploits as of Friday. I've seen LLM hallucinations purporting to be exploits and real exploits missing pieces (address leaks), but nothing complete. Friends at some of the bigger IR practices (CrowdStrike CAO, Unit 42, Talos) have said the same thing.
It'll happen sooner or later, but all signs are that this was first and foremost a process nightmare. It wasn't another Log4Shell.
Comment · 7 days ago
Ty isn't a compelling option. If you want support for dynamic libraries, mypy is king. If you want speed and strict conformance, Pyrefly and Zuban are better.
Ty's original pitch was that it would have strong inference and be useful for gradually typing existing, untyped codebases, but AI made that moot. Adding types to existing code is now trivial.
Comment · 9 days ago
More cache misses, and also an increased false positive rate from doing multiple lookups. A similarly optimized cuckoo filter (cache line-sized buckets/windows and SIMD queries) is both smaller and faster.
Comment · 10 days ago
I've seen the mods change account names for folks in the past. You can reach out to them at [email protected].
Comment · 10 days ago
I wouldn't say plain, but it's a generic LLM design. Which made me curious whether the blog was around with a different look before AI was commonly used for such things, and it turns out it was, at https://www.pzuraq.com (which now redirects to the current site).
One article survived the move, so you can compare:
https://web.archive.org/web/20220426154343/https://www.pzura...
https://maevyn.codes/four-eras-of-javascript-frameworks
Edit: Loading any page of the old blog on archive.org always errors out initially. Click back to the blog list and then on the article again.
Comment · 11 days ago
It's absolutely a speed optimization, although more for reads than writes. The 64-byte cache line bit is a standard blocked Bloom filter. Add SIMD queries and that's about as fast as these things get.
The other side of the tradeoff is bumped ribbon retrieval. Blocked Bloom filters are about 50% bigger than BuRR.
Comment · 11 days ago
I'm describing the data structure from the article, which is partitioned twice: first into 64-byte, then into pairwise coprime-sized chunks. The 64-byte chunks are what you're quoting as "blocked", the pairwise coprime-sized chunks as "partitioned". The space inefficiency I mentioned applies to the 64-byte chunks.
Comment · 12 days ago
NB: You're trading non-negligible space efficiency here, which gets worse as you lower the false positive rate. Partitioning means uneven occupancy rates across partitions, and either you accept low occupancy (increased filter size overall) or you're pretty much guaranteed to have hot blocks (increased false positive rate for specific partitions).
Comment · 18 days ago
I shouldn't have borrowed 'misrepresent' from the person I replied to; 'misunderstand' or 'misinterpret' would've been a better choice. My read of the paper is that you can posit a stable model with perfect recall capable of doing genuinely useful things and it doesn't meaningfully affect the argument, which is more philosophical than technical.
I don't mean to defend the paper in general, though. It has plenty of problems.
Comment · 19 days ago
Column Tetris is one example: https://stackoverflow.com/questions/2966524/calculating-and-....
Optimizing column layout has been enough for me to leave OLAP workloads in Postgres a few times when I otherwise would've had to spin up something dedicated for them.
Comment · 19 days ago
It was probably flagged because however much you (and for the record I, and most other people here) may think that the rise of sports betting and prediction markets are a problem, this particular article is full of nonsense and really quite bad.
[email protected] where x=kcl y=fcb z=gmail