RocketChat / RocketChat/Rocket.Chat
Show ratio of people who have read the message compared to total people in channel
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Rocket.Chat uses ticks to indicate the read receipts for the user. It is possible to see the list of people who have read the message from the "Info" popup, where the members are listed. To keep track of all people in the room who have read the messages, it would help to see an ratio of people who have read the message out of the total people in the room. It will help the room administrator / moderator to see in glance, if everyone are up to speed.
For example, if the room had 20 people in total and only 5 have read the last message, then the read receipt would show 5 / 20 (or 25% etc). This would be shown per message.
Steps to reproduce:
- view the message read receipt
Expected behavior:
Have an information how many people in the room have read your message in a glance.
Actual behavior:
Not shown.
Server Setup Information:
- Version of Rocket.Chat Server: 3.1.1
- Operating System: Linux
- Deployment Method: docker
- Number of Running Instances: 1
- DB Replicaset Oplog: disabled
- NodeJS Version: 12.18.4
- MongoDB Version: 4.0.17
Client Setup Information
- Desktop App or Browser Version: Desktop app 3.1.1
- Operating System: Linux
Additional context
Same in the web app and desktop app.
Relevant logs:
NA
Contributor guide
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
Start at the message read receipt and its "Info" popup in the web and desktop apps, then trace how the reader list and total channel membership are obtained. Done means each message's read-receipt view shows the number or percentage of readers relative to the total people in the room.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100