One Player in Use at Any Time

[OlYeller21]

Per this thread, I would like to request the ability to mark a person's account so that they can only use their account on one player at any one time to keep people from sharing their account.

A check in the admin setting for each account would be great. It seems that it would work best the newest play gets priority in case you leave your computer playing music at home, it won't keep you from listening at work (for example).

[m0ore4ustin391]

I second this request, would be a great feature to have.

[Cook66]

Keeping in the spirit of the thread I'd also like it to be possible to limit users to a specific device/player type and IP to further prohibit account sharing.

[nutt318]

+1

[OlYeller21]

I can't explain how much I would like to have this feature implemented. I currently have no way of getting people to not share their account information and have no one to tell, beyond any doubt, that a person has shared their information.

Again, as I mentioned in the other thread, I don't believe that anyone is sharing their information in a deceptive way. I think they just don't understand the cost or problem with doing that.

[GJ51]

It would require associating their external ip address with a single player for them. I'm pretty sure this wouldn'y work with a mobil device. It would also mean that if one of your users was on a laptop at a different location, they wouldn't have access. There would also be the issue of dealing with the ISP changing the users external ip.

This is a great idea, but I don't see any practical way to implement it without getting into some pretty sophisticated verification schemes that are probably not practical for an application like this.

I guess the reality is, if you don't trust someone to respect the privileges you're giving them, you might just be better off not giving them access.

[bushman4]

As Ed Crowley would say, "There are seldom good technological solutions to behavioral problems."

Glenn

[OlYeller21]

Gary,

I'm not really qualified to comment on this because I know relatively little about coding which is probably obvious since I call it "coding". I assumed that allowing only on IP to use the service per account would be enough to fix my problem. The way I see it, if their mobile device changes IPs, Subsonic would stop the player on the old IP and start it on the new IP. If they move from their laptop or desktop to their mobile device, the old player would be deleted or shut down and the new player would be used. I don't particularly care if it's a seamless transition and the user can deal with their current playlist being unavailable or deleted.

It's certainly possible that I'm not seeing the whole picture or don't have the expertise to understand the issues with implementing this kind of system.

Glenn & Gary,

You're right. My frist reaction was to just delete their accounts but it's a little more complicated than that for me. These are some of my best friends and I've known two of the three of them for about twenty years. The other, I've known for about ten years. They wouldn't do it if they understood that it's not like some Google website where it's an endless well of content and can handle infinite users.

I wish I had a better way to handle this but I explain on the log in screen the problem with sharing account info and it was ignored or not even read. I guess I either have to eat it, tell my friends to f-off, or come up with some story about how I had to get rid of Subsonic and just use it for myself.

[BKKKPewsey]

The trouble is with this issue is that there can be numerous reasons why the IP address can change, most of them mentioned in the previous posts,
however as SS does have rudimentary log-in procedures in place I cannot see why SS cannot limit the number of simultaneous log-ins by the same user.
I would suggest 2 max but an admin defined amount would be better.
EG BILL logs in with lappie at work, checks library, powers up phone (different IP), downloads music for journey home.
If Bill forgets to log off from work then when he get home and logs on via home pc. SS automatically say's whey!! already logged twice so logs off Bill from work.
Now if Bill isn't the friend you thought and has shared his log-in details then when Bill(2) logs in he will log of Bill(1).
After a while they will both get very seriously p***ed off with this situation or by means of natural selection will resolve the matter so we are left with just 1 Bill
But the end result is your bandwidth is saved

[OlYeller21]

The trouble is with this issue is that there can be numerous reasons why the IP address can change, most of them mentioned in the previous posts,
however as SS does have rudimentary log-in procedures in place I cannot see why SS cannot limit the number of simultaneous log-ins by the same user.
I would suggest 2 max but an admin defined amount would be better.
EG BILL logs in with lappie at work, checks library, powers up phone (different IP), downloads music for journey home.
If Bill forgets to log off from work then when he get home and logs on via home pc. SS automatically say's whey!! already logged twice so logs off Bill from work.
Now if Bill isn't the friend you thought and has shared his log-in details then when Bill(2) logs in he will log of Bill(1).
After a while they will both get very seriously p***ed off with this situation or by means of natural selection will resolve the matter so we are left with just 1 Bill
But the end result is your bandwidth is saved

This is exactly what I had in mind but again, I'm not proficient enough to know if that's an option.