From: [email protected]

Package: pytone
Version: 2.0.13-1
Severity: wishlist

As subject says, please add an option to dynamically hide inaccessible
files.


I need it for the following scenario:

An eco-village of 100 apartments share an Internet connection. I run a
server on the local network, used for thin clients and general storage.

Each user can (when implemented) do the following...:

* Access the server from Mac (netatalk) or Windows (samba)
* Boot into a session that Ogg's CD content and stores centrally
* Boot into an X11 session hooked onto the local soundcard
* Boot into a PyTone session...
* (more, like backup/restore snapshots of local storage)


The PyTone session do not ask for the usual login and password. Instead,
it looks for "authentication tokens" - USB sticks containing some shared secret.
When I am home, I plug my USB stick into my (completely silent VIA Eden)
thin client, and have access to all of my digitized music. My girlfriend
can do the same when she comes home.
The interesting part comes when I visit one or my friends, or better:
when some of us throws together a party: Then we plug in our USB sticks
in a USB hub, and can mix and match all of our music. When each of us
leaves the party (s)he simply unplugs her/his stick and that music is no
longer accessible.


My reason for not simply throwing all music in a collective bowl is
probably obvious: Copyright laws most places (including where I live: "Munks�g�rd", the largest eco-village in Denmark) do not allow free
sharing of (digitally copied) music.


I believe the only part of the above scenario I can't setup myself is
for PyTone to only present the user with what is allowed (dynamically
updated instead of rebuilding the backend database).

The simplest approach that I can think of (that is also reusable for
other purposes than PyTone) is to repeatedly stat all files/folders for
access rights. (I would then implement scripts to add/remove users from
the group accessible by PyTone). A better approach (and still reusable)
would be to add an "owner" field in the database and directly compare
against members of a system group, wether or not the object should be
shown. You can probably come up with a much nicer approach - but please
try to do it a way that can be reused for other purposes.


Hope you like the idea so much that you instantly come up with a cool
update to PyTone ;-)


Kind regards,


- Jonas

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)