Demonstration of how you might add some hooks to filter out spammy events.

We should only kick guest users if the guest access event is authorised.

I'm still unclear on what the intended behaviour for
`verify_json_objects_for_server` is, but at least I now understand the
behaviour of most of the things it calls...

Don't filter out current state events from timeline

Add support for event_id_only push format

Correctly handle leaving room in /key/changes

as really it's part of the event ID

Param in the data dict of a pusher that tells an HTTP pusher to
send just the event_id of the event it's notifying about and the
notification counts. For clients that want to go & fetch the body
of the event themselves anyway.

Send down device list change notif when member leaves/rejoins room

do tox install with pip -e

PR #2413 added an issue template, but just adding files to the project
directory upsets the packaging scripts: we need to explicitly include or
exclude them.

Move the template into a .github directory to make that easy, and to de-clutter
the root a bit.

- this ensures we end up with a working virtualenv which we can use for other
things.

Document known to work postgres version

.. because I want to make the 'install_and_run' script useful for non-synapse
jobs, which do not accept --python. In any case we set up the path here, so
sytest shouldn't be guessing it.

.. because I want to make the 'install_and_run' script useful for non-synapse
jobs, which do not accept --python. In any case we set up the path here, so
sytest shouldn't be guessing it.

Tweaks to the upgrade instructions

Improvements to the federation test client

python_dependencies: Use bcrypt module instead of py-bcrypt

so that you don't necessarily need a config file.

Add prometheus config

Issue template for Synapse

Make it read the config file, primarily.

Added instructions for checking server version.

Responding to review comments.