I'm bringing this discussion over from support about how we can better support people behind very restrictive firewalls.
> A P2P system won't I know, but a P2P2P system would, where you connect > what is effectively an HTTP tunnel out from behind a firewall to a host > which will allow connections to other hosts - tunneling hosts included. So the components of this system are as follows: Making nodes accept HTTP encapsulated connections Making some nodes open connections to all known nodes on startup Adding shadow node address resolution Is anyone interested in working on any of these? Does this seem like a worthwhile goal? > A proxy-only HTTP firewall. Very restrictive. But my own personal > firewall problems ain't what I see as the issue here - I've already Well, that's kind of the issue. You came in and said Freenet doesn't work behind firewalls! When in actuality Freenet works behind a variety of firewalls, but not the kind that you have. > > work behind a firewall. It's not that we're lazy or no one has complained > > about this before. > > I'm a first? Makes a change :) The way I see it most people access the > internet from work, and corporates are very sensitive about perforating > firewalls - I find it hard to believe that I'm the first to encounter > this problem. Actually, I meant you're not the first. People complain about this a lot. You're probably the 50th. But many people don't actually have these stringent requirements. Most people can get what they want from Freenet behind their particular firewalls once instructed how to do so. _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
