@bweisdevi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
Founder of Springbird | Ex-Rippler, Googler, Cisco Meraki | I build incredible experiences
Manhattan, NY
Joined July 2024
- Tweets41
- Following153
- Followers26
- Likes97
Ben Weis retweeted
In case this is useful for anyone else, I created this tool to inspect my @EffectTS_ projects today.
npmjs.com/package/effect-ins…
One of my favorite PRs that I’ve put up in the past few months was a one shot migration from SST to @alchemy_run
Complete IaC swap in <6 hours.
Had an awesome time with the rest of the Springbird team! Thanks for hosting an awesome event!
The NYC @EffectTS_ community was out in force tonight!
Huge shout out to @zshrm and Hyper for hosting us in their amazing office!
Ben Weis retweeted
The NYC @EffectTS_ community was out in force tonight!
Huge shout out to @zshrm and Hyper for hosting us in their amazing office!
Ben Weis retweeted
V8 isolates & QuickJS is *not* secure by default
Seeing a lot of mistakes like:
- Running in the same process as your backend → one V8 CVE reads your API keys
- Exposing 𝙳𝚊𝚝𝚎.𝚗𝚘𝚠() → Spectre
- Removing 𝙳𝚊𝚝𝚎.𝚗𝚘𝚠() but keeping network → the network is a clock → Spectre x2
- Guest 𝚏𝚎𝚝𝚌𝚑() → SSRF to unauthed internal services
- Not whitelisting egress → botnets
- Traversal & symlink escapes in filesystem API
- Timeouts that can't actually kill 𝚠𝚑𝚒𝚕𝚎(𝚝𝚛𝚞𝚎){}
- Bad OOM guards → try 𝚗𝚎𝚠 𝙰𝚛𝚛𝚊𝚢(𝟷𝚎𝟿)
We put a lot of time into security with agentOS & Secure Exec
(WebAssembly-based Linux sandbox)
Instead, we follow the Cloudflare Workers & Chromium model.
Some functionality we put in place:
- Run isolates in a separate sidecar process
- Spectre timing mitigations
- Virtual operating system → full Linux that never touches the host
- Event pump that can preempt a hot loop
- OOM contained to VM, bounded limits, & monitoring for everything
- Deny-by-default egress, explicit allowlist
- (Soon) jail the sidecar process
Ben Weis retweeted
How long til this is the second best Postgres full-text search index, behind only TIN?
I've never written a Postgres extension. I know just enough Rust to be dangerous.
Anyway, here's Stannum, a full-text search extension designed to be TINQL-compatible.
Honest AI slop, with tests.
github.com/TeamSpringbird/st…
1/4 🧵
I've never written a Postgres extension. I know just enough Rust to be dangerous.
Anyway, here's Stannum, a full-text search extension designed to be TINQL-compatible.
Honest AI slop, with tests.
github.com/TeamSpringbird/st…
1/4 🧵
Thanks @PlanetScale, and @p_reynolds for Lead and the writeups that got this going.
Stannum is open source, very alpha, and I'll keep working on it. Contributions, demanding workloads, and scrutiny of the benchmarks are welcome.
4/4
Ben Weis retweeted
Do I know anyone who knows anyone who knows someone who works at @npmjs ? It's an emergency!
Replying to @rankintweets
Awesome! Took a crack at rebuilding this on Temporal, without the DSL. The model writes plain JavaScript. It runs in a sandbox with five functions available to it, and the script is rerun from the top every time one of those calls finishes. Calls that already happened return their saved result; the first one that hasn't is where the run waits.
All of it is one workflow on effect-temporal.com/. Sleep is a Temporal timer, approval waits on a signal, a tool call is an activity.
Still a prototype, but plain JS has something going for it.
Ben Weis retweeted
The shit we get before GTA VI
We’re sharing a solution to the Navier-Stokes Millennium Prize Problem, one of the deepest problems at the frontier of mathematics.
The proof was produced by a group of agents, using an OpenAI next-generation model significantly more capable than GPT-6 Astra.
The problem concerns whether the description of smooth three-dimensional fluid motion modeled by the Navier-Stokes equations can break down. It has remained unresolved for roughly 90 years.
Ben Weis retweeted
In the next version of @EffectTS_ , there will be a 2x improvement in memory usage for the core apis. And a 20% improvement in minor GCs.
I'm super excited for @EffectTS_ NYC Meetup #2 luma.com/2e0qaazh
See you all there!
You can now run plain @EffectTS_ workflows on @temporalio: effect-temporal 0.2.0 hosts Workflow.toLayer registrations behind one workflowBundle default export. same workflow code runs on effect cluster or Temporal, you just swap a layer.
thanks @MattiaManzati for the nudge, you were right
effect-temporal.com
Thanks for the push — yours shipping is why ours is a package now instead of a folder in our monorepo.
effect-mq → jobs, bring your own Postgres/Redis.
effect-temporal → durable workflows, Temporal underneath.
MIT too. Pick your weight class.
effect-temporal.com
Our CTO @rankintweets side-quested a background jobs library for Effect. Borne out of what we've really wanted here at @warpdotco for the past year.
Now it's open source.
Schema-typed payloads. Swappable storage (Postgres/Redis/memory). At-least-once with durable retries that live in the store, never in worker memory.
Under MIT license. effect-mq.com
Enjoy.
We've run Effect workflows on Temporal internally at Springbird for a while and never published it. @rankintweets shipping effect-mq was the nudge — it's a real package now.
Multi-day sleeps, signals, human approvals. MIT.
effect-temporal.com