| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Trying to keep the size of matrix-room.c under control, move the membertable
management bits out to a separate file.
Also do away with the special handling for the first /sync of a room, and
instead *always* group together member arrivals/departures until after we've
finished handling the state table.
|
|
|
|
| |
The 'persistent' behaviour matches the matrix model much better.
|
|
|
|
|
|
|
|
| |
An initial implementation for displaying the people in a room. This isn't very
nice, and the code is somewhat thrown together as a prototype/proof-of-concept
for now. We probably want to refactor matrix-room.c, which is now altogether
too unwieldy. It probably also makes sense to try to do some of this stuff on
the server.
|
|
|
|
| |
Give rooms a name according to who's in it, if there is no proper name.
|
|
|
|
|
|
|
| |
Move all matrix-login and bits of matrix-sync into matrix-connection, where
it seems to make more sense.
Also move MatrixConnectionData into matrix-connection.h
|
|
|
|
|
| |
This structure comes and goes with each connection, so rename it to better
reflect its lifecycle.
|
|
|
|
|
| |
Persist the next_batch, so that we don't get old scrollback each time we open
the application.
|
| |
|
|
|
|
| |
Do local echo of sent messages, and ignore the remote echo.
|
|
|
|
| |
Use an external http parser, instead of inventing that wheel ourselves.
|
|
|
|
|
| |
Factor out the handling of errors from API calls, to make it easier to add new
ones.
|
|
Move things around quite a lot, to make it a bit saner
|