Repository navigation
feat(privacy): per-contact Always Single Tick and per-contact call blocking type - #877
Open
hozin-king wants to merge 1 commit into
Open
hozin-king wants to merge 1 commit into
hozin-king wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Two per-contact options in the Custom Privacy dialog (per contact, independent of the global settings):
Always Single Tick — a new toggle for one contact. When enabled, the sender always sees a single tick for messages sent to you from that contact only: both the delivered tick and the blue (read) tick are hidden for that contact. It does not follow the global Hide Delivered / Hide Blue Ticks settings and does not affect other contacts. Implemented as a new
AlwaysSingleTickkey in the per-contact privacy JSON, checked inHideSeenalongside the existing HideSeen / HideReceipt checks.Per-contact call blocking type — previously, Block Call in the per-contact dialog was only on/off and the blocking method always came from the global call type. Now, when Block Call is checked for a contact and OK is pressed, a type picker appears for that contact only: No internet (Calling), Busy, Not answered, or Unable to receive WhatsApp calls. The choice is saved as
BlockCallTypein the same per-contact JSON.CallPrivacyuses the per-contact type when set, and falls back to the global call type when it is unset, cancelled, or when Block Call is turned off for that contact.Files changed
CustomPrivacy.kt— new dialog item, per-contact type picker (shown only when Block Call is checked), save/clear helpers forBlockCallTypeHideSeen.kt—AlwaysSingleTickforces both receipt and seen hiding for that contactCallPrivacy.kt— per-contact reject type with fallback to the global call type (both incoming-call hooks)strings.xml/strings-id— EN and ID strings for Always Single TickTesting
Static checks only so far: edited files have balanced braces/parens and the string XMLs parse. Not yet tested on a device with a real WhatsApp install — happy to test further if the maintainer wants changes.
Based on upstream master
36c22aed(1.6.2).