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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Support membership events and more camelcase/underscores	David Baker	2015-01-26	2	-4/+8
\|
*	Pushers should only try & look for rejected devices in something that's a ↵	David Baker	2015-01-26	1	-1/+1
\| \| \| \|	list or tuple.
*	Use push settings!	David Baker	2015-01-23	2	-12/+88
\|
*	more pep8 suggestions	David Baker	2015-01-23	1	-2/+1
\|
*	use underscores everywhere, not camelcase.	David Baker	2015-01-20	1	-3/+3
\|
*	add instance_handles to pushers so we have a way to refer to them even if ↵	David Baker	2015-01-20	3	-5/+10
\| \| \| \|	the push token changes.
*	Require device language when adding a pusher.	David Baker	2015-01-16	1	-3/+5
\| \| \| \| \|	Because this seems like it might be useful to do sooner rather than later.
*	Send room name and first alias in notification poke.	David Baker	2015-01-15	2	-3/+26
\|
*	Don't make the pushers' event streams cause people to appear online	David Baker	2015-01-15	1	-1/+3
\|
*	Honour the 'rejected' return from push gateways	David Baker	2015-01-13	3	-8/+56
\| \| \| \| \| \| \|	Add a timestamp to push tokens so we know the last time they we got them from the device. Send it to the push gateways so it can determine whether its failure is more recent than the token. Stop and remove pushers that have been rejected.
*	Split out function to decide whether to notify or a given event	David Baker	2015-01-13	1	-2/+17
\|
*	If we didn't get any events, advance the token or we'll just keep not ↵	David Baker	2014-12-18	1	-0/+1
\| \| \| \|	getting the same events again.
*	after a few rethinks, a working implementation of pushers.	David Baker	2014-12-18	3	-36/+48
\|
*	Update to app_id / app_instance_id (partially) and mangle to be PEP8 compliant.	David Baker	2014-12-03	3	-92/+155
\|
*	More work on pushers. Attempt to do HTTP pokes. Not sure if the actual HTTP ↵	David Baker	2014-11-21	3	-16/+105
\| \| \| \|	pokes work or not yet but the retry semantics are pretty good.
*	remove random half-line	David Baker	2014-11-19	1	-1/+0
\|
*	Start creating a module to do generic notifications (just prints them to ↵	David Baker	2014-11-19	3	-0/+210
	stdout currently!)