On Fri, 18 May 2001 15:51:31 -0500 [EMAIL PROTECTED] writes:
>
> Guys!
>
> > Aaron P Ingebrigtsen ([EMAIL PROTECTED]) wrote:
> >
> >>> I personaly would really like some kind of Windows Explorer
> extension
> for
> >>> freenet that makes windows think that freenet is some kind of
> CD-R
> drive
> >>> or something, you know, write once, read only media.
> >
> >David McNab ([EMAIL PROTECTED]) wrote:
>
> >> Personally, I feel it's highly viable and desirable to implement
> a
> Windows
> >> virtual disk that interfaces with Freenet. I think Aaron was
> flamed most
> >> unfairly.
>
> > Greg Wooledge <[EMAIL PROTECTED]> wrote:
> > For what it's worth, I wasn't flaming Aaron -- just pointing out
> the
> > reason why it would be incredibly difficult to implement his
> wish.
> > As I said in the prior message, I think it would be a rather
> useful thing
> to have.
>
> OK, OK, this IS driving me crazy now. What Aaron wants, while not
> trivial,
> is also not too hard under Windows. It's called a shell name space
> extension. It is built as a Windows DLL using C++ and the MFC. It is
> then
> registered to run with IE's explorer tree. I have code that does
> this. The
> only problem is conceptual: How do you want to map freenet to a
> Windows
> explorer interface. This would be a fun project if someone has the
> idea for
> how the mapping might look. If anyone is interested (Aaron?), let me
> know
> what you interface ideas are.
>
> Jeff Furgal
Cool. :)
Ok, here is what I want, in more detail:
Every key in Steve's Key Index must be read each time the internet
connection is activated, but the internet must not be used if a
connection is not detected, this way it only connects to the site when
the user wants to be online. Then it should be able to read freenet, if
the freenet client is running. If niether the freenet client is running,
nor an internet connection is detected, then the Vdrive should not be
actively accessible from anywhere on windows. To try to access it would
bring up a warning dialog or something that tells the user to connect to
the internet and run the freenet client before opening the Freenet
Explorer Drive. Or something to that effect. It must also have the
ability to add keys to Steve's Key Index, but only if the user tells it
to, after being prompted, whenever a user inserts a file. The user
should be able to add a file to freenet under any of the "directories" in
the drive, but only if that user is able to plug in the private key when
prompted during an attempt to insert a file under an SSK. Perhaps it
should have the ability to keep a file handy for storing and retrieving
private keys, but the file should be encrypted with the user's own
password. Yes, passwords must be linked to the inserting of files under
any SSK. :)
And it would be nice if SSKs could have shortcuts pointing to them, just
like any other Windows file. Like when you create an SSK for the first
time, the interface creates a shortcut to that SSK calling it the name of
the user or something, like "Krepta's Freenet Subspace" or something.
This way the user can easily get to his/her own subspace without haveing
to remember his/her public key. Yes, the public/private keys should be
made to be in the background somehow, so that users don't HAVE to
remember them, or even have to see them unless they want to.
Also, the user might want to keep secret copies of thier personal
directory list, so make it so that the program can optionaly keep it's
own private keyindex when inserting files, so that these files can be
retrieved, but not by useing any of the keys on the public keylists.
Also make it so that backups of the users settings, encrypted private
keylist, and encrypted private key file for his/her SSKs, can be stored
and retrieved easily on freenet.
It is all well and good to create an interface that makes freenet look
like a drive, but it is more complex than simply listing directories and
file names from a keylist and retrieving files from freenet.
And last but not least, the vdrive MUST be mapped to a drive letter, and
windows MUST treat it as if it were a write-once/read-only disk drive, it
must not be treated like a conventional network drive, because most
networks allow you to write over files that have already been writen
there by that same user, and freenet does not allow this. Once you write
a file, it can't be deleted or overwriten, it can only be left there.
Perhaps you can setup a function that allows you to set a particular key
as invisible if you want it to be, map it to the delete function or
something. That way the system will not allow you to overwrite a file
even if you can't see it in the directory listing when viewing it
normaly. :)
Did I mention that I want this vdrive to be accessible from a DOS box in
windows? Yes, it must be mapped to a drive letter for that to work.
Make it so it takes the next available drive letter, just like a CD-R
drive. :)
Also, when creating directories on the vdrive you would need to have it
insert some kind of generic key onto freenet which would mean inserting a
file. When I created my SSK I just inserted hello.txt, which contained
only the text :"hello". You can do the same thing for creating a
directory on freenet under which you wish to put multiple files. :)
I don't think you need to keep a local cache of anything, freenet handles
that already.
________________________________________________________________
GET INTERNET ACCESS FROM JUNO!
Juno offers FREE or PREMIUM Internet access for less!
Join Juno today! For your FREE software, visit:
http://dl.www.juno.com/get/tagj.
_______________________________________________
Chat mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/chat
