HelloZeroNet
commented
5 years ago Probably it would be better solution to randomize port if the client detects external IP change, so it would not lead to more dead peers and you would not have to restart your client if you change network.
The site count at peers line on /Stat page is based on the sites peer list. So it counts how many sites you seeding that has that ip:port in the peer list queried from the trackers. Your client don't know how many sites the other peer is seeding.
Hello,
while the fileserver_port number is constant (even if once randomly generated), maybe this constant port number can be another indicator that can hurt anonymity of the user meaning if there are peers who are collecting zeronet network traffic, this constant (unchanging port) may (i do not know) help them pair network activity even if one's IP is changed or if zeronet ID is changed (increasing probability that two IDs are used by one person).
Why not do it by default the way that if fileserver_port is set to 0 in zeronet.conf (i think this should be by default like that), then zeronet will be generating random port on EVERY start?
I think that this is related code.
Another thing like static fileserver port is count of sites one user has. (i see it in /Stats), unsure why this is needed, because it also looks like another thing that may help connect/pair numeours accounts/IDs?