LotusGuild/cinny
3
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases Wiki Activity

[decide] One-sentence "who can see this" line in room settings #133

New Issue
Closed
opened 2026-09-17 16:10:05 -04:00 by jared · 2 comments
jared commented 2026-09-17 16:10:05 -04:00
Owner
Copy Link
Copy Source

One line under the room name in Room Settings → General, no new controls: e.g. "Encrypted · Invite only · History visible to members since they joined" derived from m.room.encryption, m.room.join_rules, m.room.history_visibility. Existing chips (encryption/join-rule) already exist on the room preview card — reuse their wording so it's consistent.

Jared: "maybe — must not be bloat". Decide on the mock-up; if it adds a card or icons, drop it.

One line under the room name in Room Settings → General, no new controls: e.g. **"Encrypted · Invite only · History visible to members since they joined"** derived from `m.room.encryption`, `m.room.join_rules`, `m.room.history_visibility`. Existing chips (encryption/join-rule) already exist on the room preview card — reuse their wording so it's consistent. Jared: "maybe — must not be bloat". Decide on the mock-up; if it adds a card or icons, drop it.
vis133.png
6.1 KiB
vis133.png
jared added this to the Features 2026-Q4 milestone 2026-09-17 16:10:05 -04:00
jared added the enhancementpriority: lowuxarea: settings labels 2026-09-17 16:10:05 -04:00
jared self-assigned this 2026-09-17 16:10:05 -04:00
jared commented 2026-09-20 15:18:27 -04:00
Author
Owner
Copy Link
Copy Source

Mock-up built as the real thing (ad1cbcf7) so it can be judged in place — one T200 line under the room name in Room Settings → General, no card, no icons, no controls:

line

Wording reuses the preview-card chips ("Invite only", "Ask to join", "Restricted", "Anyone can join") and the history-visibility setting's meanings; spec defaults (invite-only, shared history) when a state event is absent. Unit-tested (utils/roomVisibilityLine.ts). If this reads as bloat, say so and I'll revert the one line — leaving the issue open for that call.

Mock-up built as the real thing (ad1cbcf7) so it can be judged in place — one `T200` line under the room name in Room Settings → General, no card, no icons, no controls: ![line](https://code.lotusguild.org/attachments/4befe074-9401-4d94-8a84-c31649e009d0) Wording reuses the preview-card chips ("Invite only", "Ask to join", "Restricted", "Anyone can join") and the history-visibility setting's meanings; spec defaults (invite-only, shared history) when a state event is absent. Unit-tested (`utils/roomVisibilityLine.ts`). If this reads as bloat, say so and I'll revert the one line — leaving the issue open for that call.
jared commented 2026-10-23 16:02:19 -04:00
Author
Owner
Copy Link
Copy Source

Owner decision (2026-10-23): keep the one-line summary under the room name in Room Settings → General (ad1cbcf7). Closing.

Owner decision (2026-10-23): **keep** the one-line summary under the room name in Room Settings → General (ad1cbcf7). Closing.
jared closed this issue 2026-10-23 16:02:20 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
a11y
Accessibility: keyboard, screen reader, contrast, motion
 area: appearance
Client area: appearance
 area: auth-session
Client area: auth-session
 area: build-ci
Client area: build-ci
 area: calls
Client area: calls
 area: desktop
Client area: desktop
 area: media
Client area: media
 area: messaging
Client area: messaging
 area: mobile
Client area: mobile
 area: moderation
Client area: moderation
 area: navigation
Client area: navigation
 area: notifications
Client area: notifications
 area: settings
Client area: settings
 area: threads
Client area: threads
 bug
Something is not working
 dependencies
Third-party package versions and advisories
 docs
README / LOTUS_* docs wrong or missing
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 needs-human-review
performance
Re-render storms, leaks, heavy work on hot paths
 planning
priority: critical
Data loss, security hole, or crash on a main path
 priority: high
Broken feature or serious usability problem
 priority: low
Minor issue or polish
 priority: medium
Wrong behaviour in an edge case or notable degradation
 qa
Manual QA: shipped, needs a human in a real environment
 question
More information is needed
 research
security
XSS, unsafe URLs, data leaks, auth/session
 tech-debt
Code health, dead code, fragile patterns
 ux
Usability or visual inconsistency
 wontfix
This won't be fixed
No labels area: settings enhancement priority: low ux
Milestone
No items
No Milestone Features 2026-Q4
Projects
Clear projects
No projects
Assignees
Clear assignees
cole (Cole Keller) jared (Jared Vititoe) nathan (Nathan Vititoe)
No Assignees jared
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: LotusGuild/cinny#133