My wife runs a tiny kids’ crafts YouTube side hustle with almost no income. She’s facing legal action over a trademark. She did what was asked, but missed some old content. Now both sides are paying lawyers over something one more email could have solved peacefully. Sad, really.
Summer holidays have come to an end. ☀️
A great time to slow down, be with family, recharge, reflect… and, of course, keep learning.
As always. Stay hungry. Hack the Planet!
Yesterday was incredible! 🌌 We visited NASA’s telescope deployment in Villalibado, Burgos, preparing to observe the total solar eclipse. And at night, we were treated to a spectacular dark sky for watching the Perseids. ☄️✨
Found a couple of interesting repos that let you leverage your existing OpenAI Plus/Pro account and access it locally via an API. Handy for prototyping apps without spending extra money.
https://t.co/4QLt3ZKqMn
https://t.co/9n8Pxhs2iY
An Anthropic engineer shared the exact system they use as a second brain.
Three folders. One file. One evening to build.
Most people use Claude the same way every day. Open a new tab. Rebuild context. Get an answer. Close the tab. Tomorrow it remembers nothing. You are still the one holding all the context. You are still the one resetting.
This architecture solves that problem.
The system is built around three folders and one file.
raw/ holds everything unstructured. Articles, transcripts, PDFs, voice memos, screenshots. Drop it in and never touch it again. Immutable ground truth.
wiki/ is where Claude converts everything in raw into structured, linked, cross-referenced knowledge. Clean. Organized. This is the folder Claude actually thinks from. The human reads it. The model writes it.
output/ is where finished work lands. Reports, posts, documents, presentations. Everything Claude builds using the wiki as its source.
At the center is CLAUDE.md. Not a prompt, but a persistent layer of identity, preferences, goals, and project context. Claude reads it before every session. You never explain yourself again.
Five automations run the system.
Ingest captures and extracts new sources into the wiki. Write retrieves context and drafts outputs. Manage links decisions to context. Review summarizes and updates. Maintain prunes and improves connections.
Every session adds to the system. Every source makes the wiki smarter. The returns compound over time.
One month in, context stops disappearing. Three months in, the vault surfaces ideas you forgot you had. Six months in, the gap between compounding and resetting becomes impossible to ignore.
Build once. Maintain daily. Let it compound.
Bookmark this.
A workmate recommended this skill to me, and I’ve been using it for a week. I have to say, it’s amazing for staying up to date on any topic you’re interested in:
https://t.co/QuP7GmCu7M
North Korean intelligence agents built an entire fake company to compromise one JavaScript developer. And it worked.
UNC1069 didn't hack Axios. They befriended its maintainer. They cloned a real company founder's identity, built a branded Slack workspace with fake employee profiles and LinkedIn post channels, then scheduled a Microsoft Teams call with what appeared to be a full team. During the call, a fake error message said his system needed an update. He installed it. That update was the RAT.
From one developer's laptop, they had everything: npm credentials, publishing access, the keys to a package installed in 80% of cloud environments. Axios gets 100 million downloads per week. The attackers published two poisoned versions at 12:21 AM UTC on a Sunday night, tagging both the latest and legacy branches within 39 minutes. The malicious dependency had been pre-staged 18 hours earlier with a clean decoy version to build registry history. Three separate RAT payloads were pre-built for macOS, Windows, and Linux. The malware self-deleted after execution to erase forensic evidence.
The poisoned versions were live for about three hours before npm pulled them. Huntress observed 135 endpoints across all operating systems calling the attacker's command-and-control server during that window. Wiz found the malicious versions in roughly 3% of environments scanned. Every affected machine needs full credential rotation: npm tokens, AWS keys, SSH keys, CI/CD secrets, everything in .env files.
The part that keeps getting worse: this isn't isolated. The same threat cluster compromised Trivy (a security scanner), KICS, LiteLLM, and multiple GitHub Actions in the two weeks before Axios. Google estimates hundreds of thousands of stolen secrets are now circulating from these combined attacks. The maintainer had 2FA enabled. He said himself: "I have 2FA/MFA on practically everything." The exact method of token compromise is still undetermined.
One person. One fake Teams call. 100 million weekly downloads weaponized in under three hours. The npm ecosystem runs on mass trust in individual maintainers who volunteer their time, and North Korean intelligence now has a repeatable playbook for turning that trust into a delivery mechanism.
Today I received and set up a @Starlink kit with the roaming plan. I have to say that I'm really impressed by the speed, latency and stability of the service.
Getting an average of:
⬇️250 Mbps ⬆️35 Mbps 🕔 30 ms latency
Really good job, Starlink Team!
Cambia el alcohol por agua.
Cambia Netflix por podcasts.
Cambia las quejas por gratitud.
Cambia gastar dinero por invertir.
Cambia trasnochar por madrugar.
Cambia influencers por creadores.
Cambia el sobrepensar por acción.
Cambia amigos tóxicos por mentores.
Decompiling and reverse engineering a Godot game is a trivial task. If you're looking to increase the difficulty of this process, check out this awesome guide which provides useful tips to protect your project:
https://t.co/jJJHPxRC7O
#GodotEngine