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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Merge branch 'develop' of github.com:matrix-org/synapse into ↵	Erik Johnston	2017-03-14	1	-0/+34
\|\ \| \| \| \| \| \|	erikj/public_list_speed
\| *	Implement _simple_delete_many_txn, use it to delete devices	Luke Barnard	2017-03-13	1	-0/+34
\| \| \| \| \| \| \| \| \| \| \| \|	(But this doesn't implement the same for deleting access tokens or e2e keys. Also respond to code review.
* \|	Get current state by using current_state_events table	Erik Johnston	2017-03-10	1	-1/+1
\|/
*	Don't keep around old stream IDs forever	Erik Johnston	2017-03-03	1	-2/+9
\|
*	Spelling	Erik Johnston	2017-03-03	1	-2/+2
\|
*	Fix device list update to not constantly resync	Erik Johnston	2017-03-01	1	-46/+115
\|
*	Fix bugs in the /keys/changes api	Richard van der Hoff	2017-02-14	1	-9/+29
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* `get_forward_extremeties_for_room` takes a numeric `stream_ordering`. We were passing a `RoomStreamToken`, which meant that it returned the current extremities, rather than those corresponding to the `from_token`. However: * `get_state_ids_for_events` required a second ('types') parameter; this meant that a `TypeError` was thrown and we ended up acting as though there was no prev state. * `get_state_ids_for_events` actually returns a map from event_id to state dictionary - just looking up the state keys in it again meant that we acted as though there was no prev state. We now check if each member's state has changed since any of the extremities. Also add/fix some comments.
*	Measure new device list stuff	Erik Johnston	2017-02-02	1	-0/+4
\|
*	Use new get_users_who_share_room_with_user	Erik Johnston	2017-02-02	1	-11/+13
\|
*	Use stream_ordering_to_exterm for /keys/changes	Erik Johnston	2017-02-02	1	-9/+9
\|
*	Doc args	Erik Johnston	2017-02-01	1	-0/+7
\|
*	Include newly joined users in /keys/changes API	Erik Johnston	2017-02-01	1	-4/+35
\|
*	Implement /keys/changes	Erik Johnston	2017-02-01	1	-0/+16
\|
*	Use get_users_in_room and declare it iterable	Erik Johnston	2017-01-30	1	-1/+1
\|
*	Hook device list updates to replication	Erik Johnston	2017-01-27	1	-16/+0
\|
*	Better name	Erik Johnston	2017-01-27	1	-1/+3
\|
*	Handle users leaving rooms	Erik Johnston	2017-01-26	1	-1/+16
\|
*	Add comments	Erik Johnston	2017-01-26	1	-3/+16
\|
*	Implement device key caching over federation	Erik Johnston	2017-01-26	1	-12/+73
\|
*	Fix up sending of m.device_list_update edus	Erik Johnston	2017-01-25	1	-0/+1
\|
*	Add basic implementation of local device list changes	Erik Johnston	2017-01-25	1	-12/+53
\|
*	make device IDs more useful for human disambiguation	Matthew Hodgson	2016-09-13	1	-1/+1
\|
*	PEP8	Richard van der Hoff	2016-08-03	1	-1/+1
\|
*	Default device_display_name to null	Richard van der Hoff	2016-08-03	1	-1/+1
\| \| \| \| \| \|	It turns out that it's more useful to return a null device display name (and let clients decide how to handle it: eg, falling back to device_id) than using a constant string like "unknown device".
*	Delete e2e keys on device delete	Richard van der Hoff	2016-07-27	1	-0/+4
\|
*	Delete refresh tokens when deleting devices	Richard van der Hoff	2016-07-26	1	-2/+4
\|
*	Implement updating devices	Richard van der Hoff	2016-07-26	1	-0/+24
\| \| \| \|	You can update the displayname of devices now.
*	Implement deleting devices	Richard van der Hoff	2016-07-26	1	-1/+26
\|
*	make /devices return a list	Richard van der Hoff	2016-07-21	1	-5/+5
\| \| \| \|	Turns out I specced this to return a list of devices rather than a dict of them
*	Fix PEP8 errors	Richard van der Hoff	2016-07-21	1	-1/+1
\|
*	Implement GET /device/{deviceId}	Richard van der Hoff	2016-07-21	1	-9/+37
\|
*	GET /devices endpoint	Richard van der Hoff	2016-07-20	1	-0/+27
\| \| \| \| \| \| \|	implement a GET /devices endpoint which lists all of the user's devices. It also returns the last IP where we saw that device, so there is some dancing to fish that out of the user_ips table.
*	Add device_id support to /login	Richard van der Hoff	2016-07-18	1	-0/+71
	Add a 'devices' table to the storage, as well as a 'device_id' column to refresh_tokens. Allow the client to pass a device_id, and initial_device_display_name, to /login. If login is successful, then register the device in the devices table if it wasn't known already. If no device_id was supplied, make one up. Associate the device_id with the access token and refresh token, so that we can get at it again later. Ensure that the device_id is copied from the refresh token to the access_token when the token is refreshed.