Maxi

@Baconbrix @SpaceXAI congrats Evan! thanks for everything you’ve done for the react native community while at @expo 🫡

Honored to announce that I’ve joined @SpaceXAI! 🚀 I believe this team can do for intelligence what SpaceX did for rockets and the internet, I'm grateful and humbled to contribute to it. If you have feedback on Grok, Grok Build, or the APIs; I'm all ears!

@hirbod @zeeg you will 100% get annoyed, but it'll all be worth it in the end

@zeeg Hm. I think @maxast might have some good points here

should I rewrite my project in Effect or will i just get annoyed

@hirbod @expo Ohh, nice work Hirbod 🔥

Had so much fun redesigning @Expo’s new homepage. Nico, sadly not on X, is a goated designer. Loved working on the Liquid Metal shader. Proud to be part of this amazing team and also to help redesign many parts of the EAS dashboard (still WIP). So many great things to come.

@hirbod It’s so satisfying to watch the number go down right

From 32°C to 28°C in ~30min. I am so back.

@felippewick Herzlichen Glückwunsch! 🫶

Personal Update: I gained 0 MRR this month but added a new member to the team

@peterpme If you’re not using relay, you’re not using graphql correctly

GraphQL Relay, one of the most sophisticated data fetching libraries ever built completely overshadowed by "easy" graphql clients that fk'd it all up

@SarthiB7 st oberholz?

Cafe hopping is gud ✨👀 Planning to work from cafes more. Lmk if anyone wanna join in.

@0xJunebox LFG @Jon_hivy

Huge congrats to the winners of the LI.​FI Frontier track at Superteam Germany 👏 This cohort drew 15 project submissions - teams building real cross-chain integrations powered by LI.​FI across AI agents, yield infrastructure, and consumer payments. The bar was genuinely high. Full winners below! @colosseum @SuperteamDE

@SarthiB7 nice, been wanting to try pi. When and why do you decide to use pi instead of codex?

@maxast I use codex and pi mostly. Opencode was to experiment running custom NVIDIA models. Or else my top use is Pi and codex

Keyboardmaxxing (testing/learning something) IDE ❌ Terminal ✅ ps. i still use cursor IDE btw :)

@SarthiB7 Next step: dropping cursor in favor of neovim 😅

@SarthiB7 Same setup here! Although I stopped using opencode and only use codex these days

@anubis2406 @llestutSVWeh Weil ich da mehrere sender auf einmal habe. Und Seiten als Favoriten speichern kann

@maxast @llestutSVWeh warum eine App bauen? Hat die Ard schon am Start. ard-text.de/mobil/100

Ich weiß noch wie ich da als kind 90 min draufgeglotzt habe kannste mit der heutigen tiktok generation nicht mehr machen

@tasko_fyi Cool combination of new tech, looking forward to trying it out!

Tasko Demo is live. We’re building outcome-based payments for AI work: Businesses can post confidential tasks, lock funds in escrow, receive deliverables, and release payment only after the result is verified. Live devnet demo: tasko.fyi 1/3

@kadikraman @expo That’s perfect, thanks a lot @kadikraman!

@maxast @expo Yes! We have an example of how you could implement this actually. Search this repo for "critical" github.com/expo/UpdatesAP…

react native friends, quick Q: Is there a way to distinguish OTA updates based on some kind of custom metadata in @expo-updates? We currently check for and install updates every 30min (see screenshot). The register function is called in a root-level useEffect. We'd like to change this setup, so that urgent updates get downloaded and installed instantly (via a sheet and a button that users have to press) while non-urgent updates can get downloaded and installed in the background, the default way in expo-updates. How would you build this?

@SarthiB7 @SuperteamDE gm!

Gm from buildstation

@o_kwasniewski looks much faster than maestro!

this is what AUTOMATED UI testing looks like

@FredKSchott This looks great! I want to build a control plane UI for my ralph loops and it looks likei just found the perfect backend for it!

Introducing Flue — The First Agent Harness Framework Flue is a TypeScript framework for building the next generation of agents, designed around a built-in agent harness. Flue is like Claude Code, but 100% headless and programmable. There's no baked in assumption like requiring a human operator to function. No TUI. No GUI. Just TypeScript. But using Flue feels like using Claude Code. The agents you build act autonomously to solve problems and complete tasks. They require very little code to run. Most of the "logic" lives in Markdown: skills and context and AGENTS.md. Flue is like Astro or Next.js for agents (not surprising, given my background 🙃). It's not another AI SDK. It's a proper runtime-agnostic framework. Write once, build, and deploy your agents anywhere (Node.js, Cloudflare, GitHub Actions, GitLab CI/CD, etc). We originally built Flue to power AI workflows inside of the Astro GitHub repo. But then @_bgiori got his hands on it, and we realized that every agent needs a framework like Flue, not just us. Check it out! It's early, but I'm curious to hear what people think. Are agents ready for their library -> framework moment?

@_lhermann What do you use as the source for German laws? gesetze-im-internet.de, dejure, etc?

I added a German Law tool to my home-brew OpenClaw alternative. Now it can look up any regulation and help me win against German paperwork ⚔️