Multi-user remote access / web interface

[bayxsonic]

I was considering using Transmission on a "server" and let my family use it via its web interface.
It would be nice if user A would only see user A's downloads and not everyone's. Perhaps it could be done via automatic groups, inheriting their "custom location" feature.

Example:
group LUCY, password 0123, location: /users/Lucy/Downloads/ (location manually set)
group MARK, password 3210, location: /users/Mark/Downloads/

[Ruroniarc]

I see this as a very important feature, I haven't looked at the code yet (and I don't know how to program Ajax and Jscript), but I would like to see this rolled out.

The feature should definitely include that each user can't see the other users torrents, and that you can set directories for each user. They should also be able to download their files remotely via HTTP.

Another thing that isn't AS important, would be quotas for each specific user, both in actually space, and bandwidth.

[starmoon]

multiuser support is good idea.

every user has configable download commit location(s).

[lazybones]

Would be great to use with the various Front ends out there... Running more than one bittorent client in a home network almost always kills the network, being able to setup one instance with one global set of bandwidth settings and port mappings would be very nice.


The system would also have to cope with duplicates... What happens if user A downloads a torrent to their default download folder then user B tries to grab the same torrent? Should transmission make two file copies in different locations? What happens if one user cancels the torrent?

[starmoon]

if one user cancels the torrent?

both users cancle, the jobs will cancel.

when finished. make copies for each user (or hardlink for each user)

[kintaro]

any news about multi user remote access?

[Rolcol]

It probably won't happen. Transmission is meant to be a single user application.