-
v0.8.1d028207a · ·
Changes in synapse v0.8.1 (2015-03-18) ====================================== * Disable registration by default. New users can be added using the command ``register_new_matrix_user`` or by enabling registration in the config. * Add metrics to synapse. To enable metrics use config options ``enable_metrics`` and ``metrics_port``. * Fix bug where banning only kicked the user.
-
v0.8.0d5174065 · ·
Changes in synapse v0.8.0 (2015-03-06) ====================================== General: * Add support for registration fallback. This is a page hosted on the server which allows a user to register for an account, regardless of what client they are using (e.g. mobile devices). * Added new default push rules and made them configurable by clients: * Suppress all notice messages. * Notify when invited to a new room. * Notify for messages that don't match any rule. * Notify on incoming call. Federation: * Added per host server side rate-limiting of incoming federation requests. * Added a ``/get_missing_events/`` API to federation to reduce number of ``/events/`` requests. Configuration: * Added configuration option to disable registration: ``disable_registration``. * Added configuration option to change soft limit of number of open file descriptors: ``soft_file_limit``. * Make ``tls_private_key_path`` optional when running with ``no_tls``. Application services: * Application services can now poll on the CS API ``/events`` for their events, by providing their application service ``access_token``. * Added exclusive namespace support to application services API.
-
v0.7.1894a89d9 · ·
v0.7.1 Changes in synapse v0.7.1 (2015-02-19) ====================================== * Initial alpha implementation of parts of the Application Services API. Including: - AS Registration / Unregistration - User Query API - Room Alias Query API - Push transport for receiving events. - User/Alias namespace admin control * Add cache when fetching events from remote servers to stop repeatedly fetching events with bad signatures. * Respect the per remote server retry scheme when fetching both events and server keys to reduce the number of times we send requests to dead servers. * Inform remote servers when the local server fails to handle a received event. * Turn off python bytecode generation due to problems experienced when upgrading from previous versions.