process_sync_response reads only resp["rooms"]["join"] (backend/matrix/mod.rs:370). The invite and leave sections of the sync response are never touched, and there is no accept- or decline-invite RPC.
So somebody inviting you to a Matrix room is something this client cannot perceive at all — the invite does not appear, cannot be accepted, and cannot be declined. The only way into a room is joinMatrixRoom with an id or alias you already have out of band.
(An m.room.member invite event in a room you have already joined does produce a chat line — that is a different thing and works.)
Done looks like:rooms.invite read into a pending-invite list, surfaced in the UI, with accept (/join) and decline (/leave) actions. Reading rooms.leave would also let a room you were kicked from or left elsewhere disappear.
Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho 1a11250, nobilis 030707f).
`process_sync_response` reads only `resp["rooms"]["join"]` (`backend/matrix/mod.rs:370`). The `invite` and `leave` sections of the sync response are never touched, and there is no accept- or decline-invite RPC.
So somebody inviting you to a Matrix room is something this client cannot perceive at all — the invite does not appear, cannot be accepted, and cannot be declined. The only way into a room is `joinMatrixRoom` with an id or alias you already have out of band.
(An `m.room.member` invite event in a room you have *already* joined does produce a chat line — that is a different thing and works.)
**Done looks like:** `rooms.invite` read into a pending-invite list, surfaced in the UI, with accept (`/join`) and decline (`/leave`) actions. Reading `rooms.leave` would also let a room you were kicked from or left elsewhere disappear.
---
_Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho `1a11250`, nobilis `030707f`)._
Salastil
added the bug label 2026-08-29 09:59:43 -04:00
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.
process_sync_responsereads onlyresp["rooms"]["join"](backend/matrix/mod.rs:370). Theinviteandleavesections of the sync response are never touched, and there is no accept- or decline-invite RPC.So somebody inviting you to a Matrix room is something this client cannot perceive at all — the invite does not appear, cannot be accepted, and cannot be declined. The only way into a room is
joinMatrixRoomwith an id or alias you already have out of band.(An
m.room.memberinvite event in a room you have already joined does produce a chat line — that is a different thing and works.)Done looks like:
rooms.inviteread into a pending-invite list, surfaced in the UI, with accept (/join) and decline (/leave) actions. Readingrooms.leavewould also let a room you were kicked from or left elsewhere disappear.Filed from a protocol coverage survey of the four deployed protocols, 2026-08-29 (moho
1a11250, nobilis030707f).Finished — nobilis
9226c92, moho629948b