matrix/thirdparty/synapse.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove the deprecated Handlers object (#8494)	Patrick Cloke	2020-10-09	1	-1/+1
\| \| \|	All handlers now available via get_*_handler() methods on the HomeServer.
*	Invalidate the cache when an olm fallback key is uploaded (#8501)	Hubert Chathi	2020-10-08	1	-0/+20
\|
*	Add support for MSC2732: olm fallback keys (#8312)	Hubert Chathi	2020-10-06	1	-0/+65
\|
*	Simplify super() calls to Python 3 syntax. (#8344)	Patrick Cloke	2020-09-18	1	-1/+1
\| \| \| \| \| \| \|	This converts calls like super(Foo, self) -> super(). Generated with: sed -i "" -Ee 's/super\([^\(]+\)/super()/g' */.py
*	Convert device handler to async/await (#7871)	Patrick Cloke	2020-07-17	1	-4/+6
\|
*	Convert E2E key and room key handlers to async/await. (#7851)	Patrick Cloke	2020-07-15	1	-112/+174
\|
*	isort 5 compatibility (#7786)	Will Hunt	2020-07-05	1	-3/+1
\| \| \|	The CI appears to use the latest version of isort, which is a problem when isort gets a major version bump. Rather than try to pin the version, I've done the necessary to make isort5 happy with synapse.
*	Add option to enable encryption by default for new rooms (#7639)	Andrew Morgan	2020-06-10	1	-4/+14
\| \| \| \| \| \| \| \| \|	Fixes https://github.com/matrix-org/synapse/issues/2431 Adds config option `encryption_enabled_by_default_for_room_type`, which determines whether encryption should be enabled with the default encryption algorithm in private or public rooms upon creation. Whether the room is private or public is decided based upon the room creation preset that is used. Part of this PR is also pulling out all of the individual instances of `m.megolm.v1.aes-sha2` into a constant variable to eliminate typos ala https://github.com/matrix-org/synapse/pull/7637 Based on #7637
*	Fix encryption algorithm typos in tests/comments (#7637)	Andrew Morgan	2020-06-04	1	-5/+5
\| \| \| \| \| \| \| \|	@uhoreg has confirmed these were both typos. They are only in comments and tests though, rather than anything critical. Introduced in: * https://github.com/matrix-org/synapse/pull/7157 * https://github.com/matrix-org/synapse/pull/5726
*	look up cross-signing keys from the DB in bulk (#6486)	Hubert Chathi	2019-12-12	1	-8/+0
\|
*	Back out perf regression from get_cross_signing_keys_from_cache. (#6494)	Neil Johnson	2019-12-09	1	-0/+8
\| \| \|	Back out cross-signing code added in Synapse 1.5.0, which caused a performance regression.
*	use something that's the right type for user_id	Hubert Chathi	2019-09-06	1	-1/+1
\|
*	fix test	Hubert Chathi	2019-09-05	1	-1/+3
\|
*	add test	Hubert Chathi	2019-09-04	1	-0/+88
\|
*	make isort happy	Hubert Chathi	2019-09-04	1	-0/+1
\|
*	make black happy	Hubert Chathi	2019-09-04	1	-85/+62
\|
*	allow uploading signatures of master key signed by devices	Hubert Chathi	2019-09-04	1	-1/+226
\|
*	fix formatting	Hubert Chathi	2019-08-01	1	-1/+3
\|
*	allow uploading keys for cross-signing	Hubert Chathi	2019-07-25	1	-0/+63
\|
*	Run tests under PostgreSQL (#3423)	Amber Brown	2018-08-13	1	-1/+1
\|
*	Run black.	black	2018-08-10	1	-65/+34
\|
*	run isort	Amber Brown	2018-07-09	1	-2/+3
\|
*	s/replication_client/federation_client/	Erik Johnston	2018-03-13	1	-1/+1
\|
*	Fix tests	Erik Johnston	2018-03-13	1	-1/+1
\|
*	Remove spurious unittest.DEBUG	Richard van der Hoff	2018-01-26	1	-1/+0
\|
*	Do some logging when one-time-keys get claimed	Richard van der Hoff	2017-05-09	1	-0/+34
\| \| \| \| \|	might help us figure out if https://github.com/vector-im/riot-web/issues/3868 has happened.
*	Allow clients to upload one-time-keys with new sigs	Richard van der Hoff	2017-05-09	1	-0/+98
\| \| \| \| \| \| \|	When a client retries a key upload, don't give an error if the signature has changed (but the key is the same). Fixes https://github.com/vector-im/riot-android/issues/1208, hopefully.
*	keys/query: return all users which were asked for	Richard van der Hoff	2016-08-03	1	-0/+46
	In the situation where all of a user's devices get deleted, we want to indicate this to a client, so we want to return an empty dictionary, rather than nothing at all.