Skip to content

Support tapbacks on older messages and exact emoji on macOS 27 - #159

Merged
nixfred merged 5 commits into
nixfred:mainfrom
marcus:upstream-reactions
Nov 11, 2026
Merged

nixfred merged 5 commits into
nixfred:mainfrom
marcus:upstream-reactions

Conversation

@marcus

@marcus marcus commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Adds older/off-screen message reactions and exact custom emoji, with a searchable reaction picker. Classic and custom reactions preserve their identity on reads, including custom emoji that resemble a classic tapback. The generated QML module matches its TypeScript source.

The Mac resolves target ordinals including literal reaction-annotation lookalikes, settles the bubble, validates picker context/focus and button uniqueness, and performs at most one selection. chat.db decides the result; uncertain gestures are never retried. Custom input is bounded stdin. Picker routes require macOS 27.2+; earlier versions may use direct bubble actions but never the unproven emoji catalogue path. Synthetic event access is preflighted without prompting, and cleanup dismisses both picker layers.

Based on current upstream main, including #158/#161, with upstream theme, controls and manifest preserved. The separate composer emoji feature is already upstream. The maintainer's live self-thread validation remains necessary for AX identifiers and platform behavior; docs/reactions.md records the limits.

Validation: 827 Bun tests, 347 synthetic Mac Python tests and 7 Qt picker checks pass. The native classic path covers wrong labels, duplicate buttons, focus loss and changed origin; the custom read-path fixture runs in CI. GitHub CI passes. No real conversations opened or reactions sent.

@nixfred

nixfred commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Thank you, Marcus. Reacting to older and off-screen messages through Tapback Details, with exact custom emoji, is the biggest parity gap on the macOS 27 gateway, and the discipline is good: emoji on bounded stdin, the Messages UI lock, one press and never a retry after an uncertain result. The generated TapbackActions.mjs matches its source byte for byte. An independent review of this branch came back with one blocking item and several should-fix items.

Blocking

  1. The macOS 27 path that ships has no test. In production run is jxa, so picker_route returns native_emoji_picker(request); the JXA picker() and its q.emoji branch never run there. Every macOS 27 react() test injects a runner, so it exercises that code instead, and NativeEmojiPickerTests cover only the emoji path. Two one-line mutations leave the suite green: deleting the classic branch's if not context(): return picker-elsewhere, and changing len(hits) != 1 to not hits (which lets duplicate buttons through). That context() check is the only guard against pressing a reaction in a picker opened on the wrong bubble. Please add tests for the classic branch (wrong label, duplicate button, focus lost), and delete the JXA picker and emoji code that cannot run.

Should fix

  1. A wider wrong-message hole, on macOS 26 and 27. bodyIs and REACTED now accept "<text>, Ann loved this" with no reaction count, while resolve() still counts only exact-text twins. With a target ok and a later real message ok, Ann loved this in the same minute on the same side, the newest-first scan lands on the wrong bubble (ordinal 0), and on 27 context() accepts it too. main's bodyIs does not match it. stray() only catches it after the other person has seen the reaction. Counting look-alikes whose tail matches REACTED as twins in resolve() closes it.
  2. The read path never sends kind. bridge/mac/imsg emits {emoji, from_me, by}, but tapback-actions.ts checks t.kind === "emoji", so a custom 👍 or ❤️ reads as a classic like or love. Choosing the custom 👍 again sends --emoji-stdin --yes without --remove, the Mac answers "unchanged", and the pending pill never settles. Nothing wrong is sent, because emoji_plan on the Mac decides, but docs/reactions.md ("retain their type on the read path") is not true yet and the TS tests assert a shape the bridge does not emit.
  3. The macOS 26 custom-emoji path is unproven (the docs list 27.2 only). It runs entireContents with the catalogue open, which your own doc forbids, and on versions below 27 there is no close_picker or clear_stale_picker, so a failure leaves the catalogue open for the next run's scan. Please fail closed below 27 unless the bubble offers the emoji as a direct action.
  4. Possible regression on macOS 27.0 and 27.1. The change deletes is_last and the Edit, Tapback Last Message route. main's notes say no bubble action opened the picker on 27.0.1, so if that still holds, reactions on the newest message, which work today, would now exit 69 with no picker. Gate on 27.2 or keep the menu route for the newest message.
  5. click_glyph posts synthetic CGEvents without calling CGPreflightPostEventAccess(). That call never prompts, so it keeps the "no unrequested consent prompt" rule from macOS 26.6.2: sshd-keygen-wrapper → Messages Automation cannot be enabled #36.

Smaller notes: the picture flag and its imsg-reply comment are dead code (no such tool is in this branch), open_picker is unused, the composer emoji mode (showClassics=false, emojiChosen) is not wired into any QML though docs/reactions.md says it ships, and close_picker sends one Escape when two layers can be open.

What I will do. I will run this on the real macOS 27.2 gateway, on the self-thread only, once the above is in, because the open questions need a live Mac: whether Tapback Details opens the picker on 27.0 and 27.1, the accessibility identifier of the classic buttons, and how the 26 catalogue is laid out. Replies (#160) and this branch share imsg-react, so they will land one after the other.


Generated by Claude Code

nixfred added a commit that referenced this pull request Nov 10, 2026
…ll 4x faster (CHANGELOG, CHANGE.log, roster, weekly notes)

WHAT: CHANGELOG entries for #158 (Delivered until Read) and #161 (composer emoji picker) with the real end-to-end numbers for the poll speed-up (shallow 0.77 s to 0.2 s, deep 2.1 s to 1.0 s on gus); CHANGE.log entries for 401b99d, #158 and #161; Marcus Vorwaller added to the no-X table in CONTRIBUTORS-X.md (nothing on his GitHub profile or social accounts, his site marcus.pictures lists none, checked 10 Nov); WEEKLY-NOTES W46 section for 10 Nov with Marcus's own words about the rebases and the reasons #159 #160 #162 #163 were sent back.
WHY: the PR-run checklist records every merge the day it lands, with the contributor's real name and a verified X handle or a visible "none found" plus asking Fred the same day.
CONTEXT: independent review of #159 #160 #162 #163 (read-only, nothing sent to the Mac) found: #162 ffmpeg guessed the format from sender bytes (reproduced: a two-line ffconcat file delivered as a video rendered a different cached picture), #163 Qt plays bytes the safety check never saw and playback stops on any list rebuild, #160 three failure paths after Return report "nothing sent" and the recipient is never checked before Return (both confirmed against the code), #159 the shipped macOS 27 path has no test. Comments with the specifics are on each PR. Deployed 10 Nov to the gateway Mac (read_state.py and imsg, backups in ~/.blip/backups-20261110), gus and vic, all healthy, no log errors.
TAGS: docs, changelog, change-log, weekly-notes, roster, marcus, pr-run, review

LR-T: pr-run, contributor-pr, bookkeeping
LR-D: blip, docs
LR-K: pr-158-161-merged, pr-159-160-162-163-sent-back, marcus-no-x
LR-R: 401b99d, ea64c98, 0d302b1

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BXN1v67b9f9VHGe3FhaQuD
@marcus
marcus force-pushed the upstream-reactions branch from dad4c85 to cb1972e Compare November 10, 2026 16:55

marcus commented Nov 10, 2026

Copy link
Copy Markdown
Contributor Author

Addressed the review and rebased onto current main.

The native classic-button path now has wrong-label, duplicate-button, lost-focus and changed-origin tests. Removed the unused JXA picker/catalogue implementation, picture flag and unused native opener seam. resolve() counts literal reaction-annotation lookalikes as ordinal twins, and a synthetic bridge test confirms custom 👍 retains kind: emoji on reads (also run in CI).

Below macOS 27, custom emoji use direct bubble actions only; the unproven catalogue path is gone. Picker-based production routes are gated to 27.2+ rather than assuming 27.0/27.1 support. click_glyph now preflights event-post access without prompting; cleanup Escapes both picker layers. Docs distinguish the separate composer PR from this reaction picker.

Validation: 827 Bun tests, 347 synthetic Mac Python tests, and 7 Qt picker checks passed after rebase. No real conversations were opened or reactions sent. CI is running on the updated head. The live AX identifiers and older macOS behavior remain for your planned self-thread gateway validation; the version gate deliberately fails closed in the meantime.

@marcus
marcus force-pushed the upstream-reactions branch from 1cbae30 to 47874b6 Compare November 10, 2026 18:02
nixfred added a commit that referenced this pull request Nov 10, 2026
… (CHANGELOG, CHANGE.log, roster, weekly notes, CLAUDE.md)

WHAT: CHANGELOG and CHANGE.log entries for #162 (native stickers) and the reaction-scan speed-up (9b4f8d9) with the real numbers; CONTRIBUTORS-X.md moves Marcus Vorwaller to 3 merged (#158, #161, #162), still no X handle found and asked Fred; WEEKLY-NOTES W46 gets the #162 and speed-up bullets plus the note that #159, #160 and #163 got a second independent review of their rebased heads; CLAUDE.md's measured-latency paragraph gains the lesson from the reaction scan (the 90-day margin is real data: 3 of 28,305 reactions are stamped before their target, the worst by 0.83 days; an ORDER BY in SQL brings the full scan back; the date index reorders reactions unless sorted by ROWID; do not probe the guid index by shape because _strip_assoc is lenient on purpose).
WHY: the PR-run checklist records every merge the day it lands, and the next agent that "optimises" enrich() must find the traps written down instead of rediscovering them.
CONTEXT: Fred approved the #162 merge and the speed-up from the literal diffs on 10 Nov. Merge commit aee3394, speed-up 9b4f8d9.
TAGS: docs, changelog, change-log, weekly-notes, roster, claude-md, pr-run, stickers, latency

LR-T: pr-run, bookkeeping, latency
LR-D: blip, docs
LR-K: pr-162-merged, tapback-window-bound, marcus-no-x
LR-R: aee3394, 9b4f8d9

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BXN1v67b9f9VHGe3FhaQuD
@nixfred

nixfred commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Second-round review of 47874b6, and thank you: the original blocker is properly closed. An independent reviewer went through it read-only (nothing sent to a Mac); I re-checked the first item myself.

Fixed and confirmed

  • The shipped macOS 27 classic-button path is now tested; mutating the guards before the classic press (context()) and on len(hits) != 1 fails the suite. The JXA picker code is gone and a test keeps it gone.
  • The look-alike hole is closed in one direction: resolve() now counts look-alikes, and reverting it fails a test.
  • Reactions on macOS below 27 no longer open the unproven catalogue picker; kind is now emitted on the read path; the 27.0/27.1 regression risk fails closed; TapbackActions.mjs is byte-identical to its source. No untrusted text reaches script source (constants for the JXA and AppleScript, bounded validated JSON on stdin).

Should-fix

  1. CI runs nothing from bridge/mac/test_reaction_kind.py. The file has no if __name__ == "__main__": unittest.main() (I checked: zero matches), so python3 bridge/mac/test_reaction_kind.py exits 0 without running a test. The kind fix is therefore unguarded in CI (reverting it fails only under python3 -m unittest). Two lines fix it, and the file also still has the sticker PR's docstring and an unused helper.
  2. The mirror look-alike is still open (traced by the reviewer in the code, not run on a Mac). Target text "ok, Ann loved this", and a later message on the same side at the same HH:MM that reads "ok", which Ann loved: resolve() gives ordinal 0, the JXA bodyIs exact-match branch (imsg-react ~450) and the native context() (~909) both accept the later bubble, so the press lands on the other message. stray() reports it only afterwards. Main could not reach this on 27 because it refused any older message. Simplest fix: refuse any target whose own text has the form "X, ".
  3. The 27.2 gate and the permission preflight are untested and say the wrong thing. The gate refuses only after select_chat() (~1198) has opened the conversation, which brings Messages forward, and then reports "the bubble does not offer 'Heart' (Messages may have renamed it)" when the real cause is the macOS version. The preflight (~745) surfaces the bare code event-access-denied with exit 75, does not say nothing was sent or which permission is missing, and is checked last, after the picker and palette have been opened. Removing either leaves both suites green. Gating 27.0/27.1 is fine as a decision, but say it plainly in the error and the CHANGELOG.
  4. The neighbour-prefix guard has no test. Replacing the REACTED check in context() (~909) with a plain prefix match leaves both suites green; it is the one check that stops a reaction on "ok, see you" when the target is "ok".

Nits: close_picker always sends two Escapes even when nothing is open, and clear_stale_picker can send up to six while the docs say one per layer; a classic Heart failing inside the native picker is told "Messages did not expose that exact emoji"; the helper's 30 s deadline is separate from the run's; a sticker reaction reads as a custom star because the kind: "sticker" checks rely on a shape only the sticker PR emits; on macOS 26 the "+" catalogue is still offered though most choices will fail; pressing Enter in the search field sends the first result as a reaction (ReactionPicker.qml:132).

Still to prove live on the 27.2 gateway, self-thread only, once this and the rebase are done: whether CGPreflightPostEventAccess() returns true for sshd-keygen-wrapper (if not, every custom emoji needing the palette fails), whether a reacted bubble reads ", Ann loved this" with no count, and what the extra Escape does when nothing is open. I will not run anything that sends without Fred's explicit word.

Heads-up for the rebase: #162 is merged and already carries the "kind": "emoji" tapback line in enrich(), so drop that duplicate hunk. bun test 836 pass and the CI Python suites pass on your head.

Use each bubble action and verify the exact picker target and database receipt. Keep payloads on bounded stdin, serialize Messages UI actions, press once and never retry uncertain outcomes. Include synthetic AX and QtTest coverage without changing the app style or version.
Cover classic native picker context and uniqueness guards, count reaction-label lookalikes, and preserve custom emoji kind on reads. Fail closed for unproven picker versions, preflight synthetic event access, and close both picker layers.
A custom emoji that resembles a classic tapback must retain kind=emoji so selecting it again removes it and settles pending state.
Exercise the synthetic bridge fixture alongside native reaction tests.
@marcus
marcus force-pushed the upstream-reactions branch from 47874b6 to 5fc0454 Compare November 10, 2026 22:47
nixfred added a commit that referenced this pull request Nov 11, 2026
…mission probe addresses System Events by PID and is bounded

WHAT: imsg-react's ae_permission() (AEDeterminePermissionToAutomateTarget,
  askUserIfNeeded=false, the prompt-free "may sshd automate System Events?"
  check that system_events_consent() asks before every tapback on macOS 27)
  now builds a typeKernelProcessID ("kpid") descriptor from System Events'
  pid (pgrep -x, no LaunchServices) instead of a bundle-id ("bund") one, and
  runs the call on a daemon thread bounded at AE_PROBE_SECONDS = 5. An answer
  that does not come is None -> "cannot confirm ... nothing was done", the
  same refusal as any other unknown answer.
WHY: over ssh on macOS 27.2 the bundle-id form never returns (LaunchServices
  is not available to ssh sessions on 27.2, the same fault the Pin helper
  works around with pgrep). Every tapback then sat inside the Messages UI lock
  for minutes before touching Messages, and the Mac-side process outlived the
  caller. Found during the #159 live test (self-thread only, Fred approved):
  faulthandler placed both hung runs in ae_permission <- system_events_consent
  <- react, before any UI action, so nothing was pressed. On main since
  5658760 (2026-10-07); tapbacks are off in this install's bridge.conf, which
  is why nobody saw it.
VERIFIED on the gateway, read-only: bundle id still blocked at 15 s, kpid
  answered 0 in 0.04 s; the fixed probe from this file answered granted in
  0.15 s three times. With the same fix in #159's copy, a self-thread Heart on
  a month-old message landed in 12.6 s (chat.db type 2000). Tests:
  test_react.py 63 pass (3 new: a probe that never answers refuses in under
  5 s; _bounded answers and errors; kpid, never bund); all 28 CI Python/Qt
  suites pass; bun test 872 pass. Door one-way (bridge/mac/imsg-react), the
  literal diff approved by Fred.
NOT YET: installed on the Mac. fnix went offline at 15:12 EST right after the
  Heart (Tailscale offline, ssh times out); it gets this file once it is back.

LR-T: blip, bridge, imsg-react, tapbacks, macos-27, appleevents, tcc, hang, fix
LR-D: blip, bridge, macos
LR-K: ae-permission-kpid-not-bund, bounded-tcc-probe, launchservices-over-ssh-27-2
LR-R: 5658760
LR-L: law-3, law-10, law-11

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BXN1v67b9f9VHGe3FhaQuD
@nixfred

nixfred commented Nov 11, 2026

Copy link
Copy Markdown
Owner

Round three on 5fc0454, and this time with the real macOS 27.2 gateway (self-thread only, with Fred's explicit OK). Thank you: every round-2 point is fixed in code, and I checked each one by breaking it.

Round-2 points, fixed and guarded

  • test_reaction_kind.py now runs its test in CI.
  • A target whose own text ends in ", " is refused before any UI opens (removing that refusal fails a test).
  • The 27.2 gate and the event-posting preflight now run before Messages is brought forward, and say plainly what is wrong and that nothing was sent. Removing either one, or the whole gate, fails a test.
  • The neighbour-prefix guard in context() is tested now (replacing it with a plain prefix match fails the suite).
  • CI green, test_react.py 86 pass, test-reaction-ui.py 7 pass, TapbackActions.mjs rebuilds byte-identical, pyflakes clean, gitleaks clean.

Live on the 27.2 gateway

  1. Both main and this branch hung before touching Messages. The prompt-free Automation check (ae_permission, on main since October) addresses System Events by bundle id, and over ssh on 27.2 AEDeterminePermissionToAutomateTarget never returns for that: still blocked at 15 s, while the same call by PID answered in 0.04 s. The Mac-side run sat in the UI lock for minutes. That one is ours, not yours: fixed on main in 33aab7b and 1a51bbe (PID descriptor, a 5 s bound that refuses, and a retry while a just-launched System Events answers -600). Your branch does not touch that function, so a rebase picks it up.
  2. Classic Heart on a month-old message, far off screen: works. 12.6 s, and chat.db confirms it (type 2000). That is the main thing this PR adds, and it held on the real Mac.
  3. Event-posting permission: present. The custom-emoji run got past your CGPreflightPostEventAccess check, so sshd-keygen-wrapper can post events on this gateway.
  4. Blocker: once a bubble carries a reaction, its picker cannot be confirmed. On that same (now Hearted) bubble, a custom 🦊 returned picker-elsewhere ("the tapback picker opened on another message; nothing was done"), and removing the Heart returned the same. Your guard refused correctly both times, so nothing landed on the wrong message, but adding a second reaction or removing one does not work on 27.2. I stopped there (two failed attempts on the same target), so a custom emoji on a bubble with no reaction is still untested. My guess, not verified: the reacted bubble's accessibility label on 27.2 is not the ", " shape the context check expects. If you send me a read-only snippet that prints the label of the selected bubble and the picker's context, I will run it on the gateway and paste the output.

Small things, none blocking on their own

  • Your only change to bridge/mac/imsg is a second copy of the "kind": "emoji" line Render native stickers and bounded animated previews #162 already put on main (it now appears twice in the dict). Please drop the hunk, so the PR stops touching that file.
  • resolve()'s copy of the prefix guard (imsg-react ~275) is still untested: replacing it with a plain prefix match leaves everything green, and the two copies must agree, or a later "ok, see you" shifts the ordinal and the scan can land on an older "ok".
  • ci.yml now conflicts with Play voice messages inline with real waveforms and seeking #163's audio steps, which landed today (both add steps in the same place; keep both).
  • Pressing Enter in the picker's search field reacts with the first result while nothing is highlighted (ReactionPicker.qml:132); highlight it, or require a choice.

Once the reacted-bubble case works, I will run the remaining live steps (custom emoji on a fresh bubble, remove, a second reaction) and land it ahead of #160.


Generated by Claude Code

nixfred added a commit that referenced this pull request Nov 11, 2026
…s live test

What the #159 self-thread test on the real gateway proved (Heart on an old
message works, event-posting granted) and found (main's permission probe hung
over ssh on 27.2, fixed in 33aab7b + 1a51bbe; #159 cannot add or remove a
second reaction on a reacted bubble, sent back).

LR-T: blip, weekly-notes, pr-159, tapbacks
LR-D: blip, docs
LR-K: weekly-w46-wed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BXN1v67b9f9VHGe3FhaQuD
@nixfred
nixfred merged commit 6a4fbce into nixfred:main Nov 11, 2026
1 check passed
nixfred added a commit that referenced this pull request Nov 11, 2026
WHAT: the same-turn bookkeeping for the #159 merge (6a4fbce, 56bc294).
  - CHANGELOG.md: a proper Unreleased entry; the one-line note Marcus's rebase
    left above the "## Unreleased" heading is removed (it was orphaned there).
  - CHANGE.log: #159 entry with the live 27.2 proof and what Larry added.
  - CONTRIBUTORS-X.md: Marcus 5 merged (#158 #161 #162 #163 #159), #160 under
    review, X handle still none found (rechecked 2026-11-11, asked Fred).
  - WEEKLY-NOTES.md: W46 Wed 11 Nov, #159 bullet and the two Blip-side findings.
NOT staged on purpose: bridge/mac/findmy_city.py and test_findmy_city.py are
  someone else's uncommitted work in this tree.

LR-T: blip, pr-159, changelog, contributors, weekly-notes
LR-D: blip, docs
LR-K: pr-run-bookkeeping
LR-R: 6a4fbce, 56bc294

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nixfred

nixfred commented Nov 11, 2026 •

Copy link
Copy Markdown
Owner

Merged as 6a4fbce. Thank you, Marcus: reacting to any message with any emoji on 27.2 is a real gap closed, and you fixed every point of my second round in the same evening.

What I checked on 5fc0454, merged onto current main:

  • Tried on the real 27.2 gateway, self-thread only (Fred approved those sends in advance): a Heart on a month-old message, a custom 🦊 (exact emoji confirmed in chat.db, kind: "emoji" on the read path), a reaction on an already-reacted bubble (so the "text, Ann loved this" label match works), and removal back to none. The picker ignoring AXPress and needing one hit-tested click was exactly as you described, and the event-posting permission is granted for sshd-keygen-wrapper. The extra Escape left nothing stuck.
  • CI green, 877 bun test, the Qt suites, 92 bridge tests, TapbackActions.mjs rebuilds byte-identical, no undefined names, gitleaks clean. Every guard I named last round now fails a test when removed (27.2 gate, preflight, ambiguous-text refusal, neighbour-prefix in context()).

What I changed on top, in the open:

  • ci.yml: kept both new steps, yours and Play voice messages inline with real waveforms and seeking #163's audio suites.
  • Dropped your "kind": "emoji" tapback line in imsg: Render native stickers and bounded animated previews #162 already carries it, so it appeared twice.
  • Your CHANGELOG line had landed above the ## Unreleased heading after the rebase; I turned it into a proper entry.
  • One new test (56bc294): resolve() counts a later bubble that reads exactly like the reacted target ("ok, Ann loved this") but must not count one that merely starts with "ok, ". That guard had no test; replacing it with a plain prefix match, or with False, left both suites green. Both now fail.

Two things I found on the way that were Blip's, not yours, both fixed on main: the permission check before any tapback hung forever over ssh on 27.2 when System Events was addressed by bundle id (33aab7b, now by pid and bounded), and the first reaction after a Mac reboot was refused because a just-launched System Events answers "not running" once (ef9a1ab).

Small things I left, none blocking, yours if you want them: pressing Enter in the picker's search field sends the first match as a reaction (ReactionPicker.qml ~132); close_picker sends two Escapes even when nothing is open; on macOS 26 the "+" catalogue is still offered though most choices will fail there.

#160 is next. Correction to a line I first wrote here: I said its two blockers still applied, and I had not re-checked its new head. I have now: REACTED is defined on d0fc54f and pyflakes is clean, and the Linux side now says "Check Messages before sending again" for exit codes that do not prove nothing was sent, so both are addressed. It still needs a rebase onto main now that #159 and #163 are in (it carries a stale copy of #159's code), and I will review the new head in full when it is rebased.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants