handleReject related the MSC4310 decline to the caller's call.member event, which is what the notification references. MSC4310 and Element Call match a decline against the rtc.notification event itself. So:
the caller kept "Calling…" for the full 90 s after being told "Declined";
declines from other clients, which correctly reference the notification, didn't stop Lotus ringing on your other devices.
Change
The incoming call keeps the notification's own event ID, and Reject relates the decline to it.
The "declined on another device" dismissal and declinedRing accept either ID, since older Lotus builds referenced the membership.
The missed-call line is skipped for a call you declined.
Verified headless (a DM, Bob rings, Reject):
Before: the decline referenced the membership.
After: it references the notification.
Unit test added. tsc clean · unit tests pass · ESLint/Prettier clean.
Fixes #313.
`handleReject` related the MSC4310 decline to the caller's `call.member` event, which is what the notification references. MSC4310 and Element Call match a decline against the **`rtc.notification` event itself**. So:
- the caller kept **"Calling…" for the full 90 s** after being told "Declined";
- declines from other clients, which correctly reference the notification, didn't stop Lotus ringing on your other devices.
**Change**
- The incoming call keeps the notification's own event ID, and **Reject** relates the decline to it.
- The "declined on another device" dismissal and `declinedRing` accept **either** ID, since older Lotus builds referenced the membership.
- The **missed-call** line is skipped for a call you declined.
**Verified** headless (a DM, Bob rings, Reject):
- **Before:** the decline referenced the membership.
- **After:** it references **the notification**.
Unit test added. `tsc` clean · unit tests pass · ESLint/Prettier clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
handleReject related the MSC4310 decline to the caller's call.member event
(the notification's reference), but MSC4310 and Element Call match a
decline against the rtc.notification event itself, so the caller kept
"Calling…" for the full 90 s after being told "Declined", and declines
from other clients (correctly referencing the notification) didn't stop
Lotus ringing on other devices.
- The incoming call keeps the notification's own event id; Reject relates
the decline to it.
- The "declined on another device" dismissal and declinedRing accept
either id (older Lotus builds referenced the membership).
- The missed-call line is skipped for a call we declined.
Verified headless (DM, Bob rings, Reject): the decline used to reference
the membership; it now references the notification. Unit test added.
Fixes#313
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #313.
handleRejectrelated the MSC4310 decline to the caller'scall.memberevent, which is what the notification references. MSC4310 and Element Call match a decline against thertc.notificationevent itself. So:Change
declinedRingaccept either ID, since older Lotus builds referenced the membership.Verified headless (a DM, Bob rings, Reject):
Unit test added.
tscclean · unit tests pass · ESLint/Prettier clean.🤖 Generated with Claude Code
https://claude.ai/code/session_017PCb59uY3UKqDqt7B6hzd5