keybase / keybase/client

Readonly channels

Open
#10,529 1 comment 0 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

Hi,
At the moment readers and writers can add to the chat in a channel. The reader and writer states applies to the file system (if I am correct). Sometimes we want to have "info only" channels where the admin/owner can add messages to the chat but no other person can chat in (to keep the information channel clean).
We could solve this with making everyone reader for a team and placing all the information in a text file. It would be far more accessible though if we could mark a channel as "info only" channel.

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 names no files, tests, or entry points. Start by tracing how channel membership and posting permissions are handled, then determine how an info-only channel should identify its owner or admins. Done means a channel can be marked read-only while permitted administrators can still post.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.