Igor Strmecki @strma

in light of the AI cyberattack mayhem going on right now, it's a good time to reshare Karapthy's Digital Hygiene guide probably the most important thing you can read this week: > use a password manager for every account > set up physical security keys so attackers can't log in > enable face id and fingerprint everywhere > randomize your security question answers > encrypt your hard drive > get rid of unnecessary smart home devices > switch to signal for private messaging > use brave instead of chrome > switch to brave search instead of google > mint virtual credit cards for every purchase > get a virtual mailing address > never click links inside emails > use a vpn on public wifi > block ads and trackers at the dns level > install a network monitor to see which apps are spying on you

Ole Lehmann @itsolelehmann

7 months ago

x.com/i/article/2041…

16 117 782 821K 3K

Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.

Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.

Ako znate nekog normalnog (znam, puno ocekujem) da trazi stan na istoku Zg - mirna ulica kod Poljanica, parkirno mjesto, potpuno namjesten i opremljen, samo ceka stanare da donesu svoje kofere. Vesmasina, sudjerica, klima, frizider, skrinja, internet 40mbit... Na duzi rok.

keyboard_arrow_left Previous keyboard_arrow_right Next

Terrassa. Barcelona. Zagreb. Leipzig. Barcelona. Nueva York. ❤️🌎

Fable 5 flips to pay‑per‑use in 48 hours. Burn the remaining runway to make sure you don’t actually leave anything behind. The play: have Fable comb your repo and draft a complete skills library before the timer hits zero. Frame it as a retiring principal engineer doing a final handoff to the team, and it snaps into a totally different gear. On the other side you get 10–16 skill files—debugging runbooks, change policies, the painful failure tales that ate days. Every instinctive judgment it would’ve made silently is now documented and reusable by Opus and Sonnet for pennies. Single pass. About 30% of your weekly budget. Value keeps compounding even after it’s locked behind credits.

im releasing all my agent skills to the public this is hundreds of hours of trial & error every single global .agents skill i have go grab it. it's free.

Kimi K2.7 Code is fucking incredible the tokens per second on such a smart model are just... wow

These Claude prompts have completely changed my life. I've tested dozens of mega prompts inside Claude, and these 6 are the best. Coding prompts, productivity prompts & more. Full resources included - you'll want to save this:

AI Edge @aiedge_

4 months ago

x.com/i/article/2057…

5 26 198 80K 558

@nevenvorkapic Ma moze i prime na film :), Konica ili Olympus. Kolko para?

Kako nekome može biti dosadno, nikad mi neće biti jasno.

Danas je Dan planeta Zemlje - to je naš dom, naša odgovornost i naša budućnost. Svaka mala promjena koju napravimo danas može imati veliki utjecaj sutra. Zemlja ne pripada nama, mi pripadamo njoj. Čuvajmo je zajedno – ne samo danas, nego svaki dan. #DanPlanetaZemlje #zaorah

@ai_rohitt Course thx

@vishisinghal_ Pls Bible thx 👍

LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.

One frame. One moment. Everything after this is momentum, trajectory, physics. But right here, right now, a rocket is deciding to leave the Earth. The solid boosters ignite and hold down claps release. This is the last instant four astronauts are still on Earth but once those clamps release when the booster fire, there’s no going back, only forward. 📸 credit: me for @SuperclusterHQ - Artemis II liftoff | Pad 39B, Kennedy Space Center | April 1, 2026

@itsolelehmann Cowork

Healthcare professions such as doctors, nurses, therapists, and counselors continue to rank among the most automation-resistant. They involve unpredictable human needs, emotional complexity, and ethical decision-making, which are areas where algorithms still lag. Find out more about the other high-paying jobs. Read more: forbes.com/sites/shodewan…

This victory not only adds to our personal achievements but also marks a historic moment for Croatian sports. We’re proud to become the first Croatian athletes to win four Olympic medals since our country’s independence 🇭🇷 Thank you to everyone for your unwavering support!

keyboard_arrow_left Previous keyboard_arrow_right Next