- Apr 04, 2019
-
-
Brendan Abolivier authored
-
Amber Brown authored
* rewrite & simplify * changelog * cleanup potential sql injection
-
Erik Johnston authored
Add delete group admin API
-
Andrew Morgan authored
Prevent kick events from succeeding if the user is not currently in the room.
-
Marcel Krüger authored
* Do not double encode fallback redirect URL Signed-off-by:
Marcel Fabian Krüger <zauguin@gmail.com>
-
Erik Johnston authored
Fix issue #4596
-
*=0=1=4=* authored
Correct default POSTGRES_USER in Docker README
-
- Apr 03, 2019
-
-
Anders authored
Make synapse_port_db --curses work with Python 3. Signed-off-by:
Anders Jensen-Waud <anders@jensenwaud.com>
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
Andrew Morgan authored
-
Richard van der Hoff authored
This is a bit fiddly due to the keyring doing weird things with logcontexts.
-
Neil Johnson authored
Remove presence list support as per MSC 1819
-
Erik Johnston authored
Implement MSC1915 - 3PID unbind APIs
-
Amber Brown authored
-
- Apr 02, 2019
-
-
Erik Johnston authored
Make starting pushers faster during start up
-
Erik Johnston authored
-
Andrew Morgan authored
Transfers the m.room.related_groups state event on room upgrade.
-
Erik Johnston authored
-
Richard van der Hoff authored
As requested by @andrewshadura
-
Erik Johnston authored
We start all pushers on start up and immediately start a background process to fetch push to send. This makes start up incredibly painful when dealing with many pushers. Instead, let's do a quick fast DB check to see if there *may* be push to send and only start the background processes for those pushers. We also stagger starting up and doing those checks so that we don't try and handle all pushers at once.
-
Richard van der Hoff authored
Hopefully this time we really will fix #4422. We need to make sure that the cache on `get_rooms_for_user_with_stream_ordering` is invalidated *before* the SyncHandler is notified for the new events, and we can now do so reliably via the `events` stream.
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
-
- Apr 01, 2019
-
-
Neil Johnson authored
test threepid checking
-
Erik Johnston authored
-
Erik Johnston authored
-
Erik Johnston authored
We assume, as we did before, that users bound their threepid to one of the trusted identity servers. So we simply fill the new table with all threepids in `user_threepids` joined with the trusted identity servers.
-
Erik Johnston authored
By default the homeserver will use the identity server used during the binding of the 3PID to unbind the 3PID. However, we need to allow clients to explicitly ask the homeserver to unbind via a particular identity server, for the case where the 3PID was bound out of band from the homeserver. Implements MSC915.
-
Erik Johnston authored
This changes the behaviour from using the server specified trusted identity server to using the IS that used during the binding of the 3PID, if known. This is the behaviour specified by MSC1915.
-
Erik Johnston authored
This will then be used to know which IS to default to when unbinding the threepid.
-
manuroe authored
start.sh: Fix the --no-rate-limit option for messages
-
Neil Johnson authored
-
manuroe authored
start.sh: Fix the --no-rate-limit option for messages and make it bypass rate limit on registration and login too.
-
Neil Johnson authored
-
Richard van der Hoff authored
Collect all the things that make room-versions different to one another into one place, so that it's easier to define new room versions.
-