gnunet-developers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Keywords with file insertion


From: Bram Neijt
Subject: Re: [GNUnet-developers] Keywords with file insertion
Date: Sun, 23 Jan 2005 12:18:34 +0100

On Fri, 21 Jan 2005 22:25:59 +0100, milan <address@hidden> wrote:
> Yeah, that's my idea. ;-) GNUnet-GTK does a few keyword extraction, but
> doesn't organise keywords like it should. Indeed, I'm working on a form
> to insert audio easily and to add standard keywords (like ID3 and Vorbis
> comment's Title, Artist, Album, Date...) to the file descriptor in
> GNUnet AFS. This can be done without much problems now, but time. :-) I
> promise you I'll work on it more... See the attached screenshot to have
> an idea of what it can be... and give me your suggestions.
Wel, but this is more general then audio only, I was thinking about
adding extra hash information as keywords to allow ed2k links (that
contain an SHA4) to be resolved. This could also be done for some
other links by adding the SHA1 also. Adding the MD5 would allow some
files on the internet (which often have a .md5 sum file with them) te
be resolved.
Things like title, tracknumber and album should be added tot he
filename, I think, just as Nils mentions. The only thing that should
be added is a standard for doing this.
I've mailed Tom Barnes-Lewrence about his netiquettes for GNUnet
keywords, te see if he is willing to add things like this to his
documentation.

 
> So it could be added to the tag, no ?
This is not a bad idee, but the problem is, that once you add an MD5
to a file as a  tag in the ogg/mp3, the actual hash of the file
changes :-) And, furthermore, libextractor should not collect all tag
information and add them as keywords.
So, no I don't think adding the hash (any kind MD4/5 SHA1) to the
files tags is useful.

I'm going to wait a bit, see what Tom thinks. If you have any progress
or questions, you may also mail me personally.

Bram
address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]