Re: The future of the file-sharing service

[TheJackiMonster]

On Mon, 2022-09-19 at 23:45 +0100, madmurphy wrote:
> Forgot about this:
> On Mon, Sep 19, 2022 at 9:06 PM TheJackiMonster
> <thejackimonster@gmail.com> wrote:
> > Also I would like to see git over GNUnet FS or CADET (depends on
> > what makes more sense). Because when I think about the autoshare
> > functionality, I already start thinking about syncing files between
> > devices which can cause conflicts.
> That seems like a complex task, which maybe could be accomplished by
> a further service on top of FS (something like “FSGIT”)?

I assume a service on top of FS and CADET would make sense. So you
could accept public keys from other identities or peers to push commits
onto some of your local branches. Local changes would then be indexed
and published with FS to be shared.

Anyway I generally just like the idea that we could use GNUnet for
contribution instead of the current central servers.

I think it would make sense to allow signatures added to the files (via
metadata or file-information). Because in some cases it might make
sense to verify the author of a file. For example auto-sharing a
directory with binary releases of an application.

> 
> On Mon, Sep 19, 2022 at 11:39 PM madmurphy <madmurphy333@gmail.com>
> wrote:
> > Here is the list updated with Jacki's suggestion and a further
> > point from me I had forgotten to mention…
> >    1. Possibility of sharing a file while it is still being
> > downloaded (parts of it, of course)
> >    2. Metadata must be editable and sharable
> >    3. Search keywords must be visible, editable, sharable (part of
> > the metadata?)
> >    4. Introduction of a rating mechanism for files (against spam)
> >    5. Allow reverse search (i.e. chk-URI lookup)
> >    6. Automatically and fully auto-unindex a file when it is
> > missing
> >    7. Autoshare the dynamic content of a directory and update its
> > index in real time (e.g. if I “autoshare” the content of
> > /srv/filesharing/gnunet/madmurphy/, when I add foobar.txt to that
> > directory it must be automatically indexed – the opposite if I
> > remove it)
> >    8. Implement file statistics (download counter? last seen? etc.)
> > – this should allow the network to get rid easily of “lost” content
> >    9. Implement a NOT operator for search keywords (a tilde, “~”?)
> >   10. Implement an OR operator (a vertical bar, “|”? currently not
> > writing any operator equals OR, but we need an explicit OR operator
> > if we want to implement the next point)
> >   11. Allow parenthesis parsing for AND/OR/NOT operators; this will
> > require that operators can be followed by spaces (e.g. gnunet-
> > search +required '+' '(' optional1 '|' optional2 ')')
> >   12. The output filename must become optional in gnunet-download.
> > If not specified, the file/directory must be downloaded using the
> > original filename it was published with – if currently this
> > information is not always saved during publishing, then we must
> > make sure that it is always saved (this is part of the metadata too
> > and must be editable)
> >   13. “Private file sharing so that URIs don't reveal the actual
> > hash and the actual file size. So either the data in the URI or
> > file needs to be encrypted with a symmetric key” (Jacki)
> >   14. Local operations must not require the GNUnet services to be
> > running (e.g.: querying the list of indexed files)
> > On Mon, Sep 19, 2022 at 9:50 PM Luis Soeiro <lfl.sl@soeiro.com.br>
> > wrote:
> > > >    1. Metadata must be editable and sharable
> > > >    2. Search keywords must be visible, editable, sharable (part
> > > > of the metadata?)
> > > Hummm. Ok. But would it lead to spammers?
> > Hi Luis, the rating mechanism will prevent that.
> > On Mon, Sep 19, 2022 at 9:50 PM Luis Soeiro <lfl.sl@soeiro.com.br>
> > wrote:
> > > >    1. Allow reverse search (i.e. chk-URI lookup)
> > > This might be troublesome. Imagine if some entity is looking for
> > > people who might donwload some special file (a planted file or an
> > > unauthorized file). That entity might try to locate the URI and
> > > then the users by looking at the pieces...
> > That should be prevented by the network even if chk-URI lookup is
> > allowed…
> > 
> > --madmurphy
> > 
> > On Mon, Sep 19, 2022 at 9:50 PM Luis Soeiro <lfl.sl@soeiro.com.br>
> > wrote:
> > > Hello
> > > 
> > > Em 2022-09-19 20:42, madmurphy escreveu:
> > > 
> > > > What FS needs to have:
> > > > 
> > > > * Possibility of sharing a file while it is still being
> > > > downloaded 
> > > > (parts of it, of course)
> > > 
> > > That would be interesting. It would be cool to have it swarm the
> > > pieces 
> > > (like torrent)...
> > > 
> > > > * Metadata must be editable and sharable
> > > > * Search keywords must be visible, editable, sharable (part of
> > > > the 
> > > > metadata?)
> > > 
> > > Hummm. Ok. But would it lead to spammers?
> > > 
> > > > * Introduction of a rating mechanism for files (against spam)
> > > 
> > > +1
> > > 
> > > > * Allow reverse search (i.e. chk-URI lookup)
> > > 
> > > This might be troublesome. Imagine if some entity is looking for
> > > people 
> > > who might donwload some special file (a planted file or an
> > > unauthorized 
> > > file). That entity might try to locate the URI and then the users
> > > by 
> > > looking at the pieces...
> > > 
> > > > * Automatically and fully auto-unindex a file when it is
> > > > missing
> > > > * Autoshare the dynamic content of a directory and update its
> > > > index in 
> > > > real time (e.g. if I "autoshare" the content of 
> > > > /srv/filesharing/gnunet/madmurphy/, when I add foobar.txt to
> > > > that 
> > > > directory it must be automatically indexed - the opposite if I
> > > > remove 
> > > > it)
> > > > * Implement file statistics (download counter? last seen? etc.)
> > > > - this 
> > > > should allow the network to get rid easily of "lost" content
> > > > * Implement a NOT operator for search keywords (a tilde, "~"?)
> > > > * Implement an OR operator (a vertical bar, "|"? currently not
> > > > writing 
> > > > any operator equals OR, but we need an explicit OR operator if
> > > > we want 
> > > > to implement the next point)
> > > > * Allow parenthesis parsing for AND/OR/NOT operators; this will
> > > > require 
> > > > that operators can be followed by spaces (e.g. gnunet-search
> > > > +required 
> > > > '+' '(' optional1 '|' optional2 ')')
> > > > * The output filename must become optional in gnunet-download.
> > > > If not 
> > > > specified, the file/directory must be downloaded using the
> > > > original 
> > > > filename it was published with - if currently this information
> > > > is not 
> > > > always saved during publishing, then we must make sure that it
> > > > is 
> > > > always saved (this is part of the metadata too and must be
> > > > editable)
> > > 
> > > +1
> > > 
> > > []s,
> > > Luis
> > >

signature.asc
Description: This is a digitally signed message part