I have a few very specific requests in relation to running multi-user server systems. 1. CLI option on Mac OS X - this is a deal breaker. I've heard some people say you don't need a command line option on OS X or Windows because you can do it all through the GUI. Obviously they've never run a server. For security and configuration reasons, I need BTSync running as a daemon as its own user, starting on boot without each user having to log in. Additionally, this process should be a standard process and NOT fork itself as the current Linux CLI version does. This is bad practice. Write a wrapper script to fork it if you need to, but DO NOT fork the main process and let it quit. This is fine for single instances, but for a robust setup it doesn't cut it. 2. Multiple users. I want one copy of BTSync, one web admin interface, and multiple user accounts. In my opinion, the BTSync app should be able to tie into UNIX user accounts for admin interface login. Users in wheel, for example, could turn individual users on and off, and normal users, if enabled, could log in with their credentials and administer folders that are accessible to them. This may require that files added to the folder have their group changed to the group that the BTSync daemon is running as, but this would not be a huge problem. (Indiscriminate users could run the daemon as root and avoid this requirement, though that would be... unwise.) There are a lot of little details here but that's the basic concept. 3. Download-only file access. This is more for personal use. I'd like to have a BTSync folder that stores all of my movies, archives, and other data that I only access infrequently. When I want to download one of them, I want to be able to pick the file instead of syncing the whole folder, and likewise for uploading. This would be a huge advantage, and based on how BTSync works I don't think it would be that difficult to do.
