Better default access control
1) Suppose that the kids have a renderer whose IP address is 192.168.1.54 and that dad has set its group membership to "Limited Access"
2) Dad has also set "Limited Access" to all the kid's cartoons folders, but dad has thoughtfully left his porn folder set to the default "No Restriction".
3) Kids cannot access dad's porn because their renderer is set to "Limited Access" and dad's porn does not have the "Limited Access" group. So far, so good, right?
4) One day, the DHCP lease on the kids renderer expires and it gets assigned a different IP address, say 192.168.1.55.
5) Serviio sets "No Restriction" for this renderer by default.
6) Wham! Kids start watching dad's porn. Now that's entertainment


This problem can be easily fixed by allowing dad to remove the "No Restriction" group from his porn. Here is how it would work:
1) Kid's renderer 192.168.1.54 is assigned the default "No Restriction"
2) Dad sets "No Restriction" on all cartoon folders. Dad removes "No Restriction" from his porn but adds "Limited Access".
3) Dad sets his renderer to "Limited Access" so he can watch his porn.
4) Kids cannot watch porn because their renderer is set to the default "No Restriction"
5) One day, the DHCP lease on the kids renderer expires and it gets assigned a different IP address, say 192.168.1.55. But that's OK because Serviio assigns it "No restriction", so no elevation of privilege occurs.
Please add this feature. Specifically, allow dad to remove the "No Retriction" group from folders. That's all.
BTW, here is a different group naming scheme that fits better with this approach:
- Rename "No Restriction" to "General Audience" or "All Viewers".
- Rename "Limited Access" to "Mature Audience" or "Limited Audience" or "Select Audience".