m.room.tombstone is not handled anywhere. When a room is upgraded - a version bump, a spam clear-out - the old room stops receiving messages and points at its replacement, and moho keeps showing the dead one as though the conversation had simply gone quiet.
Done looks like: a tombstone joins the successor (or offers to), the old buffer says where the room went, and the new one takes its place in the list.
`m.room.tombstone` is not handled anywhere. When a room is upgraded - a version bump, a spam clear-out - the old room stops receiving messages and points at its replacement, and moho keeps showing the dead one as though the conversation had simply gone quiet.
**Done looks like:** a tombstone joins the successor (or offers to), the old buffer says where the room went, and the new one takes its place in the list.
Salastil
added the bug label 2026-09-03 13:11:30 -04:00
Finished. m.room.tombstone is handled: it joins the replacement room and leaves a line in the old one saying where the conversation went, so the dead room keeps its history and stops looking like a room that merely went quiet.
Followed after the sync response rather than at the point the tombstone is seen — joining registers the new room, which processes its state, which is where tombstones are noticed, so doing it inline is a function calling itself. It is noted and drained by the sync loop instead.
nobilis 1bd675c
Finished. `m.room.tombstone` is handled: it joins the replacement room and leaves a line in the old one saying where the conversation went, so the dead room keeps its history and stops looking like a room that merely went quiet.
Followed *after* the sync response rather than at the point the tombstone is seen — joining registers the new room, which processes its state, which is where tombstones are noticed, so doing it inline is a function calling itself. It is noted and drained by the sync loop instead.
nobilis 1bd675c
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.
m.room.tombstoneis not handled anywhere. When a room is upgraded - a version bump, a spam clear-out - the old room stops receiving messages and points at its replacement, and moho keeps showing the dead one as though the conversation had simply gone quiet.Done looks like: a tombstone joins the successor (or offers to), the old buffer says where the room went, and the new one takes its place in the list.
Finished.
m.room.tombstoneis handled: it joins the replacement room and leaves a line in the old one saying where the conversation went, so the dead room keeps its history and stops looking like a room that merely went quiet.Followed after the sync response rather than at the point the tombstone is seen — joining registers the new room, which processes its state, which is where tombstones are noticed, so doing it inline is a function calling itself. It is noted and drained by the sync loop instead.
nobilis 1bd675c