moar links

content/blog/2024/12/2024-12-25-the-matrix-holiday-update-2024.md

@@ -30,7 +30,7 @@ Matrix 2.0 is the project to ensure that Matrix can be used to build apps which
 
 All of these projects are big, and we’ve been taking the time to iterate and get things right rather than cut corners – the whole name of the game has been to take Matrix from 1.0 (it works) to 2.0 (it works fast and delightfully, and outperforms the others).  However, in September at the Matrix Conference we got to the point of shipping working implementations of all of the Matrix 2.0 MSCs, with the expectation of using these implementations to prove the viability of the MSCs and so propose them for merging into the spec proper.
 
-Sliding Sync ended up evolving into MSC4186: Simplified Sliding Sync, and is now natively integrated into Synapse (no more need to run a sliding sync proxy!) and deployed on matrix.org, and implemented in matrix-rust-sdk and matrix-js-sdk.  MatrixRTC is MSC4143 and dependents and is also deployed on matrix.org and call.element.io. Invisible Cryptography is a mix of MSCs: MSC4161 (Crypto terminology for non-technical users), MSC4153 (Exclude non-cross-signed devices), MSC3834 (Opportunistic user key pinning (TOFU)), and is mostly now implemented in matrix-rust-sdk - and Unable To Decrypt problems have been radically reduced (see [Kegan’s excellent Matrix Conference talk](https://www.youtube.com/watch?v=FHzh2Y7BABQ) for details).  Finally, Next Gen Auth is MSC3861 and is planned to be deployed on matrix.org via matrix-authentication-service in Feb 2025.
+Sliding Sync ended up evolving into [MSC4186](https://github.com/matrix-org/matrix-spec-proposals/pull/4186): Simplified Sliding Sync, and is now natively integrated into Synapse (no more need to run a sliding sync proxy!) and deployed on matrix.org, and implemented in matrix-rust-sdk and matrix-js-sdk.  MatrixRTC is [MSC4143](https://github.com/matrix-org/matrix-spec-proposals/pull/4143) and dependents and is also deployed on matrix.org and call.element.io. Invisible Cryptography is a mix of MSCs: [MSC4161](https://github.com/matrix-org/matrix-spec-proposals/pull/4161) (Crypto terminology for non-technical users), [MSC4153](https://github.com/matrix-org/matrix-spec-proposals/pull/4153) (Exclude non-cross-signed devices), [MSC3834](https://github.com/matrix-org/matrix-spec-proposals/pull/3834) (Opportunistic user key pinning (TOFU)), and is mostly now implemented in matrix-rust-sdk - and Unable To Decrypt problems have been radically reduced (see [Kegan’s excellent Matrix Conference talk](https://www.youtube.com/watch?v=FHzh2Y7BABQ) for details).  Finally, Next Gen Auth is [MSC3861](https://github.com/matrix-org/matrix-spec-proposals/pull/3861) and is planned to be deployed on matrix.org via [matrix-authentication-service](https://github.com/element-hq/matrix-authentication-service) in Feb 2025.
 
 It’s been controversial to ship Matrix 2.0 implementations prior to the MSCs being fully finalised and merged, but given the MSCs are backwards compatible with Matrix 1.0, and there’s unquestionable benefit to the ecosystem in getting these step-changes in the hands of users ASAP, we believe the aggressive roll-out is justified. Meanwhile, now the implementations are out and post-launch teething issues have largely been resolved, the MSCs will progress forwards.
 
@@ -52,7 +52,7 @@ Talking of The Matrix Conference - this was by far the highlight of the year; no
 
 One of the most interesting dynamics was that by far the busiest track was the Public Sector talk track (sponsored by Element) – standing room only, with folks queuing outside or watching the livefeed, whether this was [Gematik talking about Matrix](https://www.youtube.com/watch?v=MoA2cYfHlyA) powering communications for the German healthcare industry, [SwissPost showing off their nationwide Matrix deployment](https://www.youtube.com/watch?v=EIRuxDuWIDE) for Switzerland, [DINUM showing off Tchap](https://www.youtube.com/watch?v=m1roliPrNqc) for France, [NATO explaining NI²CE](https://www.youtube.com/watch?v=4aswIHJRwkk) (their Matrix messenger), [Försäkringskassen showing off Matrix for Sweden](https://www.youtube.com/watch?v=XLt70u0btsM) with SAFOS, [Tele2 showcasing Tele2 Samarbete](https://www.youtube.com/watch?v=Oan-bx84ui8) (Matrix based collaboration from one of Sweden’s main telcos), FITKO explaining how to do [Government-to-Citizen communication with Matrix in Germany](https://www.youtube.com/watch?v=Fj_tBpTlBEE), [ZenDiS using Matrix for secure communication](https://www.youtube.com/watch?v=oMxxfRiaN98) in the German sovereign workspace openDesk project, or [IBM showing off their Matrix healthcare deployments](https://www.youtube.com/watch?v=uRaKEw6Wo3U).
 
-This felt really surprising: not only are we in an era where Matrix appears to be completely dominating secure communication and collaboration in the public sector – and it’s not just GovTech folks interested, but the wider Matrix community too.
+This felt really surprising: not only are we in an era where Matrix appears to be completely dominating secure communication and collaboration in the public sector – but it’s not just GovTech folks interested, but the wider Matrix community too.
 
 I think it’s fair to say that when we created Matrix, we didn’t entirely anticipate this super-strong interest from government deployments – although in retrospect it makes perfect sense, given that more than anyone, nations wish to control their own infrastructure and run it securely without being operationally dependent on centralised solutions run out of other countries.  A particular eye-opener recently has been seeing US Senators Ron Wyden (D) and Eric Schmitt (R) [campaigning for the US Government to deploy Matrix](https://element.io/blog/senators-implore-department-of-defense-to-expand-the-use-of-matrix/) in a way similar to France, Germany, Sweden and others. If this comes to pass, then it will surely create a whole new level of Matrix momentum!