Desktop: private project home channels show no lock icon in the sidebar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 86/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- desktop
Research direction
Start in desktop/src/features/channels/ui/ChannelGlyph.tsx and inspect the projectHome and private-visibility branches. Verify the sidebar rendering for a private project home channel, then update the presentation so its privacy remains visible without losing the project mark. Done means private project homes show a lock or private variant, while other channel icons remain unchanged.
Written by the indexing model from the issue text.
Description
What happens
A channel created with visibility: private that is also a project's home channel shows the project icon (folder + #) in the sidebar, with no lock. Private channels that are not project homes show the lock as expected. Looking at the sidebar, you can't tell that the project channel is private.
Observed in Buzz Desktop 0.5.25 (macOS): the channel's kind 9007 create event and a later kind 9002 update both carry ["visibility","private"], and the relay membership is restricted.
Why
In desktop/src/features/channels/ui/ChannelGlyph.tsx, projectHome is checked first and returns early, so the visibility === "private" branch is never reached for project homes:
if (projectHome) {
return <ProjectChannelIcon className={iconClass} />;
}
if (channel.visibility === "private") {
return <Lock className={iconClass} />;
}
Suggestion
Show privacy on project homes as well, for example with a small lock badge on ProjectChannelIcon when channel.visibility === "private", or a private variant of the project icon. Privacy is the more safety-relevant signal of the two, so it shouldn't be hidden by the project mark.
- Dominant language
- Rust
- Stars
- 33.7k
- Forks
- 4.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 189
Getting set up
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.
More from block/buzz
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
block/buzz#7880 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
block/buzz#7824 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-challenge/player_rust#22 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
foundry-rs/foundry#17175 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github/copilot-sdk#2793 ·
Maintainers usually reply within 1 day