Implement Quoroom
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 20
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
During beta, channels are owned by their creating browser fingerprint which can terminate/lock them. Since we have no user authentication this is quite ephemeral to the same session and assuming all rooms will be wiped when the last participant leaves. A potential idea is to add an option for rooms to be self governed by the current majority using a quoroom approach - where the mob can act as an admin effectively. An organized anarchy?
- force-muting or kicking out someone? vote.
- renaming or terminating the channel? vote.
Ideas?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing how channel ownership, browser fingerprints, and the listed admin actions currently work, then clarify the voting rules for force-muting, kicking, renaming, and termination. Done requires an agreed quoroom design and tests covering majority decisions and the last-participant case.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100