continuwuation/continuwuity
continuwuation/continuwuity
16
112
Fork 125
Code Issues 136 Pull requests 27 Releases 40 Packages 3 Activity Actions

feat(pusher): opt-in event type in event_id_only push notifications #2171

Closed
mmaudet wants to merge 1 commit from mmaudet/continuwuity:feat/pusher-eio-type-upstream into main
pull from: mmaudet/continuwuity:feat/pusher-eio-type-upstream
merge into: continuwuation:main
Conversation 3 Commits 1 Files changed 4 +37

1 commit

Author SHA1 Message Date
Michel-Marie MAUDET
d0a5bdc445
 		feat(pusher): opt-in event type in event_id_only push notifications
Some checks failed
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 6s
Details
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Details
Checks / Prek / Check changed files (pull_request) Has been cancelled
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
Details 
Add pusher_event_id_only_include_event_type (default false) so that
push notifications for HTTP pushers registered with the event_id_only
format can additionally carry the event's type (e.g. m.call.invite).

The default behaviour is unchanged: event_id_only notifications carry
only the event ID, the room ID and the counts. With the option enabled
the gateway additionally learns the event type — and nothing else: no
content, sender, display name or room name. A VoIP push path (e.g. iOS
PushKit, where every push must be reported to CallKit immediately) can
then distinguish an incoming call from a message without a network
fetch.
 2026-08-23 15:58:56 +02:00