21–30 of 31 posts
What do you sell? Names? Names for what? Site is kinda laconic…
Claim yours, free or paid: https://mcpaas.live/claim
The globe shows where the edge binary executes. More at https://mcpaas.live/about
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.
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.
I'm both fascinated and worried about what the internet will look like in five years.
[2] https://web.archive.org/web/20150506055228/http://www.timecu...
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.
Three.js alone is ~400KB uncompressed.
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.
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.
Earlier quoted context omitted.
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 ;)
Looking at the website of the organization [1] of the author, linked at the bottom of the submitted link, I get serious Time Cube [2] vibes. I'm both fascinated and worried about what the internet will look like in five years. [1] https://www.faf.one/ [2] https://web.archive.org/web/20150506055228/http://www.timecu...
What in the slop? I have rarely seen so much of it concentrated across just a few domains
What in the slop? I have rarely seen so much of it concentrated across just a few domains
Fair — the homepage needed work. Updated to repo: https://github.com/Wolfe-Jam/faf-cli
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