[pod]

I don't think anyone here is confused about what you are talking about. You propose that since 1.4 seems to be 'safe', it can be used to revive the 1.3.3 network; 1.4 also doesn't seem to upgrade older clients, and so can act as a 'bridge' for 1.3.3 clients.

There are at least two potential ways to implement what you propose, all fraught with issues.

The most straightforward way is to introduce the 'safe' 1.4 nodes and get them promoted to supernodes withing the bigger network. Then have older clients connect to the 1.4 nodes and hope they'll remain safe.

Problem here is that while 1.4 SNs may not get upgraded by new nodes, by joining the network 1.4 SNs will be seeded with many non-1.4 node IPs, which will be cheerfully forwarded to 1.3.3 clients. Since clients connect to multiple supernodes (during one or more sessions), there is a high risk of them contacting a new SN, which will force an upgrade.

Reinfection is an issue, but an even bigger risk is, as you said, that for some reason 1.4 is sill allowed on the network. Why? Maybe it's because the 1.4 clients isn't very widespread. Maybe some licencee is still using it. Whatever the reason, even if 1.4 nodes cannot be auto-upgraded, they can easily be disallowed from connecting in the first place. It's only a mtter of time before FT does this; it doesn't buy you any time, and isn't good for shareres. You're just contributing to a dead-end network. Spend your time and bandwidth supporting a better one instead.

So the other option is to have a stand-alone network, either because you're locked out, or by choice. If you're locked out and form your own one, there is nothing stopping FT from trying to connect to it and re-infect the older clients within it, should they wish to cause you trouble. Somehow you have to prevent new nodes from connecting to your network if you go this route. But how? Nodes always allow NEWER clients to connect, you can't stop them. Run it on a different port? Sure, but how do you distribute this information (and seed node lists) to enough people to make a worthwhile network? If a small network is what you want, just run an OpenNAP server, it's easier to find and connect to with virtually any existing P2P client.

The sticking point is that, yes, technically the FT network can run split up by version numbers, assuming it is left alone. Which hasn't been the case. As soon as an 'outdated' node touches a higher version supernode, it will be upgraded and moved to the new network. If there was no automatic upgrading (which you don't know for a fact is the case with 1.4), then same version clients would stick together. BUT, FT/Kazaa is bent on moving everyone to the new network, for obvious reasons, and any attempt at a separate network of any significance will be disbanded by auto upgrades. And if your idea IS to run a small network, there are better ways to do it, and we already have an OpenNAP server for NU you can connect to.