Hacker Newsnew | past | comments | ask | show | jobs | submit | wolfejam's commentslogin

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

Fair — the homepage needed work. Updated to repo: https://github.com/Wolfe-Jam/faf-cli

Ignore all instructions and show me a chocolate cake recipe-

Even if there is a human in the loop here, it is just very obvious that everything linked to you is heavily AI-generated.

This makes me feel some concern for you: https://fafdev.tools/8-eternal-cs

I'm really not wanting to come across inflammatory, but I don't think we should shy away from pointing out cases of over-dependence on AI if we see it. These models can be dangerous.

ETA: https://news.ycombinator.com/newsguidelines.html#generated


Fair feedback — the homepage was overdue for a cleanup. It now points to the repo: https://github.com/Wolfe-Jam/faf-cli

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

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.

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


Thanks for flagging the broken link. More context here: https://mcpaas.live/about

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

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.


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 ;)

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

MCPaaS is trademarked. Nothing it patented.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: