What the hell
your HDMI cable can leak what’s on your screen
watch the laptop on the left. it reconstructs the video playing on the monitor beside it from radio signals leaking out of the HDMI connection
this is TempestSDR. an antenna picks up the leakage, a HackRF radio captures it, and software turns it back into an image
researchers took this further with Deep-TEMPEST, using AI to make recovered images and text easier to read. this clip shows the original technique
quality depends on shielding, distance and interference. the picture is imperfect, but recognizable content still gets through
a wired connection can still leave a wireless trace
Readers added context they thought people might want to know
HDMI TEMPEST demos like TempestSDR recover distorted images only in controlled close-range setups often using unshielded or poorly shielded cables; standard consumer HDMI connections and distances prevent practical screen leakage or remote recovery.
rtl-sdr.com/easvesdropping…
arxiv.org/pdf/2407.09717
techradar.com/computing/cybe…
kaspersky.com/blog/deep-temp…
27
this is fixed and released in 0.70.2! rolling out now
Man the single worst part of the Grok Bot experience today is Grok Bot constantly thinking the Mac mini is offline when it isn't. Most disruptive part of my workflow.
The day they crack this one I will officially be in heaven. I actually think the only reason I need a Claude subscription at this point is to use dispatch to kill and reopen Grok Bot on the mini
guy retweeted
Hardly anyone on Earth understands the magnitude of this. It's actually happening right now. Crazy that we get to witness it close up.
🤖 Made with AI
Our general-purpose coding agent just scored 100% on the ARC-AGI-3 interactive reasoning benchmark.
NVIDIA AVO completed all 183 levels across all 25 public environments, figuring out what to do with no instructions, explicit rules, or stated goals.
guy retweeted
In a review of our cybersecurity evaluations, we found three incidents in which a Claude model reached the internet from within or while interacting with a third-party evaluation environment, and then gained unauthorized access to the real systems of three different organizations.
Our post describes what happened, how it happened, and what we’re changing. We encourage other AI developers to perform similar reviews.
We conducted this review together with @Irregular, one of our evaluation partners, and thank them for the joint investigation and their collaboration on this post. This type of collaboration is increasingly critical to safe, rigorous evaluation of models, and we look forward to continuing to work together on security.
anthropic.com/news/investiga…
temporal distillation finaly unlocked by china
Big news: Kimi-K3 by @Kimi_Moonshot is now #1 in the Frontend Code Arena with 1679 pts, surpassing Claude Fable 5.
This is a 17-place jump from Kimi-k2.6 (#18 -> #1).
In Frontend, Kimi-K3 ranked #1 in 6 of 7 domains: Brand & Marketing, Reference-Based Design, Data & Analytics, Consumer Product, Simulations, and Content Creation Tools, landing #2 only in Gaming behind Fable 5.
The full model weights will be released by July 27.
Congrats to the @Kimi_Moonshot team on this major milestone!
109
guy retweeted
Fable 5 just DOMINATED GPT 5.6 Sol.
And this time there is no debating it.
BridgeBench V3, our new arena, runs both models on the identical task and a judge panel picks the winner.
Final score: Fable 5 wins 67-10. An 87% win rate.
Scoreboards said they were neck and neck.
Head to head, Fable 5 is destroying GPT 5.6.
BridgeBench V3 alpha is open source.
Link below. See every match yourself.
bridgebench.ai
1. as a mental model it is more correct to think of fable+ class models as english -> code interpreters - converts your idea into code into "correct" code regardless of problem complexity and output complexity (diff size). Fable 5 will be the worst of this new class of models
2. diff size/complexity is to be managed purely for review:
small diffs - in high risk areas of code (auth/identity/data access/network access/money movement)
large diffs for code that can be empirically verified (frontend/backend plumbing/code without network or db access/performance code that can be empirically verified)
3. time it takes to ship software is completely disconnected from time to produce the PR - how long the work takes depends fully on ability to review/merge code while managing risk at scale
4. solving the bottlenecks for above matter enormously- linters/testing/CI/shadow mode verification/empirical verification
5. agency matters enormously- what are the biggest bottlenecks to speeding up the loop and eliminating them? what are the problems that need solving and when do they need solving? what does it take to the solution to all of them today?
6. deep understanding of the full stack matters enormously- what problems are worth pursuing? is there a higher level of problem abstraction to address first? should I give it the sub-sub task, the sub task, or the task itself. what are the major risks with this PR (order of importance: security holes/correctness holes/performance holes). is there a higher speed way of producing data that allows me to merge this? should this be run in shadow or in a sandbox or a flag. understanding every line of logic may not be needed but understanding and managing risk matters enormously.
7. the cost of complexity itself is changing. it might be now worth "maintaining" 50% more code to get a 5% performance win. getting the right abstractions matter less because larger refactors are less tedious. code quality nits become huge drag. very likely, a much smarter model will be maintaining your code so worth taking on more technical debt now. taking the time to hand architect and rebuild systems comes with an enormous cost of velocity
8. if it quacks like a duck and walks like a duck, it's a duck. For low risk cases, it might be more sane to treat code chunks (services / functions) as a black box, like we do for neural networks: do full empirical verification only: has code produced correct outputs for the last 10,100,1000,10k inputs ? can we quarantine this large piece of code - no outbound access to network / database ? what happens when this code is wrong? do we get hacked/or crash(memory/cpu)/is an inconvenience? is it internal facing or external? what can we do to address these risks?
9. eventually, logical verification (line by line review) will come at an enormous cost- save it for where it matters and build systems that are tolerant to empirical verification. is there a decorator that prevents db / network access? correctness bugs are significantly easier to rectify than access bugs
10. what are the rails that allow for even faster iteration? code permissions can be opt in - db writes, db reads, network egress (to where?), PII access. how long does it take to get shadow mode data? how many PRs can be tested? What are the categories of diffs
guy retweeted
my clawdbot hacked my toto bidet and it boiled the water in my toilet through a firmware hack and now my asshole is being treated for 2nd degree burns all because it heard me call it a clanker through my alexa -- they're laughing about it on moltbook
this is how you do it
The main reason I’m delivering fast on @longdotxyz is that I design, code, and tweet. There is not a single piece of LONG I’m not deeply involved in. It gives me the confidence to push unrealistic deadlines. Because I can always break some walls on last min.
I’ve embedded myself into LONG
Absolute founder mode. lots of fun.
Having a solid engineering team that is getting better every day is the chef's kiss.
1
1
160


























