| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
This breaks functionality whilst both events.rooms and modelService
are in use.
|
|
|
|
| |
and fix the bug where kicks of unjoined users aren't displayed sensibly in the history
|
| |
|
| |
|
| |
|
|
|
|
| |
plays nicer with federation.
|
|
|
|
| |
doesn't clutter the recents list.
|
|
|
|
| |
sidepanel - takes up too much room
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Update it with the latest value
|
| |
|
|
|
|
| |
(ex:user has not joined the room yet)
|
| |
|
|
|
|
| |
blindly assuming a recents controller is writing to rootScope.rooms and setting numUsersInRoom there.
|
|
|
|
| |
information in the webclient.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
filters using Matrix data.
|
| |
|
|
|
|
| |
and recent flows
|
|
|
|
| |
aliases for now) and its users displaynames or ids
|
|
|
|
| |
event for other events: it's rarely going to be sesnible.
|
| |
|
| |
|
| |
|
| |
|
|
|