[Blocks-development] fake local networks? Blocks as a backend for other services?

[Spencer Jr., M. <sp...@ac...>]

It's looking like these Blocks servers won't be lightweight
connect-search-disconnect clients.  A significant number (but not a
majority) will probably be run by people with bandwidth and clue.

With that in mind, here's a silly idea that I haven't given much thought to:

for anonymity, eventually, maybe when we make Blocks client/server, if we
choose to go that route...why not make it an option to run multiple Blocks
server locally, and manage them all in one GUI!  You could even add fake
latency and bandwidth between the local servers, so they appear to be on
other machines.


While I'm at it...
if all of this web-of-trust stuff gets implemented well sometime down the
road...I suppose you could have a closed network of clients merely used as a
distributed 'disk dump' for a different service:  you connect to an FTP
server and download files, and the files are coming from a closed Blocks
network for example.

Filesystem driver for Blocks?  (mount -t blocksfs -o
cache=4,rate=32768,listen=9912 /home/ftp 209.180.104.202:91)

Perhaps have an /unsigned directory for content that hasn't been signed, and
have people 'own' certain directories with crypto keys...and files are
assigned to directories by signing the files.  I don't know...could be cool.
And these directory and key assignments could be made per-server in
/etc/blocksfs.conf or something like that.  :)

--Michael Spencer
bl...@ms...

-----Original Message-----
From: Blat Froop [mailto:pet...@ho...]
Sent: Friday, August 04, 2000 8:34 AM
To: blo...@li...
Subject: [Blocks-development] V0.15 readvertisement of locally cache
files


Here is an idea...

at the moment the V0.15 is going to readvertise the most
recent 1024 non-local file advertisements to newly connected
servers. Local files are not rebroadcast in order to stop
people connecting to see what you are serving directly.

So, what if I change it so that V0.15 makes up a bogus random
single character route for each locally cached file. Then
connecting clients wont be able to tell if the server has it
itself, or one immediately adjacent to it. The bogus route
will be valid since the server will intercept requests it
can furfill out of cache.

Comments?

ttfn

PG.

PS Other than this, and a quick check it still works on Solaris,
   V0.15 is pretty much done :)
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


_______________________________________________
Blocks-development mailing list
Blo...@li...
http://lists.sourceforge.net/mailman/listinfo/blocks-development