Geoff Goodman

Here's a demo of two aspects of MCP Auth. 1. Authenticating to an MCP Server in coordination with the MCP Host (VS Code Insiders). 2. Authenticating to a downstream service (Confluence) on demand for a tool, `confluence_search`. The MCP Host provides (1) but is oblivious to (2).

@superhackers.bsky.social what's up with the repeated likes on the same posts over time?

Go Habs Go!!

Society at large would benefit from a PID controller.

Sending unsolicited AI-generated email to the address scraped from my GitHub profile is not a growth hack, it's in violation of the CAN-SPAM act.

Some critical projects like @typescriptlang.org don't (or can't) follow SemVer. They suggest users pin versions in package.json. But what if npm package versions could explicitly *declare* their compatibility range. Clients could further constrain ranges for upon opt in. Best of both worlds.

I've seen folks looking to use AsyncLocalStorage as a way to propagate identity across async boundaries in server logic. That seems very scary to me because AFAIK it relies on 3rd party libs opting into AsyncResource or risking confusion in some edge cases. WDYT?

WinterTC is here 🎉 TC55 is a new Ecma Technical Committee for Web-interoperable Server Runtimes, originating from the existing W3C WinterCG group. This means the group is now able to publish standards, with the first effort being the Minimum Common API.

What are some useful pattern you’d expect to work across bundlers? We’re collecting a list here: github.com/tc39/js-outr...

@zachleat.com fascinating interview on @syntax.fm. Very inspiring. It sounds like many of the product velocity benefits of federation could also accrue on the backend. Do you have thoughts / observations? Worthwhile pursuit?

This seems like a fascinating innovation in load balancing but I feel like I didn't get a full picture from the talk: 1. Do the use the latency of the Probes or some aggregate of the Queries as predictors? 2. What if Queries are very heterogenous? 3. How do they derive predicted latency for RIF(n)?

Here's my aspirational vision for a modelcontextprotocol.io (MCP) project. I'm pretty excited by the potential but the scope is _huge_. If you're unfamiliar with the MCP, it tries to standardize a protocol for clients like Claude, Zed editor, etc. to get extensible super-powers. WDYT?

We are hosting an MCP hackathon in SF (December 10th) and NYC (December 11th) and giving away $30,000 In Anthropic API credits. Come join us! x.com/alexalbert__.... 🧵for more info

Huge deal! It happened. I hope this will pull back the ESM CJS partition that crept in. Bravo @joyeecheung.bsky.social and collaborators!

I bet OCI images (docker images) are a pretty perfect distribution format for MCP servers. As containers, we can abstract away dependencies while also isolating the host system as much as we want. And they should *just work* as stdio servers with the `-i` flag. Anyone already working on this?

I bet OCI images (docker images) are a pretty perfect distribution format for MCP servers. As containers, we can abstract away dependencies while also isolating the host system as much as we want. And they should *just work* as stdio servers with the `-i` flag. Anyone already working on this?

Here is a fun one for you all: contrary to popular belief, in Node.js promises (async/await) would not yield to the event loop. So, if you want the event loop to process I/O in between a long chain of async functions that actually aren’t doing I/O, you would need to add a setImmediate in between.

I think @anthropic.com's Model Context Protocol is fascinating. I've been re-implementing the stdio and sse protocols to understand the inner workings and am at the MVP stage. I'm exposing a custom weather tool that always responds with `"sunny with a chance of meatballs"` 🤣. Claude is onto me.

Once upon a time, Agile was agile.

TIL that browser fetch doesn't allow duck-typed AbortSignal instances or Proxy instances that wrap real signals. Seems like a bit of a bummer for performant, interoperable AbortSignal tooling. Is this by design?

A closely related quote: "never accept criticism from someone you would not ask for advice."

TypeScript 5.7 is released 🎉 🔶 ES2024 library types 🔷 Checker: Never-initialized variables 🔷 Checker: Stricter JSON imports 🔷 Emit: Extension rewriting (*.ts to *.js) 🔷 DTS: Computed methods 🔷 IDE: Better tsconfig discovery 🔷 Perf: Code Caching ⚡️ 2.5x faster startup

What are the go-to tools for testing against memory leaks in JavaScript libraries? I'm particularly worried about an object graph being retained by circular references.

You know what feels terrible? Leading open source volunteers on a wild goose chase only to discover you were at fault all along. 😫

Google is an imperfect steward of Chrome, but I cannot think of anyone who'd have the capital to buy & run Chrome that wouldn't be worse in every way

You know what feels terrible? Leading open source volunteers on a wild goose chase only to discover you were at fault all along. 😫

It's both a blessing and a curse to run high throughput, complex @nodejs.org workloads on the server. Blessing because there's lots of impact. Curse because we have a weird way of surfacing all the long tail weird issues in production.

With @satanacchio.bsky.social's work on stabilizing type stripping in @nodejs.org, will it become reasonable to ship modules in all their @typescriptlang.org -native glory?

I'm starting to think this way too but the muscle memory is brutal.

It's been *years* (probably since creating nostalgie.dev) that I haven't really written React code. It's *tough*. I just want to work with plain JavaScript state and have React *only* do rendering. But it feels like I'm swimming against the current trying to do so. What abstractions do folks use?

Sorry about all the confusion. I'm moving from @filearts.bsky.social to @goodman.dev before I get too engaged on the 'wrong' account.

Friends, I've committed a BlueSky fail and forgot that I have a nicer @goodman.dev account from the invite-only era. Is there a way to merge things back together?