-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Labels
branchedFeature request is assigned to it's on branchFeature request is assigned to it's on branchenhancementNew feature or requestNew feature or requestin-progressIssue/Feature acknowledged and being worked on.Issue/Feature acknowledged and being worked on.
Description
Problem Statement
As service been deployed on a home server and only few stable users are involved We are bored to deal with session IDs and have to share party code each time room being recreated.
Proposed Solution
add env bool variable flag to switch service in single static session mode
-
first user enters base service URL - automatically creates session with some static ID - 000000 for example and enters the room
-
while session not expired any user who entered base URL - joins this session automatically with only name request popups
-
session expires with standard rule and ect ect
-
as a bonus some static user names are also appreciated
Alternatives Considered
No response
Feature Category
Configuration
Priority (Your Opinion)
Low - Nice to have
Use Case
No response
Additional Context
No response
Checklist
- I have checked the existing issues to make sure this is not a duplicate
- This feature aligns with the project's goals
- I would be willing to help implement this feature
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
branchedFeature request is assigned to it's on branchFeature request is assigned to it's on branchenhancementNew feature or requestNew feature or requestin-progressIssue/Feature acknowledged and being worked on.Issue/Feature acknowledged and being worked on.