chrome not support direct create tcp connnection cause this project stuck

[lrobot]

I do some reseach on this project and it background "freedom.js", I found that it can not be continue because chrome not support the tcp feature.

Maybe better get a discontinued statement and cause,
Can give better info for all the follower(or starter)

[lrobot]

ref: freedom.js, https://github.com/freedomjs/freedom-for-chrome/blob/master/providers/core.tcpsocket.js#L14
ref: https://developer.chrome.com/docs/extensions/reference/sockets_tcp/

[olivierpichon]

Just adding a note for anyone who finds this project years later:

The original browser-extension approach that uProxy used (Chrome/Firefox + direct TCP APIs) has indeed run into extension/API deprecations, so I don’t expect this repo to see much life again.

I really liked the idea behind uProxy: a simple way to let a trusted friend or your own home machine act as an exit node. So I built a small standalone app that implements a similar concept outside the browser: TunnelBuddy.

It’s not a Chrome/Firefox extension; it’s a desktop app using modern networking/WebRTC instead of legacy extension TCP APIs.

It focuses on one use case:

• “giver” runs the app and shares a one-time code

• “getter” enters the code and routes their traffic via the giver’s machine

It’s aimed at non-technical users who just want to “use my home internet from anywhere” or help a trusted friend, not a 1:1 continuation of uProxy.

If you were a fan of uProxy and are looking for something with a similar feel that still works on current platforms, you might find it useful: https://www.tunnelbuddy.net/

(This is a separate project, not affiliated with UW or Google; just an independent attempt to keep the “personal, friend-to-friend proxy” idea alive.)