Gardner

3K posts

Gardner banner
Gardner

Gardner

@Gardner

Insatiably curious : Perpetually perplexed… Cofounder @MyUnicornAcct. ex @CUBE3AI Content Lead.

Radtown. CA, USA. Katılım Mart 2009
908 Takip Edilen911 Takipçiler
Balaji
Balaji@balajis·
I'm going to make some obvious points. (1) Blowing up all the oil infrastructure in the Middle East is an insane idea, and may well result in a global economic crash and humanitarian crisis unrivaled in the lives of those now living. We're talking about the price of everything everywhere rising, from food to gas, at a moment when inflation was already high. All of that will be laid at the feet of the authors of this war. (2) The antebellum status quo of Feb 27, 2026 was just not that bad, but we're unlikely to return to it. Expect indefinite, long-term, ongoing disruptions to everything out of the Middle East. (3) Also assume tech financing crashes for the indefinite future. The genius plan to get the Gulf states caught in the crossfire has incinerated much of the funding for LPs, for datacenters, and for IPOs. Anyone in tech who supported this war may soon learn the meaning of "force majeure" as funding gets yanked. (4) Many capital allocators will instead be allocating much further down Maslow's hierarchy of needs, towards useful basic things like food and energy. (5) It's fortunate that all those progressives yelled about the "climate crisis." Yes, their reasoning about timelines was wrong, and much of the money was wasted in graft, but the result was right: we all need energy independence from the Middle East, pronto. It's also fortunate that Elon and China autistically took climate seriously. Now they're going to need to ship a billion solar panels, electric vehicles, batteries, nuclear power plants, and the like to get everyone off oil, immediately. (6) It's not just an oil and gas problem, of course. It's also a fertilizer problem, and a chemical precursor problem. Maybe some new sources will come online at the new prices, but it takes time to dial stuff up, particularly at this scale, so shortages are almost a certainty. That said, China has actually scaled up coal-to-chemicals[a,c] (C2C), and there's also something more sci-fi called Power-to-X[b] which turns arbitrary power + water + air into hydrocarbons. But all of that will need to get accelerated. I have a background in chemical engineering so may start funding things in this area. (7) Ultimately, this war is going to result in tremendous blame for anyone associated with it. It's a no-win scenario to blow up this much infrastructure for so many people. Simply not worth it for whatever objective they thought they were going to attain. But unless you're actually in a position to stop the madness, the pragmatic thing to do is: scramble to mitigate the fallout to yourself, your business, and your people. [a]: reuters.com/business/energ… [b]: alfalaval.com/industries/ene… [c]: reuters.com/sustainability…
Balaji tweet media
English
692
2.1K
11.6K
3.2M
Gardner
Gardner@Gardner·
Critical trend to watch: When Hormuz is closed, global food insecurity rises. People don’t (yet) realize the interdependency of Gulf oil and the price of corn, wheat, soybeans, etc due to sulphur, urea, gas >> synthetic nitrogen >> basic Haber-Bosch fertilizer. Crops cycles don’t wait for geopolitics: “People understand that their cars need gasoline. They do not understand that their bread needs ammonia, that their rice needs urea, that their vegetables need phosphate processed with Gulf sulfur. The Haber-Bosch dependency is hidden in the soil, invisible to the consumer, and therefore absent from the strategic imagination of policymakers.”
Shanaka Anslem Perera ⚡@shanaka86

JUST IN: The Strait of Hormuz blocks the fertiliser from shipping. China just blocked it from being replaced. Beijing has instructed exporters to suspend overseas shipments of nitrogen and potassium fertiliser blends. Urea. NPK mixes. The molecules that American, Indian, Bangladeshi, and African farmers need to plant are now gated at two chokepoints simultaneously: a 21-mile waterway controlled by provincial commanders with sealed radio orders, and a government directive issued from Zhongnanhai that requires no radio at all. One third of global seaborne fertiliser trade transits Hormuz. China is the world’s largest fertiliser producer. When the strait closed and China suspended exports in the same month, the global food system lost its primary supply route and its primary alternative supplier at the same time. There is no third source at this scale. There is no backup to the backup. Urea has surged roughly 40 percent since the war began. CBOT March futures settled at 610.50. The peak at New Orleans touched $683. Those prices were set by the Hormuz blockade alone. China’s ban adds a second floor underneath them. Even if the strait reopened tomorrow, Chinese urea would not flow until Beijing lifts the directive. Even if Beijing lifted the directive, the strait would still need to reopen, insurance to normalise, and vessels to be available. The two gates operate independently. Both must open for the molecule to move. China’s logic is transparent. Hormuz disrupted global supply. Prices surged. Chinese domestic farmers face the same planting windows as everyone else. Beijing chose to protect its own agriculture by hoarding the molecule the rest of the world needs. This is the same country that is simultaneously drawing commercial crude reserves at a million barrels per day, running military exercises near Taiwan, receiving discounted Iranian oil through the permissioned strait, and restricting the phosphate exports it suspended months ago. Every decision serves one objective: China first. The rest of the world absorbs the shortage. The American farmer is now squeezed from two directions. The Gulf urea he used to buy cannot transit the strait. The Chinese urea that could have replaced it is embargoed by Beijing. Domestic US production covers roughly 75 percent of normal needs, but normal needs assumed Gulf and Chinese imports filling the gap. The gap is now unfillable on any timeline that matters for spring planting. USDA projects corn falling to 94 million acres. Soybeans rising to 85 million. The RFS mandate consumes 43 percent of a shrinking corn crop. The cattle herd sits at 86.2 million, a 75-year low. The protein cascade runs from corn to feed to meat to eggs to dairy to the grocery shelf. China’s ban did not create that cascade. The Hormuz blockade created it. China’s ban removed the last exit ramp. Oman crude at $154. Brent at $102. WTI at $93. Gold at $5,000. The Fed holding at 3.50 to 3.75 with PCE revised to 2.7. Trump telling Israel to stop hitting gas fields. Iran threatening to burn the Gulf to ashes. Four countries’ energy infrastructure offline. And now the world’s largest fertiliser producer has locked its warehouse and told every farmer on Earth that the key is in Beijing, not for sale, and not available until further notice. Two gates. One molecule. No alternative. The calendar closes in four weeks. open.substack.com/pub/shanakaans…

English
0
0
0
118
Gardner retweetledi
Unicorn.eth
Unicorn.eth@MyUnicornAcct·
🎉🎉The results are in for the $250 USDC Arbitrum Accounts Lottery (powered by Unicorn)! 🔍 Could it be you? Here is a little hint: The letter that the winner’s username ends with is the sound they'll surely make when they discover they've won... 😲 Reply with what letter you think it is! 💸 To the winner: An official notification email has been sent to the address used to create your Arbitrum Account. ✍️ Check your inbox as well as spam/promotions (just in case). We value your privacy and won’t reveal the winner without permission. 🔢The winner was selected via a random number generator and has 30 days to reply to our email to claim their $250 USDC prize... 🦄
GIF
English
5
6
10
479
Gardner
Gardner@Gardner·
@JJEnglert @Scobleizer @openclaw This post x comments are a super helpful. TY! Humans helping humans is the best thing to see. *AI w/the assist!
GIF
English
0
1
1
185
JJ Englert
JJ Englert@JJEnglert·
After a month of watching my fellow builders set up their @openclaw , I finally took the plunge this past week. Last night my agent ran overnight on a project we came up with together, and it was ready for review when I woke up this morning. It has its own GitHub account. Its own email. Its own Twitter. It runs 24/7 on an old MacBook Pro with the lid closed. And it has enough tools connected to actually do real work. But the magic moment wasn't the overnight build. It was something way simpler. I told it to message me at 7:30 AM with a daily plan. And it just did it. Figured out how to do it on its own. That "figure it out" mentality from an agent that actually has access to tools and a computer felt different than anything I've used before. For the first time, it felt like something capable of doing real stuff. Not a chatbot. Something else. And I'm just scratching the surface. It took me about 8 hours to get here. I want to help you get there faster. Here's everything I learned along the way, plus a prompt you can copy and paste into your OpenClaw once you're set up. Getting started I set it up on an old MacBook Pro. Dedicated device. You want this running independently so it does not have access to your data. Having a virtual device on @Hetzner_Online is also good. Installation took about an hour. Then I spent the next two hours having Codex tighten the security before training it anymore. Sandbox commands. Whitelist only what you need. Do this first. Then I hit a wall. It felt like a chatbot. Limited permissions. Couldn't access tools. Couldn't browse. It took another 2-4 hours to get terminal access and Playwright browser control working. I used Caffeinate in terminal to keep it running with the lid closed. I set up dedicated accounts. GitHub, email, Twitter. Give it its own identity so it can operate independently. Training it - Keep your Heartbeat.md lean. It gets read every session and burns tokens if it's bloated. Identity, active projects, key preferences. That's the hot cache. - Install a memory plugin early (ClawVault, Supermemory, or Lumen Notes). Persistent memory across sessions is what takes it from chatbot to something that knows your work. - Build skill files for recurring output. Emails, social posts, documents. Each gets its own file with format, voice rules, examples, and a checklist. It follows these like playbooks. - Define your agent's persona and tone. I built out voice files based on what I'd already created in Cowork and the output quality jumped immediately. - Point it at your existing repos. It can pull context from anything you give it access to. If you've already built structure somewhere, don't rebuild it. Reference it. Best advice I got from experienced OpenClaw builders Force plan before execution. Make it tell you what it's going to do before it does it. Saved me from multiple rabbit holes. Back up your repo to GitHub every night. Your config files, skills, and memory directory are the training. Lose them and you're starting over. Think in workflows, not one-off tasks. This compounds fast. I also applied the same repo structure from my Cowork setup guide: Your-Workspace/ ├── Heartbeat.md ├── Brain/ │ ├── about-me.md │ ├── brand-voice.md │ └── working-preferences.md ├── Skills/ ├── Projects/ └── Memory/ I'm about a week in. Still early. But I can see where this is going and I wish I'd started sooner. If you're just getting started, here's the prompt I'd paste in on day one to fast-track the whole setup: -- You are going to help me set up my workspace so that every future session starts with full context about who I am, what I do, and how I work. We're building the files and structure that make you useful from the first message. Interview me in phases. Ask questions, then build files based on my answers. Don't rush. Don't assume. Ask before you build. Phase 0: Foundation Check if I have a Heartbeat.md file. If not, create one. Keep it lean. Recommend a memory plugin for persistent context. Ask what tools I use daily and help me connect them. Recommend sandboxing and whitelisting commands from the start. Phase 1: Identity Interview me to create Brain/about-me.md. Ask about my work, background, what I'm building, and positioning. Show the file. Get approval before moving on. Phase 2: Voice Interview me about how I want my agent to sound. Phrases I use. Phrases I'd never use. Tone shifts by context. Create Brain/brand-voice.md. Get approval. Phase 3: Working Preferences What I want help with. Communication style. Workflow pain points. Output preferences. Create Brain/working-preferences.md. Get approval. Phase 4: Skill Files For each type of recurring output, create a skill file in its own folder under Skills/. Each gets: format, voice rules, examples, quality checklist. Ask what I create most often before building. Phase 5: Active Projects Current projects, goals, deadlines. Individual files in Projects/. Phase 6: Memory System Update Heartbeat.md with a summary of everything we built. Create Memory/ directory with subfolders for people, projects, context. Add glossary.md. Phase 7: Reference Sources Any existing repos, docs, or files I want referenced. Organize access. Rules: One phase at a time. Show each file before saving. If unsure, ask. Concise files. Lowercase, hyphens, .md format. Start with Phase 0.
JJ Englert tweet media
English
83
141
1.8K
527.2K
Aaron Erickson
Aaron Erickson@AaronErickson·
@lukOlejnik Seniors could push back on bad changes. They do in my org, where we code entirely using agents. Ability to just vibe code a high blast radius change that breaks things is a system problem, not an AI one.
English
27
3
211
94.6K
Lukasz Olejnik
Lukasz Olejnik@lukOlejnik·
Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking? The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China).
Lukasz Olejnik tweet media
English
975
3.3K
19K
29.8M
Gardner
Gardner@Gardner·
@Cube3AI Congrats on solid style and core mission 🫡🛡️👀
English
0
0
0
2
CUBE AI
CUBE AI@Cube3AI·
CUBE3 is now CUBE AI. The Conversational Crime Intelligence Platform. Network-level intelligence on active criminal operations - at the scale and speed required to make decisions, not just assess risk. New name. Elevated design. Same mission. The threat landscape keeps evolving. So do we. cube3.ai #CUBEAI #FraudPrevention
English
1
0
3
100
Robert Scoble
Robert Scoble@Scobleizer·
What does @OpenAI GPT 5.4 (just released this morning) mean for developers? You talked about it. My AI agents read it. Wrote a report. Sent it over to @NotebookLM. Which made this video. Using the new cinematic quality released yesterday. This was all built with your posts from X. Damn, I wish I had this decades ago. Do you all get how insane this is for learning about new things?
English
48
38
324
27.2K
Gardner
Gardner@Gardner·
pizza ordering agent demo from @snack_man at @Pizza_DAO was fav demo at ETHDenver 🤣 Bot: “$6900 is still extremely high…that’s over $140 per pizza….” Snax: “We have really fancy pizzas.”
English
1
4
17
3.3K
Gardner retweetledi
BridgetUnicorn @ETHDenver
BridgetUnicorn @ETHDenver@Bridget_Unicorn·
@beeple Hello from the other side ... I must have called 1000 times ... To tell you to... 🦄🩷🦄
English
2
3
8
660
Gardner
Gardner@Gardner·
@beeple Bad take Beeps. It’s high signal less noise this year and super vibrant set up in new venue.
Gardner tweet media
English
1
0
8
852
beeple
beeple@beeple·
ETH DENVER 2026
beeple tweet media
Dansk
576
544
6.9K
524.2K
J O H N P A L L Ξ R | pallΞr.Ξth (🦬,🦄)
Has to be AI!! lol. I’m amused how internet trolls so so so want @EthereumDenver to fail. Pure copium. Thanks for the free advertising tho! A bunch of people showed up today expecting desolation and found vibrancy. I won’t be tagging FUDDERs as they’re literally not relevant to do so. The builders here ARE relevant. I’ll be focusing my attention there.
17 years of song a day@songadaymann

🎵 THERE'S NOBODY AT ETH DENVER🎵 bid on the 1/1: songaday.world/6259

English
9
1
45
4.7K
Gardner
Gardner@Gardner·
Wow… ETHDENVER set up is gonna be dooope this year!! Super excited.
English
0
0
3
50