First, I want to avoid all the legal baggage and complications that come with running a
freenet node. Second, freenet is written in java. Finally, I want to try and offer people
the freedom of choice to run which ever p2p software works and runs best on their system. If the
individuals who are currently participating in the freenet network would like to carry freesoftware
on their network they are certainly capable of doing that, but the idea of participating in freenet
as nodes, or some kind of forked subnetwork, is a sub optimal one for FSPN. It is my hope that
Universities and large companies will participate in FSPN as nodes. If FSPN participants where
not able to have full control over the content of their nodes and where not able to even know exactly
what content was on their nodes, it is highly unlikely that FSPN participation would reach the level
in that demographic of participants I hope for.
This is something I'm currently looking into. Once FSPN has some well established and stable
central access points, this will be allot more practical. There really isn't any very good stable
p2p software out there right now and accessing a private subnetwork further complicates the function
that the unstable and underdeveloped software must accomplish. Therefor, initially I think it's a
good idea to keep everything as simple as possible. Allowing searches to discover FSPN content
though the main p2p network(s) of given p2p technologies also reduces the load and reliance on
the central FSPN servers until more can be established and more resources can be acquired.
Developing a new p2p architecture would take allot of time. I'd like to get FSPN up and operational and have its impact felt throughout the freesoftware community as fast as possible. Eventually, I do see a need to develop a new p2p architecture to support FSPN.