Re: nodes caching frequently requested files

--===============1914628130==
Content-Type: multipart/signed;
  boundary="nextPart2584637.LLPstfRBnA";
  protocol="application/pgp-signature";
  micalg=pgp-sha256
Content-Transfer-Encoding: 7bit

--nextPart2584637.LLPstfRBnA
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Monday 18 Apr 2011 22:02:05 Jan wrote:
>=20
> Hi,
>=20
> I'm completely new to freenet, actually I had this idea and someone told
> me that this already exists. Awesome! So I'm not sure if this is done
> already, I couldn't find anything on this. My idea is that if there are
> seedboxes (sry I'm from the bt world, dunno how you call them), and, say,
> 50GB of free disk space, and there is this new episode of, say, Pioneer
> One,=20

Looked up, since legally we have to ban from support anyone who we believe =
to be engaged in piracy. A free TV series, cool!

> and every 30 minutes he has to route the very same file. Couldn't we
> implement the option to cache that file so other nodes are less seizured
> and the file gets more seeders. The same technique could be used to keep
> files with few seeders alive, of cause. Is this already implemented? If
> not, what do you think of the idea?

Yes, this is how Freenet works.

There are several caches:
=2D The store caches data that is close to the node's specialisation, when =
it is inserted, on roughly 3 nodes for every block insert.
=2D The cache caches everything. Both the cache and the store ignore anythi=
ng at very high HTL, for security reasons.
=2D The ULPR/slashdot cache caches everything but for a very short period (=
or in some security levels it caches less than that).
=2D The client cache caches stuff you have personally requested. Obviously =
this is sensitive security-wise, but it improves security on the network le=
vel as well as performance. So it can be encrypted with a password; we ask =
about this on install.

=46reenet does not have seeders. Popular files are automatically cached eve=
rywhere, so get very fast. We can get 50KB/sec or more download for a very =
popular file on a good day. Files which are old and not very popular, on th=
e other hand, can be very slow, or not be findable at all. Data persistence=
 for older files has however improved significantly over the past year, in =
spite of a (probably justified) public perception that downloads have slowe=
d down (although this has recovered somewhat recently).

--nextPart2584637.LLPstfRBnA
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABEIAAYFAk2tlCYACgkQYUNbc3WUHYjZ1ACgna4pQOYfev05KW1PbNijjons
6RoAmwWrkF/fAOzMVyVI28mdb5QipybG
=yCav
-----END PGP SIGNATURE-----

--nextPart2584637.LLPstfRBnA--

--===============1914628130==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Tech mailing list
[email protected]
http://freenetproject.org/cgi-bin/mailman/listinfo/tech
--===============1914628130==--