- Rework the quik wire format: the visible body is now an iOS-style
fallback ("Reacted 👍 to \"...\"" or "Reacted 👍 to a message") and the
machine data (emoji, sender address, timestamp, text) is hidden in a
zero-width payload using U+2061..U+2064 so it never collides with the
iOS/Google tapback characters. Non-quik clients see a clean sentence.
- Fix swipe-to-react: the message item touch listener no longer consumes
events, so the RecyclerView's ItemTouchHelper receives swipes again.
- Restore long-press to select messages (removed long-press-to-react).
- Always hide our own outgoing reaction, even when the target message
can't be resolved locally, so the sender never sees the raw payload.
- Tune the reaction picker popup: theme-tinted background, themed text,
smaller emoji, and width capped to the screen so all options fit
without horizontal scrolling.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Address review findings on the send-reaction feature:
- Run permission checks on the main thread and only switch to IO for the
actual send, instead of touching the UI from a background thread.
- Parse outgoing reactions on the sender's own device. Sent messages don't
arrive back as incoming, so they would otherwise never be attached or
hidden until a full reparse.
- Anchor the reaction picker above the long-pressed message instead of
centering it on the screen, falling back to the list when off-screen.
- Always send reactions as group MMS in a group thread.
- Attribute our own reactions to our own number (via isMe + getMyPhoneNumber)
rather than the recipient's address, and show "Me" for them in the
reactions dialog.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Long-press a message to open an emoji reaction picker. Reactions are
sent as a plain SMS/MMS body using a quik-specific zero-width encoding
that carries the original sender's address and the message's timestamp,
so a receiving quik instance can attach the reaction to the exact
message via address + date lookup (fast path), falling back to the
existing text matching for non-quik senders.
The quik pattern is registered first so it wins over the generic Google
Messages pattern; iOS/Google parsing is unchanged. New ParsedEmojiReaction
fields are in-memory only, so no Realm migration is needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Android's normalizing function stripped out characters too aggressively leading to false matches between different numbers. This commit introduces a faster normalizing function that includes characters.
- Adds a new class of features for message management.
- Adds a manual option to find and delete duplicate messages
- Adds a setting to automatically delete duplicates during sync
- Adds a sha256 hashing function
Co-authored-by: octoshrimpy <octoshrimpy@users.noreply.github.com>
In some cases, (mainly on HyperOS and variants) content provider will return null if an empty conversation is created. This was breaking the compose activity as it expects some object other than null.
This commit changes the behavior to provide a new conversation object if createConversationFromCp ever returns null.
Some emoji reactions will appear as "Liked 'message...'" with the message cut off. This change uses a regex to match all ellipsis at the end of messages to any other message with the same content.