m.tag is not implemented. The only occurrence in the backend is a test fixture in receipts.rs:188.
Room tags are how Element sorts the room list: favourites to the top, low priority to the bottom, and both travel with the account. Without them a moho user's ordering is local at best, and a person who has organised their rooms in Element sees none of it here.
`m.tag` is not implemented. The only occurrence in the backend is a test fixture in `receipts.rs:188`.
Room tags are how Element sorts the room list: favourites to the top, low priority to the bottom, and both travel with the account. Without them a moho user's ordering is local at best, and a person who has organised their rooms in Element sees none of it here.
Read at connect and followed as it changes — one filtered sync rather than a request per room, for the same reason the receipts and invites beside it need their own: a resumed session is told only what changed, and a tag set months ago has not. Writes go one tag at a time, which is what the endpoint offers and also the right granularity: the list is shared with every other client, and replacing it whole to change one entry would drop the u.* tags this client cannot show.
They land on the buffer as favourite and lowPriority rather than as Matrix vocabulary. A favourite sits with this window's pins in the rail because it is the same intent said in a different place, and a pin made here still beats a low priority set elsewhere.
Finished.
Read at connect and followed as it changes — one filtered sync rather than a request per room, for the same reason the receipts and invites beside it need their own: a resumed session is told only what changed, and a tag set months ago has not. Writes go one tag at a time, which is what the endpoint offers and also the right granularity: the list is shared with every other client, and replacing it whole to change one entry would drop the `u.*` tags this client cannot show.
They land on the buffer as `favourite` and `lowPriority` rather than as Matrix vocabulary. A favourite sits with this window's pins in the rail because it is the same intent said in a different place, and a pin made here still beats a low priority set elsewhere.
[b7d42d8](https://git.salastil.com/Salastil/nobilis/commit/b7d42d8), [5985070](https://git.salastil.com/Salastil/moho/commit/5985070)
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.tagis not implemented. The only occurrence in the backend is a test fixture inreceipts.rs:188.Room tags are how Element sorts the room list: favourites to the top, low priority to the bottom, and both travel with the account. Without them a moho user's ordering is local at best, and a person who has organised their rooms in Element sees none of it here.
Finished.
Read at connect and followed as it changes — one filtered sync rather than a request per room, for the same reason the receipts and invites beside it need their own: a resumed session is told only what changed, and a tag set months ago has not. Writes go one tag at a time, which is what the endpoint offers and also the right granularity: the list is shared with every other client, and replacing it whole to change one entry would drop the
u.*tags this client cannot show.They land on the buffer as
favouriteandlowPriorityrather than as Matrix vocabulary. A favourite sits with this window's pins in the rail because it is the same intent said in a different place, and a pin made here still beats a low priority set elsewhere.b7d42d8, 5985070