That's pretty slick looking and I do like the Watched Together concept. The problem with this is that it won't work well with actual Emby use for anyone other than the Admin's family.
Imagine if you gave access to a neighbor and setup two accounts for the husband & wife (Jane and John). How would Jane and John use this functionality since they aren't on your quick login screen? Even if they were, would you want Jane or John to see or get a full listing of all users on your system to pick from?
IMHO, for this to really useful we need the concept of multiple quick logins (groups). Then instead of logging in on a device with a specific user you login with a group name/password which then gives you access to all users in that group. The group of people would have their own Quick Login screen as well which could have their own Watch Together. This would also allow your brother/sister to have a full quick login for all members of their immediate family as well as use the Watch Together with just their family members.
So while I really like this feature I'd love to see multiple quick logins supported first via a group login then implement this functionality based on the group logged in. That would allow it to work like Netflix and would be quite powerful.
I would find this feature very useful, namely the ability to manage watch status based on who is actually watching
Most of the times i watch with the wife, sometimes each of us on our own.
Perhaps for a single household it would be acceptable to publish the names of all the users, indeed i would not share my system with anyone i wasnt more than happy to know all the usernames.
Although this feature (as others have said) has to be exceeding simple , ultimately the 'joining user' has to authenticate to be part of the group (lest someone else 'corrupts' their watched status).
perhaps borrowing other suggestions the right balance is
- give the publishing user the ability to define the circumstances they are happy to publish but opt out on specific instances
- allow the joining user to control when and how their watched history is updated (within the boundaries of the publishing users preferences) as easily as possible.
- adding specific "recently watched views" [to tv and movies especially] would go a very long way to clear up mistakes quickly and easily.
- 1st stage may not require any app coding, the server could control the process completely.
[dont take the wording literally its just to help articulate the idea]
1. A user profile setting "'make me a publishing user' - allow other users to see my username and watch history"
2. a web ui eg for use on a phone which allows a 'joining user' to join an existing media playback instance (of participating 'publishing users' above) on a existing device to align their watch history.
List the publishing users
and the published media current playing by device..
- Align my watch history for current media only
- Align my watch history with this user's published content, until i say otherwise
- Align my watch history with this user' published content on this device, until i say otherwise
List the current active alignments, and option
- remove this alignment
- toggle on/off [default] sync unwatch as well (as opposed to watched)
and perhaps for privacy/security/age classification [i dont think this an early requirement, but for parents with children it might become one]
- a UI setting to allow the publishing user to easily 'go private/public' and not broadcast watched history
- an indicator on the screen to remind the 'publishing user' that their watched history is shared (potentially and/or actually)
- a user profile setting/ default - Do not share watched history on media above the age classification of the joining user.
- a user profile setting to define which libraries they wish to share their watched history for - all or by library
- a user profile setting to define which users you are happy to share with - all or by user - (only show users who have agreed to participate in their profile)
- a user profile setting to define which devices you are happy to share from - all or by device currently known to server
the ability for the publishing user to send out an invite for current media only, for the joining user to easily approve (like a 2FA authenticator app) (override all publishing preferences for this 'onetime' share)
the ability to join/specify alignments from within the client apps themselves [although its possibly easier for coder and users to drive this all from web ui to server on phone for both publisher and joiner]
the creation of static groups (although simple for some basic use cases) i dont think meets the granularity of the requirements for publisher and joiner..
on 2nd thoughts the group idea can be accommodated
- users are allowed to create groups linked to their account to 'offer a spaces' to one or more users,
- groups are like users with the privileges of the creating user, with a password with group name %creating user%_Name
- amend the web ui to allow joining users to also align/unalign to groups
- have an admin interface to control joining/alignment (on behalf of kids)
- logging on to a client app as a 'group', shows the library \ watched status of the creating user, and updates the watched status of the members of the group on media playback.
- Aligning to a group overrides all publishing and joining preferences and necessitates update of watched status for members of the group.
- again the server could do all the heavy lifting without the clients needing to be aware.
you could logon as a predefined group (using group idea)...or the joining user can join the publishing user ad hoc (using the publisher/joiner idea)
Edited by ginjaninja, 18 March 2019 - 03:37 AM.