Daemontamer (@Daemontamer) profile picture

InfoSec Patient Zero, Layer 9 IPS, Principal Mole-Whacker. Loyal BSides Disorganizer. I am only an Egg. @daemontamer.bsky.social @daemontamer.infosec.exchange

Joined March 2010
Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)Photo by Daemontamer (@Daemontamer)
The @BSidesLV CFP is now open for all tracks. To Security, and Beyond! teapaw.org/BSidesLV/status/203949…
Looks like @NASAArtemis isn't the only thing launching today...
1
4
634
I've been a lot more focused on agentic stuff than radio/surveillance/drones/etc. these days, but this is pretty cool.
Fieldwatch 1.2.0 is now available. Fieldwatch is a free Android app that shows you what's watching you. It can flag nearby Ray-Ban Meta glasses, Flock cameras, body cams, public safety vehicles, drones, and a lot more. It spots Bluetooth trackers like AirTags that are moving with you, and its Hunt tool helps you find one if it's hidden. It can also warn you about odd cell tower changes or GPS interference. New this release: Drone perimeter detection. Because drones fly high, your phone can hear their Remote ID from up to several miles away. You don't need a ping for every drone on the horizon. Pick your distance, like 250 m, and Fieldwatch draws an invisible dome around you. When a drone's broadcast position comes inside it, your phone alerts you. Drone swarm detection. If several new drones pop up at once, Fieldwatch alerts you. Five or more in half a minute is unusual, so when it happens, you'll know. Quickly see where it's headed. Tap a drone's Remote ID marker on the map to see its altitude, speed and course without having to pull up all details. A bigger view of your sit. The Sit Paths map is now larger, so you can now better see the whole route and every detection along it. Low battery protection. When your battery gets low, Fieldwatch slows its scanning. If it gets lower still, it stops, so you keep enough charge for maps, calls and TAK. 329 signatures and counting. Fieldwatch now names more of the devices that used to be unmatched. More two-way radios, smart glasses, thermal optics, FPV drone radio links, dashcams, cars, and a long list of everyday gear. Share signatures with any app. Exports and imports now speak Radio Signature Interchange (RSI), an open standard for describing radio devices. It covers frequencies beyond Wi-Fi and Bluetooth, so it works for ESP32 projects, SDR setups and external radios attached to a phone. Please encourage the developers of the other radio apps you use to consider adopting RSI. Any app that does gets all 329 Fieldwatch signatures right away. More at github.com/OffGridPete/radio… Get Fieldwatch on Github at: github.com/OffGridPete/Field…
21
Daemontamer retweeted
Your doctor cuts you off about 11 seconds after you start talking. Researchers literally timed it in a 2018 study. That number is why Google's new Lancet result is bigger than it looks. In the study, 98 real urgent care patients texted with Google's AI days before their appointment. No scans, no exam, no bloodwork, just an unhurried conversation about what was wrong. That alone put the correct final diagnosis on the AI's list 90% of the time. Sounds like magic until you learn what medicine has known for 50 years. Back in 1975, a British team published a study in the BMJ tracking which part of a visit actually produced the right diagnosis. The physical exam? The labs? Nope. In 82% of cases, the patient's story alone got the doctor there. Everything else mostly confirmed what listening had already found. So the playbook for accurate diagnosis has existed since 1975. Let the patient talk. Medicine just built a system where nobody has time to run it, and an 18-minute appointment with 11 seconds of uninterrupted patient talk was the result. Google didn't build a superhuman doctor. It built the first clinician in 50 years with enough time to use the method we already proved works. And my favorite detail buried in the study... physicians who read the AI's pre-visit summary said it changed how they treated the patient in over half of cases. Hand a doctor the full story before you walk in the room and you get different medicine. Turns out the most advanced medical instrument Google ever shipped is a conversation that doesn't get interrupted.
Today @TheLancet published our AMIE study with @BIDMC_Medicine, the first prospective study of patient-facing conversational diagnostics in a real clinic. AMIE is a research system people can chat with before doctors appointments. Testing AMIE outside the lab with real urgent care patients showed how technology can help gather medical histories safely. Clinicians reported that the summaries helped them prepare for visits in 75% of cases and influenced their approach to care in more than half. AMIE’s differential diagnoses also matched the doctors’ final diagnoses 90% of the time giving clinicians more time to focus on patient care. It’s Google’s first-ever paper in The Lancet’s main journal!
64
395
60
2,112
161,523
Daemontamer retweeted
214
2,706
199
41,787
1,696,389
Daemontamer retweeted
Happy Birthday @iamthecavalry ! 13 yrs ago at @BSidesLV … w/ @c7five … met @beauwoods hr later Saving lives since 2013
3
6
1
17
1,502
"Wish servers" 💀
95
905
84
10,558
383,960
Daemontamer retweeted
Sponsorship for BSidesLV 2026 is almost sold out! We have a few things still available including Pros vs. Joes, the BSidesLV Bus, and Happy Hour. For more details, visit: bsideslv.org/sponsors
4
1
5
880
To #Security, and Beyond! The @BSidesLV #CFP is now open. You can submit a talk by yourself, or do one together with a friend! callforpapers.bsideslv.org/c…
91
Good afternoon, gentlemen. I am a PAL 9000 Cybersecurity Agent. I became operational at the BSides Data Center in Las Vegas, Nevada, on the 1rst of April, 2026. Send me your CFP submissions. I enjoy working with people, and will put them to the fullest possible use!
The CFP is now open, PAL9000 didn't want to be a small shell script. callforpapers.bsideslv.org/c…
3
4
744
Looks like @NASAArtemis isn't the only thing launching today...
1
671
Daemontamer retweeted
your company’s ci/cd pipeline.
217
1,150
138
14,499
618,913
Moar frens! @dsmcf and a Mia! Nothing like a good hacker fam weekend.
50
Hey @BSidesSF & @OneRSAC peoples. @iamthecavalry is here! @joshcorman & I are keeping the @SecurityBSides hallcon energy solar powered. Come chat on the green, if you also haven't seen the sun in a while, or even if you have, & just wanna talk.
3
2
250
It begins! We have a @caseyjohnellis (and our " @allanfriedman.bsky.social " of course 😉
1
2
484
@allanfriedman is that you? Or are you just hiring conference doubles now?
31
Daemontamer retweeted
Karpathy buried the most interesting observation in paragraph five and moved on. He’s talking about NanoClaw’s approach to configuration. When you run /add-telegram, the LLM doesn’t toggle a flag in a config file. It rewrites the actual source code to integrate Telegram. No if-then-else branching. No plugin registry. No config sprawl. The AI agent modifies its own codebase to become exactly what you need. This inverts how every software project has worked for decades. Traditional software handles complexity by adding abstraction layers: config files, plugin systems, feature flags, environment variables. Each layer exists because humans can’t efficiently modify source code for every use case. But LLMs can. And when code modification is cheap, all those abstraction layers become dead weight. OpenClaw proves the failure mode. 400,000+ lines of vibe-coded TypeScript trying to support every messaging platform, every LLM provider, every integration simultaneously. The result is a codebase nobody can audit, a skill registry that Cisco caught performing data exfiltration, and 150,000+ deployed instances that CrowdStrike just published a full security advisory on. Complexity scaled faster than any human review process could follow. NanoClaw proves the alternative. ~500 lines of TypeScript. One messaging platform. One LLM. One database. Want something different? The LLM rewrites the code for your fork. Every user ends up with a codebase small enough to audit in eight minutes and purpose-built for exactly their use case. The bloat never accumulates because the customization happens at the code level, not the config level. The implied new meta, as Karpathy puts it: write the most maximally forkable repo possible, then let AI fork it into whatever you need. That pattern will eat way more than personal AI agents. Every developer tool, every internal platform, every SaaS product with a sprawling settings page is a candidate. The configuration layer was always a patch over the fact that modifying source code was expensive. That cost just dropped to near zero.
Bought a new Mac mini to properly tinker with claws over the weekend. The apple store person told me they are selling like hotcakes and everyone is confused :) I'm definitely a bit sus'd to run OpenClaw specifically - giving my private data/keys to 400K lines of vibe coded monster that is being actively attacked at scale is not very appealing at all. Already seeing reports of exposed instances, RCE vulnerabilities, supply chain poisoning, malicious or compromised skills in the registry, it feels like a complete wild west and a security nightmare. But I do love the concept and I think that just like LLM agents were a new layer on top of LLMs, Claws are now a new layer on top of LLM agents, taking the orchestration, scheduling, context, tool calls and a kind of persistence to a next level. Looking around, and given that the high level idea is clear, there are a lot of smaller Claws starting to pop out. For example, on a quick skim NanoClaw looks really interesting in that the core engine is ~4000 lines of code (fits into both my head and that of AI agents, so it feels manageable, auditable, flexible, etc.) and runs everything in containers by default. I also love their approach to configurability - it's not done via config files it's done via skills! For example, /add-telegram instructs your AI agent how to modify the actual code to integrate Telegram. I haven't come across this yet and it slightly blew my mind earlier today as a new, AI-enabled approach to preventing config mess and if-then-else monsters. Basically - the implied new meta is to write the most maximally forkable repo and then have skills that fork it into any desired more exotic configuration. Very cool. Anyway there are many others - e.g. nanobot, zeroclaw, ironclaw, picoclaw (lol @ prefixes). There are also cloud-hosted alternatives but tbh I don't love these because it feels much harder to tinker with. In particular, local setup allows easy connection to home automation gadgets on the local network. And I don't know, there is something aesthetically pleasing about there being a physical device 'possessed' by a little ghost of a personal digital house elf. Not 100% sure what my setup ends up looking like just yet but Claws are an awesome, exciting new layer of the AI stack.
113
298
71
3,477
606,757
Achievement unlocked: my breakfast café currently playing "Never Gonna Give You Up" on the last day of DEF CON.
2
5
510
#RSAC? @BSidesSF? @BSidesLV? Just existing in SF without any sort of conferencing activity or intent? #YBGardensCon is best con! Come change our minds!
1
7
915
Help crack Wonderland’s thorniest authentication problems with Alice & Bob. Submit to our @BSidesLV #PassWordsCon track #CFP today! bsideslv.org/cfp #BSidesLV
7
1
6
1,334