There has obviously been a regime change in software security. Protocols with large complex surface areas are going to be more easily exploited by these models. I'm somewhat surprised the vulns are not already worse and more numerous.
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.
This is wild. Google Research demonstrates a ~20x more efficient implementation of Shor's algorithm that could break ECDSA keys within minutes with ~500K physical qubits.
Google is now are more confident on a 2029 post-quantum transition. We are no longer looking at mid 2030s, we could have quantum computers of this scale by the end of the decade.
They believe this result is so severe that they are not publishing the actual circuits. They instead published a ZKP proving that they know of the quantum circuit with these properties. This is very atypical, showing Google thinks this is serious shit.
All blockchains need a transition plan ASAP. Post-quantum is no longer a drill.
Introducing TBD
The first product where anyone can:
🗳️ Launch global polls and measure public opinion at scale
📈 Create prediction markets on their outcomes
🏧 Earn USD rewards
Our markets have large upside. Our polls have human signal.
Wait, what? 👇
The one constant in memecoin trading has always been groups.
Telegram is where traders scan, debate, and decide together.
Quickscope is built with a deep understanding of how trading actually happens on Telegram.
@Neovim I've been looking for something like this.
I had to use Alacritty, and customize the `terminal-launcher` script to customize the PATH + set an env variable. It works great.
Half the internet seems to be down thanks to the us-aws-east-1 outage
Perplexity, Amazon .com both down (just 2 services I tried to use)
When aws-us-east-1 sneezes, the whole world feels it indeed
Many new retail perp traders have just received a crash course in auto-deleveraging over the past 24 hours. It’s a feature that seems like an obscure technical detail until it actually happens.
@dystopiabreaker@hopes_revenge I believe the keylogging issue has been addressed in Wayland, but your original point still stands and is a big problem.
My "For you" feed here is pretty fucked. So much noise and so little actual value. Feels like the algo is incentivizing the worst behavior. At least the Following feed still works.
@jacobdotsol@callum_codes I agree this is not intuitive and should probably be reversed. I've actually had Cursor try to change my decoders to encoders, because it continues to also be confused by the naming. 😅