ᐸAndyParsons/ᐳ

@dillon_mulroy born to build B2B SaaS

born to deliver value to shareholders

@irvinebroque @charl_dot_dev This is how i find out this PR finally got merged, time to go test some runtime Astro data caching, and will i prefer this to snippets github.com/cloudflare/clo…

@charl_dot_dev is this a skew protection subtweet?

PM: Cloudflare released Workers caching so we can save costs! Me: Our users don’t know how to hard reload

@Cloudflare I think berkshirehathaway.com has been like that since 1996

What’s the oldest domain name you own that you still haven’t built anything on? #CloudflareChat

@styfle I saw @DrizzleORM hit this recently, so glad that eventually got help, hopefully their struggle will help the platform improve x.com/andrii_sherman…

Not many npm packages run into this problem, but there is a maximum metadata size for all versions of a package. If you exceed it, you can't publish that pkg anymore 😰 Since we publish next@canary daily, we don't wan to hit this ceiling. github.com/vercel/next.js…

@MatthewBerman @useblacksmith tends to be faster and cheaper running GitHub actions than GitHub itself

Currently limited by how fast I can deploy. Multiple agents deploying at the same time breaks my GitHub workflow. What’s the best way to do this?

@zerocipherz @roerohan @kristianfreeman @CloudflareDev The API routes they list in their agent skills repo may be what you want #L201-L213" target="_blank" rel="nofollow noopener">github.com/cloudflare/ski…

@roerohan @kristianfreeman @CloudflareDev This is helpful thanks but for my use case I really need to understand how to fetch these flags using a REST API or some kind of wrangler command. Looking forward to seeing it when it’s ready! Thank you

cloudflare now has a built-in feature flag service 🏁 flagship enters public beta today, and you can integrate it into your workers apps already deployed on @CloudflareDev, or deploy a worker in front of your app to do feature flipping and more w/o any additional config (read on!) there's a simple binding api (env.FLAGS w/ <10 methods, easy for your agents to pick up): env.FLAGS.getBooleanValue - return basic boolean values, like "is this flag set or not?" but you can also do some funky stuff like storing objects env.FLAGS.getObjectValue - return a full JSON object. you can store full configurations and flip per-user or org. neat! flagship is also openfeature-compatible. the cloudflare/flagship npm package has full support and interoperability with openfeature's sdk. so you can easily swap in flagship from your other providers and trial it on the setting of flags side - support for booleans, strings, numbers, and json and for targeting, you can use operators (things like "user_id is equal to xyz") or you can do percentage rollouts. all available in the dashboard. the dashboard is also quite powerful - you can create flags from the beautiful ui, see where your app is bound (across multiple workers, even!) and there's full analytics. knocked it out of the park the last thing i'll mention that i think is quite compelling and unique about workers and flagship is something we've talked a lot about in workers/cf land - i don't have a great name for it so i'll call it "originless" behavior. you can do a "v2-enabled" feature flag and make a fetch request to a totally different host, do URL rewrites etc without any changes to your actual application. eg `isflagEnabled ? fetch(newUrl) : fetch(origin)` - since the worker runs _in front_ of your app, you can do all sorts of behavior w/o ever needing to talk to your origin quite excited about this release and looking forward to playing w/ it. more on flagship in our changelog: developers.cloudflare.com/changelog/post…

@davis7 Nice. Do you think you'll be in the top 1% in the US according to Cloudflare? radar.cloudflare.com/speedtest

It's so overkill but I love it so much

@dok2001 @thomasgauvin Workers caching (looks like it may be soon though github.com/cloudflare/clo…)

What are we missing?

@theo Yeah, it certainly feels like a "No, but we don't want the bad optics" as if avoiding the issue is any better for PR.

Not gonna lie, it's kind of crazy that we still have no idea if shipping this would get Claude Code users banned. Having shitty policies is bad enough. Refusing to clarify them is absurd.

@threepointone Message recieved

@andparsons let it sync in

Pull based UIs are dead. You heard it here first.

@elithrar There’s a project that Spokenly and Slipbox utilise, they’re in the showcase section. I’ve used both of these on mobile and am really happy with the concept of a free unlimited local voice to text model that takes advantage of the Apple Neural Engine github.com/FluidInference…

what are your favorite voice note-taking apps? must be device local for the speech-to-text + transcription. iCloud sync OK. basic search across transcripts.

@mattpocockuk Maybe, sounds like you're in two minds about it

Shit I might have become one of those "second brain" people

@ZachWarunek @ancientjames?si=MIZT9kiU1duQ_e99" target="_blank" rel="nofollow noopener">youtube.com/@ancientjames?…

@ZachWarunek Thought this was a cool approach youtu.be/o76U0JPrMFk?si…

Who will be the first to run Doom on a Lego brick?

@_georgemoller I hadn’t considered this, this is very relevant to my interests Thanks man

❌ Conditional rendering loses form state in React. ✅ React 19's Activity API preserves it. e.g. Switch between steps → your data stays. Effects cleanup automatically → no wasted resources.

@kitlangton @dillon_mulroy Oh is this the new course, I feel educated

@dillon_mulroy I'm sorry I'm sorry wrong link 🤡👇👇👇👇👇👇👇👇👇👇👇👇👇🤡 👉👉 cube.kitlangton.com 👈👈 🤡👆👆👆👆👆👆👆👆👆👆👆👆👆🤡

introducing cf-workflow-rollback a library for saga-like rollbacks and compensating actions for your durable workflows npm i cf-workflow-rollback

@imax153 @EffectTS_ Damn, I wish I was

Like I said before, you all are NOT READY for @EffectTS_ Schema v4

@theo The secret's out... x.com/theo/status/16…

Theo, well known Rust zealot

@kitlangton Type based magic, you have invoked the wizard 🧙‍♂️

presenting 𝚍𝚘𝚌𝚝𝚘𝚛-𝚎𝚏𝚏𝚎𝚌𝚝