On Sunday 28 Jul 2013 19:39:36 leuchtkaefer wrote:
> 
> >
> >> - add bookmarklet button so the user can  Indexes will further share with 
> >> other identities who may
> >
> >I do not understand this line.
> 
> Bookmarklet buttons are added to bookmarks bar in web browsers. It makes easy 
> to share some content, after pressing the button the current website URL is 
> load on the sharing form.

Interesting. We should do this for adding a bookmark, sharing with friends ... 
maybe adding it to our own index would be useful, but I thought our own index 
was more for files?
> 
> >> - have a list of terms showed by the input form, so the user can select 
> >> the topic (category) easily.
> 
> >I do not follow - you want to manually label the files with keywords? This 
> >is a good idea, but if they are multi-word there may be complications. 
> >Initially we can just index by words extracted from the description or 
> >filename?
> 
> At the moment I am not thinking in multi-word. Curate content means make 
> things simple. Multi-word will complicate things in a way I don't think it 
> will be helpful. Maybe you can think in the word as a channel. A curator 
> curates content for some specific channels, then he/she becomes an specialist 
> of such topic.

So you want to search for a single word topic? That doesn't sound very useful.

I was thinking more of typing in "Elephant's Dream" and getting a bunch of 
files containing that in their filename or description? [ Note that Elephant's 
Dream is a free creative commons licensed animated movie ].

Anyway, we can have the best of both worlds:
Library already supports multi-word matches and adjacent word matches.

All we need to do to support that here is include term numbers, just like in 
the Spider-generated indexes.

So e.g.:

Key: SSK@blah,blah,blah/elephants-dream-quad-hd.ogv
Title: Elephant's Dream Quad-HD
Description: A wierd free animation in quad HD
Tag: Free movie
Tag: Wierd animation
Format: video/ogg-theora
Length: 8000000000

All we have to do is enumerate the words, but insert gaps when we go from one 
indexable element to another. So e.g.:
0: elephants
1: dream
2: quad
3: hd
1000: elephant's
1001: dream
1002: quad
1003: hd
2000: free
2001: movie
3000: wierd
3001: animation

The purpose of the numerical gaps is to prevent e.g. "hd free" from matching: 
An adjacent word search will only match if it matches word n and word n+1.

This means your format should be fairly close to the existing Library format, 
although we can add some extra fields.
> 
> >> - Ideas for future work on the plugin (cannot estimate the amount of work 
> >> needed):
> >>      - search terms under indexes (search from trusted identities, use 
> >> some threshold)
> >
> >Right. This is key.

Note that we already have code for searching multiple indexes.
> >
> >>      - reuse indexes curated by other identities to generate new indexes.
> >
> >This is future stuff.

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

_______________________________________________
Devl mailing list
Devl@freenetproject.org
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to