*Matrix Conference preroll music*
Matthew Hodgson: Right good morning everybody I'm Matthew Hodgson I'm the
Matthew: project lead for Matrix and I am not
Matthew: going to talk about money I'm going to talk about technology and talk about
Matthew: where Matrix is. Or am I? Let's face it the world needs Matrix more than ever
Matthew: today we see all sorts of fragmentation happening we see attacks on encryption
Matthew: with chat control and the online safety acts and... Well,
Matthew: we're basically living in a pretty dark timeline in the grand scheme of things.
Matthew: And as Amandine says, Matrix aspires to be the missing communication layer of the open web.
Matthew: And my God, does the web need a secure, open, defragmented communication layer today
Matthew: Now, Matrix really feels like it's growing up. Like if I, 11 years ago,
Matthew: when we began this, imagine standing on stage and having the Ministry of Digital
Matthew: of France on stage saying, "Hey, we're joining Matrix to support it financially",
Matthew: I just wouldn't have believed it.
Matthew: And nowadays, looking around, honestly, I'm in a pretty good mood.
Matthew: I mean, over the last couple of years, I've been a little bit stressed at points.
Matthew: Whereas today, I'm actually feeling that we're in a pretty good place.
Matthew: We have all of the pieces needed to outcompete the centralized alternatives,
Matthew: and it is actually happening. so we have an impressively diverse ecosystem.
Matthew: So apologies to the other bits of the ecosystem, but I'm going to go and drill
Matthew: down and look at clients.
Matthew: So I was trying to figure out how can we do a map of clients out there.
Matthew: Now, obviously, there are hundreds of Matrix clients now.
Matthew: Some of them are little proof of concepts.
Matthew: Some of them are enormous organizations and companies and everything in between.
Matthew: So apologies profusely, if in the map that I'm about to lay out,
Matthew: I'm missing you or your favorite client.
Matthew: But I've gone and tried to cherry pick kind of representative ones.
Matthew: And I'm going to start with Beeper. So I saw the Beeper team last night and
Matthew: said, guys, you're going to get a massive call out in the keynote.
Matthew: And here you are, here it is.
Matthew: So Beeper, excellent, excellent app.
Matthew: Interesting stack. So they're built on Go as the underlying libraries using
Matthew: Tulir's wonderful Mautrix infrastructure. structure, then they're using native
Matthew: mobile UI on the mobile apps.
Matthew: So that's if UI and UI kit on iOS, Compose on Android, and then Beeper itself on top.
Matthew: I at least think of Beeper as a third generation app, in that the original ones
Matthew: were a fork of Element, or actually a fork of Element's second generation apps.
Matthew: And it has now been completely rebuilt as a completely separate,
Matthew: unique stack, which is pretty cool.
Matthew: If you like Go, and you were wanting to build on the Go ecosystem,
Matthew: you can go wild with Beeper.
Matthew: Now, my original plan is to then go and start screen sharing little demos of
Matthew: all of these, although I'm not sure whether I'm going to really have enough time.
Matthew: But let me risk it and see if I open up QuickTime, and if it gives me permission,
Matthew: come on QuickTime, to go and start a movie recording, and...
Matthew: Oh, yeah, there we go. So here's people everybody.
Matthew: Let me see if I can actually make that go full screen. So you can see me just
Matthew: talking to myself on Matrix network going and sending free photos.
Matthew: Also, you might see actually, yeah, I'm not actually online.
Matthew: I don't know why it says... It's got fake UI on it. So I'm not actually online
Matthew: right now. So it's got excellent offline support.
Matthew: I can even view things offline. You can see I'm not actually using this account
Matthew: very much. and it's a nice, beautiful iOS native stack.
Matthew: So that's Beeper. Where's my actual deck gone?
Matthew: Then looking at this sort of architecture, it's not a million miles away from Element X.
Matthew: I'm probably biased being CEO of Element, but Element X, again,
Matthew: third generation app built not on top of Go, but on top of Rust,
Matthew: everybody's favorite crustration language.
Matthew: Similar architecture though, the again, third gen Matrix Rust SDK that is owned
Matthew: by the Matrix Foundation,
Matthew: albeit very funded by Element which then
Matthew: goes and loops things into mobile native ui. You
Matthew: have element x on top and if I were to pop over to my Element X here I'm sure
Matthew: that many people have seen this thing already looks like this. Now some of the
Matthew: things to call out here is that we've got nice stuff like liquid glass whether
Matthew: you love it or hate it you can see at the bottom we've got our new space view,
Matthew: which is new in Element X, you got the chats.
Matthew: And again, I'm actually offline, even though claims that I am online here,
Matthew: I could go and hop into one of these rooms. And you can see we have offline support.
Matthew: We can also see that hides images by default. So part of the trust and safety stuff on public rooms.
Matthew: Although even though I'm offline, I can still hit the show button and put them in.
Matthew: So I mean, again, this is because it's using a native UI that you get things
Matthew: like iOS 26 and liquid glass for free.
Matthew: Then on top of Rust, you have entirely different apps. So it's Fractal. Who uses Fractal?
Matthew: Not that many people. You're missing out because it's a really pretty app.
Matthew: I've got it running, I hope, in a Ubuntu VM, right here.
Matthew: You can see it sitting here in TWIM .
Matthew: And I know just to give an idea of the kind of quality that you have here.
Matthew: If you go into settings, you got a really nice set of UI for managing your notifications,
Matthew: your safety settings, your encryption stuff.
Matthew: Frankly, the UI is something definitely on a level, if not beyond something like Element X, etc.
Matthew: Then, and also on top of Rust, you've got a totally different stack. He uses Robrix.
Matthew: Come on, Kevin, where are you? Yeah, there he is at the back.
Matthew: So Robrix is a really interesting project done by Futurewei to build on top
Matthew: of native Rust UI rather than GTK4 like Fractal, again building on top of Rust SDK.
Matthew: And it looks like this sort of thing.
Matthew: So I mean, this is, again, we've got offline support here because I've turned off my Wi Fi.
Matthew: You can see here on TWIM, we've got things like a tileable UI.
Matthew: So I can go and drag down, or hopefully drag down one of these windows,
Matthew: like, in theory, come on, that, and have a sort of split view approach.
Matthew: And have of both say the synchronous to Mozilla room alongside the TWIM room there.
Matthew: Again, really polished glossy app built on an entirely different UI stack,
Matthew: albeit using Rust SDK funded by Futurewei, which is adjacent to Huawei as one
Matthew: of the world's biggest companies.
Matthew: Then Filament, who's on Filament?
Matthew: Nobody. That's because it hasn't launched yet. However, I spoke to Tony,
Matthew: who's the CEO at Filament last night and said, "Oi, Tony, is it okay if I demo
Matthew: this in my keynote?" And he said: "yeah, go nuts".
Matthew: So here is hopefully Filament.
Matthew: If it launches. Now I've had to turn my Wi-Fi on because it doesn't have offline mode. But here it is.
Matthew: So another Matrix client. This one isn't federated with Matrix yet,
Matthew: although I hope to convince them that they should.
Matthew: And if I go into a testing room here, you can see this has got more of a kind
Matthew: of slack vibe going on. No bubbles in there.
Matthew: I can see my DM with Tony, perhaps last night.
Matthew: He says, "feel free to do the extended razzle dazzle with jazz hands".
Matthew: So Tony, here are your jazz hands.
Matthew: This guy is built entirely in React Native on top of Rust SDK.
Matthew: So it's really interesting to see all the various different stacks here going
Matthew: and using different UI environments.
Matthew: So if you're a React developer and you love React Native, Filament have done
Matthew: amazing work in terms of going and exposing Rust SDK bindings all the way through
Matthew: to React land, and it looks great.
Matthew: And then interestingly, bit of an edge case is Flutter.
Matthew: So there's an outfit doing an app called Axiom, which I don't think it's fully
Matthew: launched yet. I can't demo it.
Matthew: But it's a particularly good stat because it's using Flutter for cross platform
Matthew: device interoperability, a bit like Fluffychat does, but built on Rust SDK.
Matthew: Then you've got Fluffychat itself. I'm sure many people use Fluffychat. Who uses Fluffychat?
Matthew: About third quarter of the room. So really nice app built by Krille and funded
Matthew: by Famedly used as the basis of all sorts of Gematik German healthcare deployments
Matthew: built on Flutter using the Matrix Dart SDK, and obviously running on Dart.
Matthew: Then you've got Kotlin platforms.
Matthew: So all the work that Connect2X are doing with the Trixinity SDK,
Matthew: Trixinity Messenger, and then on top of it, modular messengers like Tami built
Matthew: on Kotlin multi-platform.
Matthew: So this is targeting both mobile and web and desktop, all via the platform abstraction of Kotlin.
Matthew: So if you love Kotlin, you've got an incredibly mature stat there too.
Matthew: Then if you're a C++ enthusiast, you've got the various Qt options.
Matthew: So you can have Nheko running on mtrxclient on C++ using, I think, QML still.
Matthew: Nico, is it still QML? Or is it a weird mix of QT
Matthew: and QML no Nico nobody wants
Matthew: to fess up to it perhaps I got it horribly wrong who knows and
Matthew: then neochat is a kde driven
Matthew: project running again on top of QT this time using libquotient rather
Matthew: than mtxclient and finally on the web you've got matrix-js-sdk the original
Matthew: and gnarliest and most horrible Matrix SDK there is with react-sdk or
Matthew: running on react. And then finally,
Matthew: last but not least, you have, say, Cinny as a really nice desktop client,
Matthew: arguably better for people wanting a Discord replacement than Element-Web today
Matthew: built on that stack. So seriously, look at it.
Matthew: I don't think there is a single development platform not represented here for the modern developer.
Matthew: If you want React Native, you've got a best-in-class solution there.
Matthew: If you want Go, you've got a stack there.
Matthew: I cannot believe that we're at this level of diversity and maturity at this
Matthew: point in the game. It's not a monoculture.
Matthew: It's not everyone saying, oh, this will only work if we use our Rust SDK.
Matthew: Instead, each of these are completely independently written and maintained by
Matthew: different organizations.
Matthew: And at the risk of talking briefly about money, these aren't small outfits.
Matthew: Like Beeper got acquired by Automatic for, what, 125 million?
Matthew: Filament just announced 10 million of funding last week.
Matthew: I mentioned Robrix is made by Futurewei. These are big players doing big,
Matthew: exciting things on top of Matrix.
Matthew: Uptake is accelerating. Here is our 30-day retained user graph.
Matthew: So this is kind of the smallest number graph that we have, which is people who
Matthew: are on a server that reports phonehome stats to us who have been hanging around for at least 30 days.
Matthew: And from September through to September, you can see that we've gone up from
Matthew: about 270,000 R30 users on the network to about 550,000.
Matthew: So I'm going to declare that that is exponential because it's doubled,
Matthew: And this is in no way a linear graph.
Matthew: So the spec, meanwhile, is steadily improving. This one isn't exponential. This really is linear.
Matthew: You can see the total number of Matrix Spec Changes over the years since we
Matthew: started the spec process in 2019.
Matthew: It's been accelerating a little bit over the last year.
Matthew: Frankly, it's probably not a good thing if it accelerates too much because we
Matthew: don't want the spec to be constantly sprawling around, changing all the time.
Matthew: What's interesting is that all the way through, we've maintained basically a
Matthew: sort of for every two MSCs coming in, one of them goes out.
Matthew: So either gets merged into the spec, the red block, or it gets closed, the blue block.
Matthew: So I think this looks pretty healthy. You can see that we on the spec core team
Matthew: consistently cranking things through.
Matthew: People keep proposing new things, and we try to merge them in as rapidly as we possibly can.
Matthew: 10 minutes left. So let me talk a bit about Mmatrix 2.0.
Matthew: Last year, we showed off the first implementations of the MSCs that the spec
Matthew: core team had earmarked for Matrix 2.0 got into a lot of trouble for saying
Matthew: Matrix 2.0 is here by which I meant the implementations are there you can play with them in Element X,
Matthew: but obviously the MSCs were not ready at that point for merging into the spec
Matthew: which is just as well because over the year there have been a lot of refinements
Matthew: of these MSCs as we've really tested them in the wild and we've discovered I
Matthew: don't know the MatrixRTC has interesting problems here and there and whatnot.
Matthew: And so we've been polishing them away. What we were hoping for was a grand confetti
Matthew: drop at this point, where we announced Matrix 2.0 is here for real, and it's in the spec.
Matthew: We're close. We're not quite at confetti drop levels. I'll lay it out in a second.
Matthew: But the good news here is that where there are still things which we're ironing
Matthew: out, we're not going to rush it and mess it up just so that we can drop confetti on you all.
Matthew: So, first of all, talking of Confetti, are we OIDC yet? Do we have Next Gen
Matthew: Auth? And the answer is, my friends, yes, we are.
Matthew: Congratulations to the Matrix Identity team and Quentin and Hugh and everybody
Matthew: who put literally about four years of their lives into getting Matrix on the
Matthew: best possible authentication system we can have with password
Matthew: manager support, and pass keys, two-factor Auth, multi-factor Auth,
Matthew: QR login, all these amazing things.
Matthew: Got merged in April, released in Matrix 1.15, and then deployed almost immediately
Matthew: on matrix.org two days later, migrating 45 million access tokens and under half an hour.
Matthew: Go see Quentins Talk tomorrow at 16:30 all about it.
Matthew: However, the QR code log in MSC probably needs a little bit more iteration.
Matthew: Ironically, in the time that we were specing it,
Matthew: the encryption that we used got obsoleted moving from elliptic curve to rfc9180
Matthew: hybrid key encryption so we need to rework it to use non-obsolete crypto.
Matthew: Then Sliding Sync saying lots of finessing as the
Matthew: Rust SDK implementation has matured adding in threads, adding
Matthew: in spaces. We are now gathering votes for it
Matthew: to enter um final comment period in order to be merged into the spec as of a
Matthew: few weeks ago. It is stuck at the moment on whether we need to do all of the
Matthew: SSS extensions too but at least it's in the final progress now. Then MatrixRTC. So, I mean,
Matthew: MatrixRTC is a really ambitious project to do decentralized,
Matthew: end-to-end encrypted group voice and video for all of Matrix and beyond.
Matthew: Loads of work has gone into those MSCs this year, and Element Call was basically
Matthew: dogfooding it in beta, and we found all sorts of exciting challenges along the way,
Matthew: like various obscure races that
Matthew: we hadn't quite anticipated due to decentralization, permission problems,
Matthew: Do we really want to allow anybody in rooms to be able to start calls in order to join calls?,
Matthew: State bloat. If you let people start calls, are they going to fill up the room with state?
Matthew: Timing out users correctly. It's been a fun, fun, fun year for the VoIP team
Matthew: where fun is quite painful.
Matthew: We believe that these are now fixed and
Matthew: whole new edition of MSC4143 was published
Matthew: on tuesday if you like voip go read it it's
Matthew: a really good MSC it's massive it's a huge labor of love from Florian and the
Matthew: team and it has some pretty major changes. So first of all participation is now
Matthew: tracked with an entirely new type of event in Matrix. Yes, after 11 years we finally
Matthew: have... I see our VoIP developers are celebrating this.
Matthew: After 11 years, we've finally added the missing primitive, which we've called
Matthew: sticky events, which is not state, it's just stuff in a timeline that sticks
Matthew: around for like an hour so that you can reliably see who's in a call without
Matthew: having to mess around with state resolution or state.
Matthew: We've also introduced a concept called slots, which solves the race conditions.
Matthew: So you basically say a Matrix room now can have multiple RTC slots,
Matthew: And whoever is around can hop into that slot to do a call.
Matthew: And because these slots don't really have session IDs, it means that empirically,
Matthew: anybody who joins in is part of that session.
Matthew: And it solves a lot of the race conditions by slightly unintuitively removing
Matthew: the concept of session IDs.
Matthew: We should be in a much better setup for FCP now.
Matthew: The spec core team has been tracking this. I haven't heard anybody scream in
Matthew: horror yet, apart from Eric.
Matthew: So hopefully this is all on track.
Matthew: Finally, invisible crypto. Make encryption invisible to users,
Matthew: much like it is in iMessage or WhatsApp or Signal.
Matthew: This is something everybody needs to know about. The key missing ingredient
Matthew: is that all devices have to be cross-signed by their owner, and then so many
Matthew: of the weird bits of UI in Matrix will go away.
Matthew: But this is a major change. We announced it, or pre-announced it last year.
Matthew: Here we are officially announcing that we are in the endgame,
Matthew: and the clock is ticking six months from now or earlier, depending on uptake,
Matthew: we expect another MSC to mandate that all devices must be verified.
Matthew: So if you build any kind of Matrix client or bot or bridge, the clock starts
Matthew: now, we've got six months to make sure that all your devices are verified so
Matthew: we can get rid of all of the stupid "you have an unverified device" warnings.
Matthew: So to conclude, Matrix 2.0 next gen auth is there Sliding Sync is almost there
Matthew: MatrixRTC has the final MSC, but needs to go through the process.
Matthew: And Invisible Crypto is actually passed to FCP, not merged into the spec yet,
Matthew: but the clock is ticking.
Matthew: And then, based on this, we aim for the spec SPET release to actually be 2.0.
Matthew: So other stuff happening, and I've got five minutes left. Oh, Project Hydra.
Matthew: So Hydra is the codename for the multi-headed nightmare monster beast,
Matthew: which is improving state resolution in Matrix.
Matthew: And we've made huge progress on this over the last year, basically been working
Matthew: on it all year, funded by Element.
Matthew: It's ended up being a three-phase plan. First of all, basically figure out the
Matthew: problems that need to be fixed and ship a baseline solution in Room version
Matthew: 12, which happened in August.
Matthew: Then phase two we're announcing now is
Matthew: basically additional robustness now this has not yet gone
Matthew: through the MSC process this is also
Matthew: going to be done in public. Phase one
Matthew: was deliberately done under embargo because frankly we weren't
Matthew: sure what problems we were going to hit in practice the problems
Matthew: we found weren't that catastrophic and so it's one
Matthew: of these y2k things. If we hadn't done it under embargo
Matthew: you could be guaranteed that we would have found a total disaster, we did
Matthew: it under embargo and either way. Phase two
Matthew: and three we expect to be done entirely in public. Phase two is first of all
Matthew: synchronizing all room state rather than the partial setup we have today where
Matthew: you can have gaps in your rooms on the state which will improve robustness massively
Matthew: and finally shifting user ids to be account keys which is great from a GDPR perspective to.
Matthew: Then phase three is finality.
Matthew: And finality refers to making sure you can't go back in time and screw up a room, basically.
Matthew: Because in the end, a lot of the state resolution problems happen when somebody
Matthew: goes back and says, well, actually, two years ago, I found this event that made me an op.
Matthew: And then everyone has to figure out how to resolve it.
Matthew: We're going to try to stop that by basically sealing room history once all the
Matthew: servers in a room have read up to a given point and agree that that has happened.
Matthew: And then finally, there'll need to be some state res changes to reflect those
Matthew: changes. Don't miss Keegan waxing lyrical about this midday tomorrow.
Matthew: Then I've got like four minutes or three minutes or something. Trust and Safety.
Matthew: There has been a lot of much needed progress on Trust and Safety this year.
Matthew: I mean, Matrix has a huge ecosystem of developers working across safety tooling.
Matthew: This isn't just the folks hired full time by the Matrix Foundation or folks
Matthew: assisting from Element.
Matthew: This is the whole gamut. There are lots of modern moderation tools,
Matthew: including Draupnir, Meowlnir, and Mjolnir, not to be confused with Meowlnir from Tulir.
Matthew: There's a new volunteer hosting project for moderation tooling called Asgard
Matthew: Chat, which is an epic name for a set of tools named after Mjolnir.
Matthew: Loads of grassroots orgs tackling abuse on the network, like the community moderation effort.
Matthew: There's a new initiative called munin-hall.com. There is a new initiative called
Matthew: the Matrix Safety Guild to basically have a trusted cabal across the network
Matthew: of folks collaborating on trust and safety tooling.
Matthew: A big change was policy servers, giving moderators the ability to filter traffic before it hits users.
Matthew: That's been running since about May as a closed beta, open beta coming,
Matthew: I think now-ish, possibly even today.
Matthew: And then finally, that will get open sourced shortly.
Matthew: Then other things, lots of tooling to manage media preview controls.
Matthew: You already saw it in Element X, the whole show to make sure you only view images that you want to see.
Matthew: Also, invite filtering to mitigate invite spam.
Matthew: Loads of working groups and safety guild progress within the foundation itself.
Matthew: Thanks very much to the governing board for figuring out open governance in
Matthew: the matrix.org room directory. I believe the room directory will be reopened
Matthew: in a curated fashion real soon now so we can actually start using it properly again.
Matthew: And we're also a founding member of Roost.
Matthew: Amandine mentioned them earlier. Really interesting open source initiative to
Matthew: basically gather together open source trust and safety tooling from across the industry.
Matthew: And one of their first projects is this thing called Osprey,
Matthew: which is a distribution of Discord's internal trust and safety stack.
Matthew: So Discord have got like 10 people at least building nothing but developer tools
Matthew: to try to keep Discord from totally melting down.
Matthew: And they're very kindly open sourced it and so we're looking at how moderators
Matthew: could use the same kind of infrastructure and Matrix if they need to.
Matthew: Loads of stuff still to be done, though. Drawing gates, So this is a mechanism
Matthew: that says, hey, you can only join this room if you hop through a gate of some kind.
Matthew: I heard the reek have gone and built one of these recently, using it as no jump
Matthew: through the hoop before you can join my dev room.
Matthew: Reputation models is something that we're going to need. This is relative,
Matthew: not absolute reputation.
Matthew: So you're allowed to join this room if somebody has already vouched for you in your tribe.
Matthew: Discovery, server admin tools, improving what we already have.
Matthew: This trust and safety work on the core side is funded by the foundation,
Matthew: not Element, not anybody else, as well as the fun of handling the deluge of
Matthew: tickets we get to abuse at matrix.org.
Matthew: At the risk of repeating Amandine, please become a foundation member to ensure
Matthew: this work can progress, because it would really suck for everybody,
Matthew: including the governments and the big organizations who depend on Matrix,
Matthew: if a whole project collapses because it gets a reputation for abuse.
Matthew: It doesn't cost much, we just need to keep working on trust and safety.
Matthew: I'm almost done. Sorry for overrunning a few minutes. I'm sure you'll let me.
Matthew: Encryption improvements.
Matthew: Loads of work happening for sharing historical keys when you join a room.
Matthew: We have encrypted state events at last, thanks to Sky, a prototype in Element Web as of a few weeks ago.
Matthew: We also have end-to-end encrypted search happening in Rust SDK, thanks to Shrey.
Matthew: We expect to resume work on post-quantum in November.
Matthew: So many thanks to those who are funding Element to make post-quantum happen.
Matthew: I think it's basically a done deal at this point, but PQXDH,
Matthew: so just taking on, getting rid of the elliptic curve Diffie-Hellman,
Matthew: or more accurately, adding on to the elliptic curve Diffie-Hellman,
Matthew: the post-quantum stuff using Kyber 512 will be happening.
Matthew: In terms of MLS, lots of stuff happening.
Matthew: I know that BWI and Famedly are progressing on their MSC4256 approach,
Matthew: which effectively replaces Matrix state res with centralized MLS groups.
Matthew: Also on the Spec core team, we're looking at more incremental approaches,
Matthew: things like Phoenix's decentralized MLS IETF draft, which is based on Matrixes
Matthew: decentralized with an S MLS IETF draft.
Matthew: Also talking to these guys at Germ Network who are doing encryption for AT Proto
Matthew: with their distributed MLS IETF graph.
Matthew: On Digital Markets Act, Mimi don't have time to talk about it.
Matthew: Suffice it to say that we built a WhatsApp bridge, asked if anybody would use
Matthew: it, and nobody said yes. Mainly due to the limitations that WhatsApp have imposed on the bridge.
Matthew: If anybody does want native WhatsApp to Matrix Interop, come talk to me and
Matthew: give me lots of money, please.
Matthew: What's next? In the future, we're going to continue to laser focus on being
Matthew: the best decentralized secure comms platform in the world.
Matthew: That means that we are not going to pursue decentralized social.
Matthew: Good luck to Blue Sky and AT Proto, Mastodon, ActivityPub, Nostr, etc.
Matthew: It means that we are not going to pursue freestyle decentralized data replication.
Matthew: So good luck to our friends at AutoMerge or Beehive or the Local-First cult, etc.
Matthew: It means that we are also not going to build other crazy Sci-Fi Matrix showcases,
Matthew: please build them yourself if you if you like them,
Matthew: but the foundation is not going to be doing anything on Thirdroom or other such Sci-Fi.
Matthew: Instead, we will focus everything on building a safe global resilience secure
Matthew: comms network, which can be used
Matthew: to build decentralized alternatives to liberate us from Mr. Zuckerberg
Matthew: and for that matter, the centralization of signal the total scam that is Telegram.
Matthew: And I can insult the others too. So in practice, this means we finished Hydra,
Matthew: we need to get client controlled crypto group membership done,
Matthew: whether that's by MLS, DMLS, or client side Matrix stateres,
Matthew: we need to really improve our metadata posture, we do have encrypted state events
Matthew: and pseudo IDs on the horizon,
Matthew: we could perhaps leverage MLS to lots of T&S work,
Matthew: make sure that ecosystem driven features actually land, I promise we will get
Matthew: there in the end with the custom emoji.
Matthew: I'm sorry that everything else keeps pushing it out of the way.
Matthew: And finally, I think an interesting thing could be figuring out how other ecosystems
Matthew: can build on Matrix and to start people are AT Proto or Mastodon reinventing Matrix.
Matthew: Final announcement. Peer-to-peer Matrix, however, is not dead.
Matthew: And in fact, as of about an hour and a half ago, I had a call with the Dutch
Matthew: government who confirmed that they are funding it.
Matthew: So thank you very much to the Netherlands.
Matthew: So this is really exciting because most people might be saying,
Matthew: oh my God, Matthew's doing peer-to-peer again.
Matthew: It's like Thirdroom. We're going to get distracted and another three years will disappear.
Matthew: This is the opposite. I really think that peer-to-peer is the future here.
Matthew: It solves many problems, keeps metadata entirely on the client.
Matthew: So you solve the metadata problem.
Matthew: It provides resilience against blocking surveillance and other disasters on
Matthew: servers, obviously gives you connectivity, even if the internet's gone bang.
Matthew: And really interestingly, it mandates that we make federation really, really good.
Matthew: So part of the ulterior motives of Hydra and improving federation is to make
Matthew: sure that peer-to-peer works really well.
Matthew: On the flip side, it is an open area of research.
Matthew: Resilient overlay networks are still a really hard problem. And there basically
Matthew: aren't any apart from pinecone and nigdrazum maybe.
Matthew: And you also have potential battery
Matthew: problems, big interesting problems to solve over the next few years.
Matthew: Finally, Matrix 3.0, what are we going to do? Focus on trust and safety?
Matthew: Focus on peer to peer and metadata protection? Focus on MLS metadata protection?
Matthew: Really? Focus on Portable Matrix?
Matthew: Targeting other platforms? Or just keep it on 2.x for the rest of time and only
Matthew: nudge of the major version if we really get bored.
Matthew: Honestly, suggestions welcome, including MLS.
Matthew: Thank you, everybody else. Please support the foundation and thanks.
Matthew: And sorry for overrunning.
*applause*