Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Store a Room Operator password #216

Open
jimmydorry opened this Issue Feb 1, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@jimmydorry
Copy link

jimmydorry commented Feb 1, 2019

It would be nice to be able to store a Server Operator password and automatically authenticate on SyncPlay start. It's a bit of a hassle to store it elsewhere, and manually copy+paste to authenticate each time you join a managed room.

The stored password would correspond with the default room you have saved in your client configuration.

For people that have the OP password, and want to join the channel as a non-op, they could just restart syncplay and clear their saved password in the configuration before re-joining the server.

The lack of this kind of functionality is only a small hassle in an otherwise great user experience.

@Et0h Et0h added the enhancement label Feb 1, 2019

@Et0h

This comment has been minimized.

Copy link
Contributor

Et0h commented Feb 1, 2019

I think some way of storing room password would be really helpful for people who use managed room (what % of Syncplay users is that? Not sure).

The question of implementation is perhaps a tricky one. I am not sure that having it as part of the default room is the best way to do it because I can imagine circumstances where people are involved in more than one room. However, , if we start going into a whole password manager then it might be more useful if it were a broader 'favourites' facility to make it easier for users to go back to their favourite rooms. This sounds useful and less hacky, but would be more time consuming to develop especially in terms of the correct UI to make it not clutter things up.

What are people's thoughts on this? I don't use managed rooms feature, so getting feedback from people who do would be really helpful.

@jimmydorry

This comment has been minimized.

Copy link
Author

jimmydorry commented Feb 1, 2019

I use a managed room almost every day, with 3-12 people participating (as non-operators) in each session. As you said, the less hacky system of favourites will be more cumbersome to implement, but a functionally better solution.

I'm in support of any improvement in this area.

@Dimonchyk777

This comment has been minimized.

Copy link

Dimonchyk777 commented Feb 1, 2019

I agree with jimmydorry here. I think we should have an option to automatically identify as a room operator. Instead of copying and pasting the password every time.

@Et0h

This comment has been minimized.

Copy link
Contributor

Et0h commented Feb 1, 2019

I don't really have any 'user stories' for how managed rooms are actually used and how operators behave. To what extent does someone who is sometimes a room operator want to always be identified as such, and to what extend would they want it to be 'on demand'? Do people actually want the ability to 'unidentify' as a room operator half way through a viewing session? If so, why?

@jimmydorry

This comment has been minimized.

Copy link
Author

jimmydorry commented Feb 1, 2019

For the room I manage at least, it's typically a once-off decision at the start of the session. There are two people that can OP in my room. In that room at least, we only want one operator, to make running things simpler.

If one of us wants to de-OP after seeing there is already another OP, it's easy enough to just restart syncplay, but it's never really been an issue in our usage.

For myself at least, I'm almost always the OP, so I always end up authenticating. The other guy ends up authenticating when I'm not part of the session... or he makes his own room.

I hope that helps. I'm sure there is a wide variety of uses of SyncPlay, so I'm not sure if mine is typical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.