wouldn't a better solution be instead of giving out your own primary plex username and password to anyone but your sellf. tell them to get their own free plex account and then you being the plex media server administrator "invite" their plex ID to share your library. Once you have correctly setup sharing you can then turn "sharing" ON and OFF when ever you like. If you find one particular member who you have shared your library to has gone and shared their own username and password, then you just punish that user by revoking your shared library from them. this will then prevent that particular user from seeing your library whilst still allowing the other members access.
My guess is that all people work like that, since that is the recommended practice (although it is a horrible GUI-experience for my kids having only shared content). However, what you propose (throwing people out of the shares) is only AFTER the fact and only IF you detect it. In the meantime people can really cause mayhem by overloading your server, and Plex really isn't equipped for locating the culprit so catching the real cause is very unlikely. If my server would be overloaded because of Plex, I personally wouldn't look for that as a cause directly because it runs many more processes. Even if Plex would be identified as the cause, the info on the streaming overview is not accurate: when my kids go in and out video's quickly, it literally shows tens of movies being streamed to one user, while there is only one client active. So an abusing guest is extremely difficult and timeconsuming to find.
And having a sane default of 1 concurrent stream per shared user would make a lot of sense, because that would prevent people from abusing their guest privileges. If that restriction could be lifted for specific cases, even better. But prevention of bad behaviour is way much better than measures after the fact since it saves the incredibly dull and timeconsuming task.
The server should protect itself against abusive guests...
Jaap
