Block and unblock contacts, and show the blocklist
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the Client::blocking() API in the pinned whatsapp-rust revision ae3cefd, which provides block, unblock, get_blocklist and is_blocked, then read AGENTS.md for the privacy rules on logs and tests. Find where the chat menu and contact details are built in ZapTide's GTK UI and where Preferences pages are defined. Done means block and unblock work from both places, a Blocked contacts list with unblock buttons appears under Preferences, the chat header shows a blocked state, and new strings have pt_BR translations. Cross-device sync needs a design decision first, so ask in the thread before implementing it.
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:
Client::blocking() offers block, unblock, get_blocklist and is_blocked.
What ZapTide does today
Nothing. There is no way to block a contact from ZapTide.
Proposed scope
- Add Block and Unblock to the chat menu and the contact details.
- Add a Blocked contacts list under Preferences, with an unblock button.
- Keep the list in sync across devices and show a blocked state in the chat header.
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 39m
- Merged PRs (30d)
- 28
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
-
Appimage ConventionsPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Appimage - Some icons are not showingPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
luminusOS/zaptide#77 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
luminusOS/zaptide#65 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
luminusOS/zaptide#63 · 10 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in luminusOS/zaptide
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
C-bug needs-triage O-UEFI T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug priority: P3 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
shep-pm/shep-kelpie#1332 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramensoftware/windhawk#1156 · 2 comments ·
-
area/cli complexity:trivial good first issue Stellar Wave test
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Externalize-Labs/externalize#23 ·
Maintainers usually reply within 1 day