bastawhiz 3 days ago

It's really annoying that you can stop the globe from rotating. This also feels exactly like a Claude-built website, which is unsurprising.

  • g051051 3 days ago

    Looks like they just updated it. Check under the globe.

  • wolfejam 3 days ago

    use the pause button below it, zoom in/out, rotate too

    • bastawhiz 2 days ago

      Wasn't there when I originally visited

rcakebread 3 days ago

"36 cities so far. Every visit lights up your dot."

You paid to patent this, whatever it is. How about more than two sentences to see what you're charging people for. I can't tell from the website's "About" page.

Edit: Even the github link is a 404, I give up.

Dwedit 3 days ago

WASM + Zig (even compiling C code) will make some really tiny WASM files with no dependencies. The problem is that you don't have a standard library, then your code gets really big as you add more of that in there.

  • wolfejam 3 days ago

    Exactly right. 2.7KB works because it's pure computation — slot counting, no allocator, no stdlib, no WASI. The moment you need I/O it balloons. This use case fits a glove

ianberdin 3 days ago

What do you sell? Names? Names for what? Site is kinda laconic…

  • wolfejam 3 days ago

    MCPaaS serves persistent AI context via the Model Context Protocol. A namepoint (mcpaas.live/yourhandle) gives your AI instant project context — no re-explaining every session. Works with Claude, Gemini, Cursor, any MCP client.

    Claim yours, free or paid: https://mcpaas.live/claim

    The globe shows where the edge binary executes. More at https://mcpaas.live/about

topspin 3 days ago

It there some law that mandates all 3D globe renderings auto rotate and omit any way to stop it?

  • wolfejam 3 days ago

    use the pause button below it

    • topspin 3 days ago

      Thanks! I see that just got added.

flohofwoe 3 days ago

Plus a 1.8 MB Javascript file ;)

...that's too big for a JS shim to talk to browser APIs... it looks more like a complete 3D engine - e.g. three.js or similar?

From that pov the 2.7 KB WASM is a bit misleading (or rather meaningless), it could be a single function call into that massive JS blob where all the work happens.

  • wolfejam 3 days ago

    Fair point — globe.gl (Three.js) handles the 3D rendering client-side.

    The 2.7KB WASM is the server-side scoring engine — Zig-compiled, runs on every request at the Cloudflare edge. The globe visualizes where those executions happen.

    Two separate layers: WASM at the edge, JS in the browser.

    • flohofwoe 3 days ago

      Ah ok, might have made more sense to link to the about page tbh, but that probably would have looked too obviously like an advertisement ;)

      • wolfejam 3 days ago

        just trying to show the zig-wasm binary and CF edge :)

  • eknkc 3 days ago

    This is a completely baffling website but as far as I can tell, the 2.7 WASM thing is the MCP runtime this is marketing? The globe thing is independent of that, just showing there the MCP calls are running.

    • wolfejam 3 days ago

      The 2.7KB Zig WASM binary is the scoring engine that runs on every request at Cloudflare's edge. The globe visualizes where those requests land. Two layers — compute at the edge, visualization in the browser.

  • ivanjermakov 3 days ago

    Three.js alone is ~400KB uncompressed.

    • wolfejam 3 days ago

      Yep — Three.js renders the globe client-side. The 2.7KB scores server-side at the edge. Separate concerns.

wolttam 3 days ago

What in the slop? I have rarely seen so much of it concentrated across just a few domains

wolfejam 3 days ago

thanks for visiting — the globe just crossed 100 cities - Appreciate the feedback. Happy Sunday :)