chorus2
chorus2 copied to clipboard
Option to disable Kodi player control (leave only Local)
An install can be used by multiple people at the same time, including remotely (through an HTTPS proxy).
At the moment, it is very easy to mistakenly start playing on the local player.
A very "simple" fix would be to have a localstorage option to hide the 'Kodi' tab entirely and ensure the interface is always set to 'Local'.
An even nicer feature would be to enforce that, based on URL hostname (if used outside of local network, there's no good reason to allow controlling Kodi, except to play pranks on unsuspecting partners by playing death metal at 3am…)
This is similar to what is outlined in #318, although less ambitious: until the JSON RPC API supports multiuser, global storage and the ability to control access based on user, this would already solve the problem from a usability perspective (without stopping a determined prankster, of course).
I have never participated in chorus2 dev (I'm a recent user), but I'd be willing to give it a try, especially if someone can hold my hand through the local dev setup (I have good fullstack experience, but never used Backbone JS).
essentially this feature request would hide all device level player controls and only leave the streaming support.