hi, let me introduce you to LLMTor - a service allow you to access frontier models (Like chatGPT) anonymously.
Try it! https://t.co/QIEQaXQTn0
On HN: https://t.co/bU68SZG6SL
It cryptographically breaks the link between your identity and your prompts, using blindrsa [rfc9474] and tor, such that even if server becomes malicious, it cannot know which user sent a particular prompt
Give it a try!
The source code: https://t.co/73ha5zovhS
I will make a detailed youtube video on problem solving that lead to this, if that sounds like something you're interested in, let me know :D
Also, interactive protocol demo: https://t.co/D8Jrekyg4L
Last year at Rubrik I spent many months chasing a data encryption bug.
Turns out a CPU instruction was straight up lying!
Wanted to share my public writeup: https://t.co/Cbu2vVlzzT
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.
disaggregated storage based db like this can be faster on S3 than NVMe for very specific use cases,
but for general case fair comparison, this is clickbait I believe
You have to review all LLM code!
Codex 5.5 tried to push this awful hack to our Metal backend when it was coding font rendering. It decided to implement hacky "robust buffer access" style OOM check inside the shader and hacked our whole Metal binding architecture to add a special bind group slot 30 (hardcoded) to deliver sizes of all buffer bindings. This of course made the binding model super slow and required extra data for each buffer.
> unlike gaming which can just lag and reduce FPS, video (de)compression must maintain real-time to have smooth video
What? Neither of those are *hard* real-time systems. And arguably a stall is significantly more noticeable in games, as they need to react to user input
We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems, impacting a limited subset of customers. Please see our security bulletin:
https://t.co/0S939n3qHC