Comment by rlmineing_dead

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

5 comments

rlmineing_dead

Reply
Retr0id  5 hours ago

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.

  • ent101  5 hours ago

    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.

  • rlmineing_dead  5 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