Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Firefox in WebAssembly

developer.puter.com

Post reply on HN
Print view View original

31–40 of 134 posts

Re: Show HN: Firefox in WebAssembly

#31

Post by brewmarche »

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

Re: Show HN: Firefox in WebAssembly

#32

Post by ent101 »

Retr0id wrote: post #30
rlmineing_dead wrote: post #27

Earlier quoted context omitted.

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 prox…

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.

Re: Show HN: Firefox in WebAssembly

#33

Post by simonw »

This is amazing. I loaded up https://developer.puter.com/labs/firefox-wasm/ in Chrome and I've visited a bunch of sites, it works really well.

Then I opened up https://developer.puter.com/labs/firefox-wasm/ in Firefox-in-WebAssembly-in-Chrome

... and sadly it didn't load. I got this in the startup log:

  [log] [chrome-demo] chrome assets ready
  [warn] [gecko] warning: unsupported syscall: __syscall_madvise

Re: Show HN: Firefox in WebAssembly

#34

Post by tiagod »

yjftsjthsd-h wrote: post #29

>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.

Re: Show HN: Firefox in WebAssembly

#35

Post by smalltorch »

yjftsjthsd-h wrote: post #29

>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?

I imagine it is 25k tokens not dollars

Re: Show HN: Firefox in WebAssembly

#36

Post by rlmineing_dead »

Retr0id wrote: post #30
rlmineing_dead wrote: post #27

Earlier quoted context omitted.

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 prox…

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.

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

Re: Show HN: Firefox in WebAssembly

#37

Post by gnabgib »

ent101 wrote: post #25
zerof1l wrote: post #23

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?

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.

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

Re: Show HN: Firefox in WebAssembly

#38

Post by rustyhancock »

smalltorch wrote: post #35
yjftsjthsd-h wrote: post #29

>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?

I imagine it is 25k tokens not dollars

That's standard token usage for /init

Re: Show HN: Firefox in WebAssembly

#39

Post by rlmineing_dead »

brewmarche wrote: post #31

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 0x11…

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

Re: Show HN: Firefox in WebAssembly

#40

Post by brewmarche »

rlmineing_dead wrote: post #39
brewmarche wrote: post #31

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 0x11…

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.
Post reply on HN