Delete chats and delete messages for me, and sync them from other devices
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- backend, desktop-dev
Research direction
Start with AGENTS.md for the privacy rules, then read the chat_actions functions delete_chat, clear_chat and delete_message_for_me and the three update events in the whatsapp-rust revision ae3cefd. Find where the existing delete-for-everyone action is wired into the chat and message menus, and where incoming events are handled in the archive code. Done means the two menu actions exist, the three events update the archive, new strings have pt_BR translations, and no message content reaches 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:
delete_chat, clear_chat and delete_message_for_me in chat_actions, and the events DeleteChatUpdate, ClearChatUpdate and DeleteMessageForMeUpdate.
What ZapTide does today
Only delete for everyone is available, and none of the three events are handled, so a chat deleted or cleared on the phone stays in ZapTide.
Proposed scope
- Add Delete chat and Clear chat to the chat menu, with the option to keep starred messages once #20 lands.
- Add Delete for me to the message menu.
- Apply the three events from other devices to the archive.
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 85/100
farion1231/cc-switch#8829 ·
Maintainers usually reply within 1 day
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
longbridge/gpui-kit#3677 ·
Maintainers usually reply within 1 day
-
E-pr-welcome
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
seanmonstar/reqwest#3121 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ilya-zlobintsev/LACT#1235 ·
Maintainers usually reply within 1 day