emm jay (glowie)

Day 6 of diving deeper into cybersecurity Monitoring & AI watchers (telemetry, records of what your system did, watched by rules and by AI, so you can catch an attack while it is happening) You cannot stop what you cannot see. And seeing it late is almost as bad as not seeing it at all. An attacker who has been in your system for weeks has already had time to learn, move, and take what they want. A watcher is not magic. It is telemetry, plus triage, plus a real response. Here is what goes unnoticed, and how to fight each one: 1. Blind: no logs, no view. If you do not record logins, code changes, new admins, large exports, and key use from new places, you will not know an attack happened until someone else tells you. Fight it with telemetry. Telemetry just means records of what happened. Log what matters, keep those logs somewhere the attacker cannot delete them, and make sure you can actually read them later. 2. Noisy: real signal buried. If everything alerts, nothing alerts. People start ignoring alerts, and the real one gets missed in the noise. Fight it with triage. Triage means sorting what matters from what does not. This is where AI helps best, as a sorter, not as a decider. AI can summarize a flood of logs and point to the odd ones, and a human or a rule decides what to do about them. 3. Late: found weeks later. A slow discovery gives the attacker time to finish the chain from Day 1. Fight it with fast alerts. Alert in minutes, not weeks, on the critical things: code or config changes to auth, payments, or signing, a new admin, a failed login spike, a large export, a key used from a new place. Those are the things worth waking up for. 4. No context: alert, but who, what? An alert that just says "something odd happened" does not help you act. Fight it with rich context. Every alert should say who, what, where, and when, in plain language. Who logged in, what changed, from where, and what it touched. Without that, you waste the fast part investigating. 5. No action: seen, but not stopped. This was the Hugging Face lesson in July 2026. Their watcher was LLM-based anomaly detection, LLM triage over security telemetry to separate real signals from daily noise, and it did flag the intrusion. But a watcher is detection, not prevention. The agents had already abused remote code and template paths, harvested credentials, and moved laterally before it was contained. Fight it with policy action. Behind the watcher, have a rule or a human who can pause, revoke, roll back, and rebuild. An alert should trigger a response, not just a notification. A watcher that only watches is not enough. It has to see, explain, and trigger a real response.

I sometimes wish I could be like my favorite X accs And then I proceed to not be like them on my very next post…

I don’t mean to get political here but it appears as tho the Dems got the memo to all talk about big bad AI

Has AI made society better or worse?

“Fill this room with what you know about me” AI memory doesn’t seem to be that bad nowadays 😬 Let’s see yours 👇🏻

Day 7 of diving deeper into cybersecurity Incident response & recovery (what you do when a breach happens, in the first minutes and hours, and how you get back to safe) No defense is perfect. That was the whole point of Day 1. So the question is not just how to stop an attack, it is what you do when one gets through anyway. Incident response is the plan for that moment. Recovery is getting back to a clean, safe system, and fixing the hole so it does not happen the same way again. Here is what goes wrong in a breach, and how to fight each one: 1. No plan: panic, improvise. In a breach, you do not have time to figure out who does what, where the kill switch is, or who to call. Fight it with a playbook ready. Write the steps down before you need them, and practice them. Who pauses what, who revokes what, who tells users, and in what order. A plan you have practiced is calm. A plan you are inventing is not. 2. Still live: keys keep working. If the attacker has a key or a session, they can keep coming back while you investigate. Fight it with revoke + rotate. Kill keys and sessions first, then rotate them. That is the fastest way to cut off access, and it matters more than understanding everything first. 3. Dirty system: attacker still inside. A compromised machine cannot be trusted just because you cleaned one file. The attacker may have left another way in. Fight it with rebuild clean. Build fresh machines from a known clean image, patch the path they used, and do not reuse a system you cannot prove is clean. Hugging Face did this in July 2026, rebuilding affected nodes after their breach, not just cleaning them. 4. Data lost: no clean restore. If your only backups are on the same system that was attacked, they can be deleted or encrypted too. Fight it with restore backup. Keep backups offline or separate, test restoring from them before you need them, and know how long a restore actually takes. A backup you have never tested is a hope, not a plan. 5. No lessons: same hole, again. If you fix the symptom and move on, the next attacker will use the same hole. Fight it with learn + fix. After it is contained, write down what happened, what the root cause was, and what changes. Close the root cause, improve the alerts from Day 6, and update the playbook. The race is minutes, not days. Stop it, clean it, restore it, then fix why it worked.

Silly me, I used to manually type and format my recipes I cannot believe it

Half the calories people eat come from grass Here’s one seed’s whole life in 60 seconds: it lands, roots, breaks into the light, flowers in the wind, ripens, and drops the next seed. Rendered in Blender. Voiceover by ElevenLabs

Ohhh I’m late to this but I neeeeed one #RTXON

I really need @Da7_Tech to do an AMA already

I almost wondered if Tibo was moving to Claude

PACE THE QUANTUM FRONTIER

Anyway it’s been a long day and I’ve missed all my fave X-er tech-ers How’s everyone?

Omg I just realized I have access to Claude Duet Do we all or am I spesh?

Instead of individuals giving up their little bits of RAM, why don’t we require it of big companies with terrible AI like Apple?

Who is your favorite person in the AI world right now?

Plot twist: This is actually @poteto Now being a double agent for both OpenAI and xAI