keybase / keybase/client

better team order management (feature request)

Open
#17,987 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Allow to change team order and save the order automatically across devices - this could be also configurable.
Another option: allow to pin favourite teams in top of team list. Also allow to change the order of favourite teams. Save settings across devices, for selected devices or for current device only - allow also configure that. Some people might prefer different favourites on different devices.
Currently teams are sorted automatically by their name and all channels are also always visible which makes the whole chat list very long and then I have to search all the time if I don't scroll them.
Would propose to collapse (fold) automatically inactive (unused) team channels - this could also make the list shorter - certainly this could be configurable option as some people probably prefer all to be unfolded. Several options:

  • collapse all channels regardless of reading status
  • collapse read channels but not unread
  • show unread channels automatically as uncollapsed
    There could be also setting that show favourite teams and chats only.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a file, test, or entry point. Start by locating the client code that renders the team and channel list and the existing settings or synchronization path; completion would require an agreed scope and design for ordering, favourites, collapsing, and device-specific persistence.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react, react-native
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.