3 ms·
>it needs port forwarding to work correctly What are you talking about? You need to put a proxy 127.0.0.1:4444 into your browser setup, but I wouldn't call it
by fsflover 6y ago
>it needs port forwarding to work correctly
What are you talking about? You need to put a proxy 127.0.0.1:4444 into your browser setup, but I wouldn't call it "port forwarding". Apart from that, you just install it and go to the eepsites. Upd: Indeed, you will also have to wait until the router finds enough peers.
>What are the missing pieces to get people using this?
I would say, it only needs more people to know about it.
- Funes- 6y agoA firewalled router will not work correctly (it will be slow as hell, basically, and you'll be leeching off the network instead of contributing to it). I appreciate the project as much as anyone interested in it, but let's be real here. On top of that, no router will work efficiently right after installation, firewalled or otherwise. You have to give it time to find other routers and make connections. It's just not suited for the immediateness almost everyone expects from everything nowadays. It needs a major revamp in order to increase its adoption.
- fsflover 6y agoThis is all true. However if the goal is convenience, speed and adoption, one could decrease the number of hops and it will work much faster. > and you'll be leeching off the network instead of contributing to it Does not look like a problem in Tor (despite one would expect otherwise, given that by default you do not contribute back unlike in i2p). You just need enough seeders.