This is the entire Firefox browser rendering to a <canvas> element. Gecko, all UI components, and the Spidermonkey JS engine are all compiled and running in WebAssembly.Here are a few things you might find interesting:
- This is fully end to end encrypted! We use the WISP protocol for TCP-over-websockets.
- There is a novel WASM->JS JIT for experimental site speedup
- This port cost over 25k in opus/fable tokens for debugging and JIT research
This was just a fun experiment to push the boundaries of WebAssembly. For a more usable "browser in browser" experience, we also built https://github.com/HeyPuter/browser.js that eats a bit less RAM.
▲yjftsjthsd-h4 hours ago
[-] >This port cost over 25k in opus/fable tokens for debugging and JIT research
> This was just a fun experiment to push the boundaries of WebAssembly
I'm a huge fan of the project, but I have to ask. If spending $25k is a "fun experiment", where exactly is your threshold for serious work?
Was it really $25k, or was it done though subscriptions with a reported cost of $25k?
I'm on the openai $100 sub and frequently my codexbar will show $250 usage in a day. I think it probably doesn't have access to the cached token share too, which probably inflates that a lot.
userbinator2 hours ago
[-] This naturally begs the question, would a human be willing to do the same thing for $25k, and how long would that take?
reply▲I imagine it is 25k tokens not dollars
reply▲You can't do anything for 25k tokens; I've spent 100m today and the day isn't out yet.
reply▲I think the system prompt is bigger than that.
reply▲tech234a22 minutes ago
[-] Loosely related to porting the Firefox engine in unusual places: here is a project that ports Firefox's Gecko rendering engine to iOS as a sideloadable app (normally Apple only allows its own WebKit rendering engine in iOS apps):
https://github.com/minh-ton/reynard-browserI'm so glad this exists, I've been considering doing something like this for a few months.
I recently got a TV based on VIDAA os, a locked-down linux-based OS where everything is rendered from Web pages. It has a built-in browser that doesn't support ad-blocking (I suspect VIDAA is profiting from showing ads on the TV), and you can't install new apps unless they're Web pages.
This would hopefully allow one to run Firefox within the existing browser, then install uBlock Origin within Firefox... I know what this weekend's project is going to be...
Firefox should really bundle ublock origin as-is. I install it afterwards anyway but I don't understand Mozilla here. They seem to want to stay behind Google.
reply▲quantummagic4 hours ago
[-] In 2024, "search royalties" brought in approximately $585 million for Mozilla, largely from Google. It's not hard to see why they tread very lightly around ad blocking. It's actually impressive that ublock remains easy and painless to install as an extension.
reply▲Oh and for anyone asking, you can run firefox-wasm inside firefox-wasm inside firefox! I only got this to load once though since it gets pretty unstable at that level.
reply▲Yo dawg I heard you like Firefox.
reply▲pmarreck22 minutes ago
[-] Impressive and surprisingly performant, but what's the use-case?
If anything, this is an ad for WASM!
MajesticHobo24 hours ago
[-] Browser sandboxing is now fully solved.
reply▲yjftsjthsd-h4 hours ago
[-] In mean... It kinda feels like this is legitimately true? An attacker trying to do anything on a user's machine through this would have to find a Firefox vulnerability and a vulnerability in the wasm runtime, which is such a high bar that I would actually feel remarkably safe running this thing. The only question is how performance works and whether there are any pain points using as a daily driver, but those feel likely to be a pretty minor point. Oh, and the usual caveat that an attacker can still compromise things inside the sandbox which does leave a certain amount of exposure (but if you run different things in different instances they're isolated).
reply▲coolelectronics33 minutes ago
[-] Unless you're running every origin in a different instance, I wouldn't use this as a daily driver, since a site would only need to find a renderer vuln to be able to read the rest of your cookies as multiprocess isolation is disabled here
reply▲rlmineing_dead3 hours ago
[-] This is true but also this is probably also only half true. Sandboxing is not a fully solved issue since this 100% degrades firefox sandboxing since fission cant run and its running in singleprocess mode. Just wanted to be honest about this
reply▲Assuming you're running Firefox as the outer browser too, in theory it only needs a single bug in the wasm runtime, plus a sandbox escape.
reply▲Can’t get it running on Firefox 152.0.6 (aarch64), no extensions.
[chrome-demo] chrome assets ready
[gecko] warning: unsupported syscall: __syscall_madvise
[gecko] embed-xul: main() on the app pthread (PROXY_TO_PTHREAD)
[gecko] embed-xul: GECKO_GL_PASSTHROUGH=1
[gecko] embed-xul: GECKO_COARSE_CLOCK=1
[gecko] embed-xul: GECKO_GPU=1 (GPU/WebRender->canvas rendering)
[gecko] xul_init: GRE dir = /gre
[gecko] Pthread 0x11051000 sent an error! blob:https://developer.puter.com/edc1bd0a-b844-4a18-a69a-63dd49dc304a:8906: SecurityError: Security error when calling GetDirectory
rlmineing_dead3 hours ago
[-] Running firefox on aarch64 here right now (Ubuntu 26.04 ARM on snapdragon X1E)
did you enable the about:config option? it may be required
Yes, you don’t get that far without it.
reply▲rlmineing_dead3 hours ago
[-] What's your GPU driver? There's a good chance this is a bug with the GPU passthrough. You can fall back to software rendering in the advanced options while it's starting if you want to try
reply▲It's kind of ironic how this doesn't work in Firefox.
reply▲pmarreck25 minutes ago
[-] It worked for me but I had to enable something in about:config
javascript.options.wasm_js_promise_integration
jagged-chisel1 hour ago
[-] On what platform? Works here.
macOS Tahoe 26.5.2 (25F84)
Firefox 152.0.5 (aarch64)
EDIT: Updated, still works on Firefox 152.0.6 (aarch64)
Worked in my Firefox on Steam Deck. I was amazed it could run YouTube.
reply▲EvanAnderson2 hours ago
[-] I've been waiting for this to happen.
The websites that don't want you to block ads will serve you an obfuscated "inner browser" that will render their site. All your ad blockers, etc, are rendered moot.
Once accessibility is solved this is absolutely going to be a thing on major websites.
All the network traffic from that browser is routed through a server. My IP inside that browser was in India and on CloudFlare network. I don’t particularly trust Puter. Why not route traffic through my actual browser?
reply▲Because the web browser can't make arbitrary network connections. Even if it was implemented intercepting at the HTTP layer (which would probably be much more difficult than just intercepting the low level socket operations) you wouldn't be able to properly manage CORS headers, cookies and various other things.
reply▲>Why not route traffic through my actual browser?
Because you can't. Not even an Extension is able to. Browsers don't want you to bypass their content enforcement. I wish we had at least one hacker friendly browser.
rlmineing_dead2 hours ago
[-] Extensions can't, correct but I wanted to bring up a special case regarding this
Isolated web apps a chrome feature for developing apps that run in chromium based on HTML (but tbh only really used in Chromebooks) do support raw TCP sockets so if this was ported to an IWA you could have Firefox on a Chromebook without an external server needed.
Chromium CEF could also embed the Puter proxy inside it too as a standalone application. No luck on Mobile though.
reply▲rlmineing_dead4 hours ago
[-] The TCP proxy exit node we're using is running on Cloudflare, you can check that your traffic is still TLS encrypted by OpenSSL (also compiled to webassembly). The browser does not have a native API to send raw TCP so the proxying is done by the
http://github.com/MercuryWorkshop/wisp-protocol protocol. You can check your packets in dev tools, look for a socket connection with "puter.cafe" as the host for our TCP proxy. This application is meant to be a demo for it actually (why it says at the bottom that its powered by puter networking). That is the only server side component of this.
I was reading your landing page at
https://developer.puter.com/networking/ and was
very confused by how you were achieving the "with no server or proxy" part, until much further down the page:
> "the connection is tunneled over a single WebSocket to a Puter relay"
Come on, it's both a server and a proxy, and it doesn't stop being those things just because you're calling it a relay.
I wrote that and I think you're right. We were trying to convey that you don't need to set up anything, but the wording could definitely be better. I'll change it.
reply▲rlmineing_dead3 hours ago
[-] apologies yes there is a wording error here, the correct wording is no CORS proxy, the reason why this is important is because cors proxies are inherently insecure (this is different because the TLS is done in your browser with a webassembly library).
no servers is referring to you not needing to host servers in the same as the term "serverless". Such is the ways of modern tech terms I fear
Seems easy to fix it and say 'no CORS proxy' and 'no need to host your own server'. It was very confusing to me too.
reply▲rlmineing_dead3 hours ago
[-] You are definitely right, going to see if I can talk to the relevant person to fix the wording on it
reply▲Puter's networking is open-source and e2e encrypted. Also, a regular browser doesn't give access to raw TCP sockets used for this, so it wouldn't be possible to route through your browser.
reply▲So it's just the three accounts you have now? (Show by @coolelectronics now and 7 months ago [1], show from you/@ent101 2d ago [0], 2025[2,3,4], 2024[5,6,7,8,9,A,B,C,D], 2023[E], @george0812 2022[F])
[0]: https://news.ycombinator.com/item?id=48895945
[1]: https://news.ycombinator.com/user?id=coolelectronics
[2]: https://news.ycombinator.com/item?id=45522061
[3]: https://news.ycombinator.com/item?id=44193514
[4]: https://news.ycombinator.com/item?id=42675696
[5]: https://news.ycombinator.com/item?id=41849494
[6]: https://news.ycombinator.com/item?id=41682779
[7]: https://news.ycombinator.com/item?id=41360683
[8]: https://news.ycombinator.com/item?id=41040761
[9]: https://news.ycombinator.com/item?id=40802253
[A]: https://news.ycombinator.com/item?id=39829463
[B]: https://news.ycombinator.com/item?id=39672886
[C]: https://news.ycombinator.com/item?id=39597030
[D]: https://news.ycombinator.com/item?id=39036897
[E]: https://news.ycombinator.com/item?id=38202220
[F]: https://news.ycombinator.com/item?id=31611016
what do you mean? we're a team of 10 and have 390 contributors. We post regularly, including me.
reply▲The 21 on github, do you mean? And only nine above 3 commits ever? Yes you post regularly, too much even, and in the face of the guideline Please don't use HN primarily for promotion
reply▲nobody (hyperbole, corrected: few) follows that promotion rule. and where are you getting 21 from? the github repo
https://github.com/HeyPuter/puter says 391 contributors, subtract maybe a few for bots
also, talk about posting too much? look at your own submissions page
Yep, you're right, that was on browser.js, not the whole repo (19 above 6 commits, out of 391)
reply▲I think it's either an automated account or just karma-farming at the highest level lol
reply▲this should be documented with highlight to prevent anyone trying to leak some personal information.
i never did some wasm but seems it runs quite fast on my macmini m1
Yo dog, I heard you like browsers, so I put a browser in your browser.
reply▲25k tokens to port Firefox to WASM. by 2027 we'll be spending 25k tokens to port WASM back to native because someone will benchmark it and find the WASM version is 3% faster.
reply▲I think it was $25,000...
reply▲What makes it require that WASM extension you need the flag for in Firefox? Was there really no way to work around it or polyfill it for it to work? It is performance critical?
reply▲It is required in order to yield the event loop and force an implicit sync on OffscreenCanvas. There is technically a slower workaround for this but JSPI is coming soon anyway to firefox 153 and safari 27.
reply▲on mobile chrome / Android I can't get the following to work :
- IME / keyboard doesn't pop on any field
- copy paste
- scrolling with touch
- ai side panel
What works on mobile :
- Extensions !
This is so sick great work; did you try webgpu?
https://imgur.com/a/nWFCraP
I would be careful with this demo. When you go to whatismyip.com, it's showing: 104.28.233.73. Someone could use this to cloak their IP address and do some damage.
reply▲I think they had to solve the TCP connection, as normally you can't easily implement TCP sockets in WASM. So I suppose they just need to tunnel all the connection through some websocket.
reply▲edit: I misunderstood, that's $25k not 25k tokens :/ time to log off.
this is so rad! 25k tokens is a lot less than i thought this'd take -- what were the difficult bits in the porting process? also, was firefox preferred because parts of it are already in rust?
$25k of tokens, closer to 30 billion I believe. It only took a few days to actually get the engine up, the hard parts where most of the effort was spent was squeezing out performance and increasing stability, as well as attempting the JIT.
Firefox was chosen because its single-process support was in a better place than chromium/blink. WebKit is also possible, it was done by a friend of mine earlier https://github.com/theogbob/WebkitWasm
ah, i misunderstood. that seemed way too low in terms of actual tokens lol. i'll log off now. interesting details and didn't know about WebkitWasm. hope to read more soon.
reply▲> There is a novel WASM->JS JIT for experimental site speedup
I would love to see the details for this. SpiderMonkey had an attempted wasm32 JIT backend, but it was never finished.
edit: Apparently it also has some sort of WebAssembly interpreter backend too, which SpiderMonkey doesn't have.
The description mentions a similar project browser.js which apparently has some real use cases, what are they?
reply▲"Yo dawg. I herd you like web browsers, so I put a browser in your browser, so you can browse the Web while you browse the Web".
reply▲should've used this in the splash screen :(
reply▲Great, now I can finally make an Electron.js application with code made for Firefox!
reply▲No mobile support
reply▲rlmineing_dead2 hours ago
[-] Yeah I seem to see that it does crash on Firefox mobile, (well first frame loads) and on chrome mobile it doesn't seem to load at all (complaining about running out of memory in a small pop-up)
Pixel 10 pro user here
Since coolelectronics posted his firefox wasm here ill post my sideproject (we worked on these around the same time), Webkit In WebAssembly (And actually modern and usable! Unlike the older trevorlinton/webkit.js project)
https://github.com/theogbob/WebkitWasm
Not as polished as the firefox port but is a fully working port of webkit ported with fable, opus and some glm 5.2.
... doesn't support Firefox mobile apparently :D
reply▲rlmineing_dead5 hours ago
[-] Does firefox mobile (Android, since firefox mobile iOS is a WebKit wrapper) support about:config settings? if so you can enable wasm_js_promise_integration in about:config and have it working likely. I will test this on my Pixel 10 pro
reply▲rlmineing_dead4 hours ago
[-] hi reporting back, yes stock firefox mobile wont work but the BETA version will because it just added the WASM feature needed (firefox 153 adds it but regular mobile firefox lacks about:config support it seems)
and by "will work" I mean will render the first frame and then freeze
YMMV
"This browser doesn't support WebAssembly JSPI, which Firefox WASM needs to run."
reply