From the FAQ:<p>> How long does it take for a post to reach the most of the network?<p>> [...] Long answer [...]<p>> [...] In fact, it’s a little larger than one request in a minute, because some nodes are behind restrictive firewalls and NATs, and they cannot be reached, they can only make requests out.<p>Regardless of the actual FAQ discussed here, the statement is made that "some" nodes are behind NAT's, implying that most will <i>not</i> be behind NAT's. Living in the Netherlands, I'm not sure about countries overseas in the Americas, but here I'd wager >99% of normal household PC's will be behind a router implementing NAT. This makes actual peer-to-peer communication nigh impossible here, and I'm always doubtful about nice peer-to-peer solutions that claim to be cool and such but sneakily have the ever-present requirement that you have a public IP address. I don't. Nobody I know does, except for VPS's and so forth. But I generally don't run a graphical client on my VPS.<p>Of course, theoretically, this should be solved by IPv6. But really I wouldn't know how to start using that, and whether my provider has all the hardware and software in place to actually have this work. (And whether my provider-issued router supports it, as well.)<p>Can anyone chime in on how the situation regarding NAT's is in the Americas? And does anyone have a good source on how to get started with IPv6 communication between peers, when I don't even know the stuff I mentioned above?<p>EDIT: I see that Aether has/seems to have the option to work around this problem by allowing one to run the backend (the thing that actually connects to the peer-to-peer network) on a different machine than the client. That would enable using a VPS to run the backend.