You can give chisel a try. It tunnels all traffic over http/https, and the client can then create port forwards, just as with ssh, to access other services.

I think glider can do this, with -strategy rr (Round Robin mode). I have not used it in this way myself, so you might need to experiment a little. Proxychains can also do this, but it doesn’t present a socks5 interface itself (it uses LD_PRELOAD, so it won’t work everywhere).

https://stackoverflow.com/questions/10602504/how-does-user-js-work-in-firefox-in-detail:

It just looks like a JavaScript file. Once upon a time in Netscape 3 and maybe 4 it actually was, but now it’s just a file with a .js extension and a very restricted syntax that’s parsed by a separate (non-JS) parser and not executed in any way.

Quad9, a Swiss public benefit, not-for-profit foundation. Main address is 9.9.9.9.

We have those on I2P already, see tracker2.postman.i2p for example.

You should not torrent over the tor network, but you can torrent over the I2P network. qBittorrent even has experimental I2P support built in.

Here is a config template to run an obfs4 bridge, make changes as required:

BridgeRelay 1

# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ORPort TODO1

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:TODO2

# Local communication port between Tor and obfs4.  Always set this to "auto".
# "Ext" means "extended", not "external".  Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto

# Replace "" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo 

# Pick a nickname that you like for your bridge.  This is optional.
Nickname PickANickname

You can also use the reachability test to check if everything is configured correctly. If it is reachable and bootstrapping reaches 100% you should be set.

Set SocksPort if you want to connect your browser (don’t confuse this with ORPort). Default is localhost:9050.

I’m not on NixOS, but I have a decent working knowledge of Tor.

Not quite clear on what you’re trying to do, are you trying to run a relay, or just connecting to the Tor network and pointing your browser to the socks proxy?

Arti (the official Tor implementation in Rust) is not a complete replacement for the Tor C implementation yet. Hidden service support is disabled by default (due to the lack of a security feature that could allow guard discovery attacks), and bridges don’t work either. If you don’t understand Tor very well stick with the old router.

Indeed. This works because direct connections to the tor network are easily censored, but WebRTC is not (not without a lot of collateral damage at least).

The snowflake proxy acts as a bridge to the tor network at the entry side. If by repercussions you mean risk of exit-node traffic, there are none. It might cost a little bit of bandwidth.

The bot missed the remaining 7 pages and the result of the benchmark:

“Overall it comes down to what workloads you are engaged in whether you may notice any performance difference when upgrading your Linux kernel (or otherwise being patched for Inception on your given OS) on an AMD Zen desktop or server. For the most part users are unlikely to notice anything drastic, aside from some sizable database performance hits in a few cases. It’s unfortunate seeing some of these regressions due to the Inception mitigation but ultimately is unlikely to really change the competitive standing of AMD’s latest wares on Linux. Most of the prior AMD CPU security mitigations have also not resulted in any performance degradation, so this Inception mitigation difference is a bit rare. It also was announced on the same day as Intel Downfall where there was again a sizable hit to Intel CPU performance.”