Currently, private sessions are just unlisted. They rely on being accessed via their encoded "session_locator" which uses HashIds, do not show up in the lobby unless you are the owner, and have no password. The idea is someone will send their friend the link, and others won't just be able to make a new session and then subtract 1 from the ID in the URL to find the unlisted room.
Because of this, the idea of "session_locator"s is confusing. There are a few potentially better solutions:
Make sessions use UUIDs, and keep unlisted sessions as unlisted
Make private rooms which are password-protected, and show them on the lobby
I prefer 2 because if I think about logging on to find my friend's private session, my friend would not even need to tell me the name or password because it can be repeated, and I can just find the session when I'm in the lobby.
Currently, private sessions are just unlisted. They rely on being accessed via their encoded "session_locator" which uses
HashIds, do not show up in the lobby unless you are the owner, and have no password. The idea is someone will send their friend the link, and others won't just be able to make a new session and then subtract 1 from the ID in the URL to find the unlisted room.Because of this, the idea of "session_locator"s is confusing. There are a few potentially better solutions:
I prefer 2 because if I think about logging on to find my friend's private session, my friend would not even need to tell me the name or password because it can be repeated, and I can just find the session when I'm in the lobby.