Groups: manage members, admins, invite links and join requests
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start with the Groups methods listed in the issue, pinned at revision ae3cefd in whatsapp-rust, and with the privacy rules in AGENTS.md. The issue spans five separate features, so first agree with maintainers on a smaller first slice, such as read-only invite info. Done means the chosen slice works in the GTK4 client, has pt_BR strings, and leaves no message content in logs or tests.
Written by the indexing model from the issue text.
Description
A WhatsApp feature that whatsapp-rust already supports but ZapTide does not use yet.
What whatsapp-rust provides
Checked against the pinned revision ae3cefd:
Groups offers add_participants, remove_participants, promote_participants, demote_participants, get_invite_link, join_with_invite_code, join_with_invite_v4, get_invite_info, get_membership_requests, approve_membership_requests, reject_membership_requests and set_membership_approval.
What ZapTide does today
None of these are used. Only api.whatsapp.com/send links open a chat, and a group invite message is shown as unsupported content ("group invite").
Proposed scope
- Add and remove participants and promote or demote admins from the participant list.
- Show and copy the invite link, and revoke it.
- Open
chat.whatsapp.comlinks with a preview of the group and a Join button. - Render group invite messages with a Join button.
- List pending join requests for admins, with approve and reject.
Notes
The privacy rules in AGENTS.md apply: no message content in logs or tests. New strings need a pt_BR translation.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 1
- Avg merge
- 2h 17m
- Merged PRs (30d)
- 38
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 luminusOS/zaptide
-
bug
Difficulty 4/5 1-2 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
luminusOS/zaptide#88 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
luminusOS/zaptide#85 · 7 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
luminusOS/zaptide#84 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
luminusOS/zaptide#83 · 3 comments ·
Maintainers usually reply within 1 day
All issues in luminusOS/zaptide
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
swc-project/swc-next#1165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Alive24/shea-symphony#574 ·
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dev-five-git/devup-ui#879 ·
Maintainers usually reply within 11 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
farion1231/cc-switch#9038 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
FalkorDB/FalkorDB#3597 · 1 comment ·
Maintainers usually reply within 2 days