#Opal viewer lite switch images how to#
#Opal viewer lite switch images upgrade#
#Opal viewer lite switch images registration#

These are just the highlights please see the Upgrade Notes and Release Notes for a complete list of changes in this release.

Concurrently fetching the same large set of events ( #10703) is now much more efficient, preventing the process hangs which were possible in prior, extreme cases.Backfilling history and fetching missing events now use the same code paths, reducing the potential for bugs.Code around federation event handling and authentication has been significantly refactored to improve reliability and maintainability, including extracting nearly 1,800 lines of code from the FederationHandler class into a separate FederationEventHandler class.Custom Presence Router modules can now be built using Synapse's new, unified module interface which debuted in Synapse 1.37.In addition to the usual array of improvements to performance, type hints, error messages, and documentation: Support for MSC3283: Expose capabilities for profile actions, which hints to clients whether or not a server allows users to change their display name, avatar, or email address. This MSC and its implementations were produced as part of a Google Summer of Code (GSoC) project by Callum Brown.Р”Р„n updated implementation of MSC2946: Spaces Summary following recent changes to the proposal.

#Opal viewer lite switch images registration#

In addition to Room Version 9 ( MSC3375), this release includes:Р”Р„n initial implementation of MSC3231: Token authenticated registration, which makes it possible for homeservers to disable user registration while still allowing new accounts to be made by people who know a pre-shared secret. This prevents them from appearing in your client, though you may need to empty your client's cache and re-sync to see any effect. In Synapse 1.42, rooms with unknown room versions are no longer returned down /sync. And if you can't interact with that room, you can't leave.

#Opal viewer lite switch images how to#

The server no longer understands how to interact with that room version, which means you can't interact with that room. Then, when Synapse removes support for these versions, bad things happen.

Very rarely, users find themselves in rooms created with unstable or experimental room versions. A future release of Synapse will ask clients to prefer Room Version 9 for restricted rooms. To ensure compatibility with existing servers, Synapse 1.42's MSC3244: Room version capabilities hints will continue to ask clients to prefer Room Version 8 when creating restricted rooms and Room Version 6 otherwise. This makes it possible, in certain circumstances, for a restricted room to degrade into a state where participating servers will disagree about the room's membership.Р”В«ecause changing a room version's redaction algorithm also changes the way that event IDs are calculated, properly fixing this issue required the creation of a new room version. Synapse 1.42 includes support for Room Version 9, which fixes an oversight in the list of event fields which were protected from redaction in Room Version 8's restricted rooms.

Room Version 9: A Bugfix for Restricted Rooms Please see the Upgrade Notes for details. This release includes changes that you may need to be aware of before upgrading, such as the removal of two deprecated Admin APIs or a retroactive fix to ensure that email notifications are only sent to addresses which are presently associated with an account.