| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Apart from generally being cleaner, we're going to want to use the statetable
in isolation of rooms, to handle invites.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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
|
| |
|
|
| |
Install the artwork in the right place so that pidgin uses it.
|
| |
|
|
| |
Use an external http parser, instead of inventing that wheel ourselves.
|
| |
|
|
| |
Move things around quite a lot, to make it a bit saner
|
| |
|
|
|
|
| |
Not quite sure if this is the right approach yet - in particular, purple
distinguishes between active 'conversations', as opposed to 'chats' in the
buddy list. Which should our chats be?
|
| |
|
|
|
|
|
| |
Our first API call, woohoo.
At the moment we just call initialSync and don't do anything with the
response. But it's satisfying progress.
|
| |
|
|
| |
Still doesn't do anything, but at least it has the right name now...
|
|
|
Just lifting the null plugin from the libpurple source. Doesn't do anything
yet, but functions as a working plugin.
|
