Joined and invite user counts are now sent in the /sync room summaries Support for ignoring users has been added Support for room upgrades via the /room//upgrade endpoint has been added (contributed by DavidSpenler, alexkursell) The _inbound and _outbound configuration options allow configuring inbound and outbound presence separately.It's also a recommended upgrade if you are running a Dendrite deployment. This week we released Dendrite 0.8.0, which is primarily a feature release, and then Dendrite 0.8.1 which fixes an emergency bug. Read all about this, and more, in the release announcement on the blog! □ Dendrite / gomatrixserverlib ( website) But now that it has been mostly replaced by spaces, we have decided to retire this feature, which we thank dearly for its 4 years of good and loyal service to the federation. This is a feature we introduced back in 2017, and was the predecessor of Matrix spaces. This version of Synapse also deprecates the groups/communities feature of Matrix. This is an attempt at reducing the likelihood of spam across the federation, as most cases of abuse we've observed over time usually involves the attacker(s) finding homeservers with open registration and automatically creating a lot of accounts on them in order to evade sanctions. One of the main changes included in this version is that Synapse will now refuse to start if configured with open registration with no verification (e.g. This week, we've released Synapse 1.56! It includes only a couple of new features but quite a few bug fixes and internal improvements. Synapse is a Matrix homeserver implementation developed by the core team So many MSCs are in the open state, which is why we're continually looking at merging MSCs which are ready to go. It's currently missing an implementation if someone is looking for a medium complexity contribution this weekend □ The Chart It's a small but interesting MSC which helps clean up account data on the server when it's no longer needed, though how this sort of removal gets represented to clients can be a challenge. The script has elected MSC3391: Removing account data as the random MSC this week. If you have MSCs which you'd like included, please stop by the #sct-office: on Matrix with your suggestions - if they're near enough, we'll try to get them in. We're also thinking about what the next release (v1.3) looks like and when we'll end up putting it out into the world. In terms of Spec Core Team MSC focus for this week, we've been largely looking at proposals which are at or near FCP in an effort to get them through the last stages of the process. ![]() MSC3767: Time based notification filtering.MSC3666: Bundled aggregations for server side search (merge).MSC3700: Deprecate plaintext sender key (merge).Learn more about how the process works at. Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. is finally here as a tracker for our progress on P2P Matrix Dept of Spec □ Matrix Live □ Today's Matrix Live: Dept of Status of Matrix □️
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |