Re: [Blocks-development] Doh!

[Blat F. <pet...@ho...>]

>From: "Benjamin M. Brewer" <br...@kr...>
>To: Blat Froop <pet...@ho...>
>CC: blo...@li...
>Subject: Re: [Blocks-development] Doh!
>Date: Mon, 31 Jul 2000 22:01:21 -0400 (EDT)
>
>Comment are below in the 'correct sections'.
>
>On Tue, 1 Aug 2000, Blat Froop wrote:
>
> > Hi,
> >
> > well I thought it was getting a bit quieter on the email front...
> > I didnt realise that I actually had to *join* the mailing list
> > after I set it up! But Im here now :-)
> >
> > Ive had a quick look through the archive and heres some brief
> > comments :-
> >
> > 1) We need that ability to upload multiple files.
> >
> >     Agreed. I also need to fix the problem that everything stops
> >     while a file is uploaded. Another possibility is a(possibly
> > command line based) injection tool for injecting content into
> >     servers.
> >
>Perhaps if there was a simple 'upload' directory within the blocks
>dir? You could just mv/cp files into the directory at one time, and then
>hit a button within the blocksgui to READ that upload dir to see if any
>files were in there?

More likely I'll try and add a 'choose directory to upload' menuitem until I 
can get around to building an upload widget.

>
> > 2) Sticky local files.
> >
> >    Seems so obvious I wonder why I never thought of it. I dont
> >    want to have too much complexity on the cache maintenance side
> >    if I can avoid it, but adding a sticky bit is a possibility.
> >
> > 3) Should we readvertise proxied files?
> >
> >    Well it does at the moment. If you switch off 'readvertise files'
> >    people cant connect and browse your cache anyway. 'Deniablilty'
> >    is always there since you didnt upload these files anyway...
> >    its the same problem if you were to run a public HTTP Proxy
> >    (Squid or whatever). Routes do get 'unadvertised' when a
> >    connection is broken so content may become inaccssible.
> >    I could add another option covering this but would it really be
> >    useful?
>
>Yes. Although this system is NOT designed for the modem users, they will
>obviously become interested in the protocol / application, so they can get
>their mp3 'fix'. :)  We should _not_ leave them out, even though their
>usage of the network may not be desirable on their end.

Hmmm... dunno modemers simply dont have the bandwidth for
to broadcast file advertisements, and all the joining and
disconnecting creates a lot of routing traffic.

>
> > 4) Authentication and Ratings
> >
> >    Im quite interested in crypto, and a rating system is an
> >    interesting idea. However, I dont want to increase the size
> >    of File Adverts by including public keys, descriptions, and
> >    so on. Now, if there were a seperate system (maybe even
> >    web based) that Blocks could access information from
> >    using the file ID (hash sent with ad) that would be a very
> >    different story. Another possible future option would be
> >    to seperate out the server code and build something like
> >    a library (maybe even ActiveX control) to allow much more
> >    complex custom front ends (you might have noticed they
> >    arent really my speciality) that allow extended functionality.
>
>Idea! I was just playing with gnoRPM (A gnome frontend to the RPM package
>format) and I liked how it worked. When you clicked on a file, and quickly
>connected to that location and downloaded information about the file in
>question. Blocknet could do the same thing. This request for information
>would only be sent to the sender of the file, and since the sender will
>get 'connected to' anyways to download the file, we are not losing any
>privacy that we currently have.
>
>Have it so you highlight a file in the search list, and then hit the 'more
>info' button, or something similar, and THEN the varifying information can
>be sent - per request.

How much information (in bytes) do you estimate would be required
as a minimum to be associated with File Adverts to add public keys
and whatever else would be needed?

There is the option of having a second block of descriptive info.

I still have to get my head around how these things would work.

>
> > 5) Logos
> >
> >    The 2 Logos on the web page are the winners. These are now
> >    the Blocks logos for the foreseeable future.
>
>Not sure if you noticed the colorized version of the 'other logo' (the one
>that isn't mine...), it is much better, and if you wish, I can add that
>one instead...

Done.

>
> > 6) IRC
> >
> >    As long as Flaggovic hold #blocks open on DALNet I'll
> >    keep it listed. I may change the order to list EFNet first
> >    if its more popular.
> >
>
>DALNet is crap =\ I think it should mainly be based on EFnet, but that's
>just personal opinion.

DALNEt is dead, long live EFNet.

>
>PS, did you get those linux-binaries?

On new page!

ttfn

PG.

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com