So everybody, good morning, afternoon, whatever we are now, sorry for the late star.
Turns out that this is an accurate representation of not just the road, some mainstream
matrix, but also the combination of HDMI and USB-C devices before me.
So I am now going to fit a probably 55 minute presentation into about 40 minutes, so buckle
up because we are going for a ride.
So first of all, hopefully everybody knows by now, matrix is an open network for
security, centralised rule, time communication.
The mission being to build the real-time communication network of the open web.
The whole idea is that no single party into your conversations, they have replicated
shared across all participating servers.
So, different graph this time, looking at the 30 day retained users.
So this is the actual secret metric that we have been staring at, it is literally on a
different platform of dashboard in the will of the Make sure
explanation offices in Chasic in London.
Looking at how many people have actually been hanging around for at least 30 days on the platform
at any given point.
So if they stop using it for more than 30 days, it is clear if they are being added
for more than 30 days, if they are being added from more than 30 days to the tele count.
And this is based on the phone home stats that synapses across all reporting
servers.
You can see that, you know, many years ago now, six years ago, we were down at a couple
of tens of thousands.
It's been growing fairly linearly, we've had some kind of more exponential phases through
to 2022, then a bit of a slow down in 2023, but then I'm happy to say in 2024 things are
moving off, indeed, since the summer things are really heading on as slightly better track
again.
So, we are here today to talk about the road to mainstream matrix, and this is a road that
has both a past and a future.
So, I warn you, if you expect me to talk an awful lot of very geeky stuff about new
MSCs, this is going to be a bit of a mix.
We're going to look at things in the bigger picture for once, so I apologize if anybody
flees in horror at this, but I promise we'll have some fun demos, which definitely
won't work, if I'm doing this off-Ham and didn't slap top, but that's fine, don't
worry about it.
So, first of all, in the past, May 2014, the dream, we sat down and said, hey, why don't
we try to build the most communication there with the web?
I mean, I already had a team of about 10 folks who've been working together for about 10 years
doing lots of sip, we wrote on Ron Vogue Stacks, and all that sort of thing, and our idea
was that we were building implementation first, called Synapse, and in fact, originally
matrix was called Project Synapse, that was the code name, and we would use this implementation
to prove the protocol, work, and try to figure it out, and then have the implement of it
when we spec it, updating the one-true spec.
This Wikipedia is anchored in reality, hopefully.
The whole idea had been that we would prioritize a killer app, a actual real-life production
code, over a theoretical protocol.
And this is, I apologize for the corporate PowerPoint, and this is the original Project Synapse
timeline before it was even called matrix, and you can see, starting in May, we go and
actually build the thing, we launch it at TechCrunch to stroke.
We then go around the world, telling people how amazing it is, including Foz Dam in February
2015, so this is our 10th year Foz Dam, and then we would try to get people to actually
use it, and you can possibly read, it says, here, get the glossy app to differentiate,
which is horrible business speed for saying, we want to have the killer app that people
can actually use.
So 2014 September, here we are at four or five or six o'clock in the morning of the TechCrunch
to stroke hackathon, weirdly enough, nobody is hacking on matrix, because it is about
six hours older at this point, and so we do so instead.
We ship Synapse, we go and ship this in called CyWeb, which became renamed matrix console,
and actually had an awful lot of stuff.
You'd have chat, you'd have one to one vote, you'd get federation in there too, I think
boy got added literally at the last hour, and again the whole idea is it would prove the
implementations and them would spark it.
And it looked like this, so this is a real screenshot from a few days before launch on
September 3rd with a stupid inception joke and the XKCT joke, and you can see even at this
point that people have got their real matrix IDs, you can see Eric on Eric J on JKI
to RE, you can see me as Arathorn on Erisphere.net, and a whole bunch of other people, and
there's ugliest sin, and if anybody can be bothered to click on that hyperlink, you would
go there in your matrix client today, and see there is still there.
The images won't work because this is pre-release, and so obviously we broke the API
at the last minute before we actually released, but it's kind of fun that we can
touch over all the way back there.
Also, during the arc fun, we made animatrix, anybody know what animatrix is?
Okay, about 10 people, so I'll show you about five seconds of a slightly cringy hack fun
pitch showing this thing off, assuming that we've got an African activity.
What we have here is a unity thing where you use in those kinematics to go and puppet
this little character, hit send, and the world's first ever Android matrix client, and
that was literally what became eventually Android, and nowadays, Alan and Android, was
written in order to take this 3D telemetry to find your own animation, a district man going
and wandering across the thing, hit send, send it to the other person, they re-render it.
This is 4 years before the emoji, hit send to add.
So what does this tell us?
We really, really want matrix to be more than chat, we want it to be mainstream, not
just for gigs, no offense, and governments, probably no offense.
We had a lot more dev skills, frankly, than product skills, we had taken building glossy
mainstream apps completely for granted, we'd done it before, but always with lots of support
before we could do it by ourselves, and also worth noting that matrix really began as this
existing, centralized team, unlike a typical force project.
So 2015, how are we going to fund this?
Still need a killer app, so let's go and build something on top of this.
We figured out there are 75 different products you can build on matrix, and really irritating
I can't find the notes from them, but I remember clearly, one of them was, hey, we should
take this animatrix thing and create an increase of visual application on it, or we could
do IoT over matrix, or we could do live video mixing for drones flying around sort of bigger
reeners, and you mix it together on matrix, or we could build virtual worlds on matrix,
we could do dating apps, or we could do gov tech comms, but seriously, it would be crazy
if governments have a bit on matrix, and what we decided in the end was to converge on this
thing that was originally codenamed Skype done right, and then subsequently got reenamed
open hangouts, as the idea of basically professional collaboration out that was open source,
how can it be?
And we called it Vector, a Vector, to push matrix out into the world, and we launched it
Oscar, which was an interesting experience, and that then became right, and became
well-eminent, and had this ugly baby blue colour theme, but that is the same code base
as element web on the day it was born, and to end encryption started at the work at the
start at the same time, I think it's interesting to note, this could be the original
sin of matrix, at least in terms of development philosophy, people who remember matrix
before E2E, but then, I suspect it felt, oh my god, this thing is going incredibly first,
I've got quite a lot of stuff, it's federation, it's amazing, state roads, my even works
on day, and then we added an answer to encryption, and frankly, everything, ground to not
a whole, but probably about 10x, so that we've been going before, because it turns out
the decentralized encryption is rather hurt, then 2015 to 2016, I just note this is premature
success, around this point, matrix is getting real attention, lots of people getting
very excited about this new protocol that will liberate us from the silos, entirely
mindful for hyping it to the heavens and back again, lots of pressure from the community
to improve the spec, because it was very much following what we had been implementing,
and the spec process wasn't there, the governance process wasn't there, it's interesting
because we ended up investing a lot of time in trying to make the spec, something that
everybody could build on, rather than actually investing in making it mainstream, and making
sure that we had a killer app that people could use, and I think it's an interesting and
very controversial viewpoint, and it's probably got people to throw rotten fruits at me,
that perhaps in retrospect, we should have ruthlessly prioritised polishing the app or an app
to drive mainstream adoption rather than perhaps prematurely focusing on the open ecosystem,
so one thought experiment is that matrix itself perhaps should not have been primarily positioned
as a protocol, matrix could have been the name of an app, which was a Trojan horse,
unashamedly for a protocol, so rather than setting the expectations from the outset,
as the missing communication layer of the web, we could have just shipped a really, really good
thing like, say, Skype, which was originally decentralized, imagine if Skype was open source,
and then you could have acted out a protocol from that, and it's interesting seeing what the
blue sky folks are up to with an 80 pro, so, again pretty controversial, but frankly it seems to
be working out for them, that they are effectively smuggling a genuinely decentralized protocol,
and under the allspices of what looks like a centralized communication network. I personally know
the guys and I believe that they are genuinely aiming to decentralise things, but they're basically
following that track that we didn't follow, and as a result, they have a really mainstream
successful decentralized social app, whereas we have been on this Escher-like infinite staircase.
2017, a new vector, if you get the gag, teams that are relevant to the work that have been happening
for matrix. At the same time, we started setting out the matrix foundation as a nonprofit
guardian to make sure that matrix would be independent from element and other commercial matrix
vendors. Community stepped up with donations to the foundation in 2017. Thank you so much,
we would never have been able to raise money element by saying, hey, look, people believe in matrix,
because they donate and fund it, and subsequently element managed to raise cash from status,
and then later from financial vcs and other investors. Something that people don't always seem
to remember is the element has spent 70-80% of its funding on basically building out matrix for
everybody, for many, many, many, many years transferring the IP through to the matrix foundation.
So then, happy days, 2018 to 2021, how's the end days? The matrix grew, matches, we finally
set one-point-owned June 2020, lots of projects and companies and organizations grew on the protocol.
Open source communities, like Foztern, Zeller, KDE, Nov, and so many others go matrix,
and government start rolling it out to provide digital softnessy. The killer apps do start to,
no, you see some hints of killer apps forming, element actually has a design and a product
team and starts fixing the baby blue color scheme we saw earlier. Beeper forks, and then
pre-exaliment, and shows that you can build a really nice killer app on top of matrix and do
lots of amazing experimental projects at the same time, this is all mindful going around saying
right, we're building the missing communication layer of the web, we need to grab as much
attention and funding as possible and show the potential and inspire people to build on it,
when people build the metaverse, they should build it on matrix, if they want to,
they should have local first matrix, we'll build pit appear, we'll do low bandwidth, we'll put
over HF radios, not anyone's in there, we've done the hydrogen for lightweight matrix,
we've got dendrite for next generation, we went and merged guest room to matrix,
3D cooling, VR demos, CRDTs, element drive, applications we on chat, and all of this inspirational
work, I think made for some fun demos at Fozden, I think at least I had fun, but it did still
a lot of energy from actually writing that killer mainstream app. So 2022, the wheels come off,
a series of unfortunate events, markets crash, post-COVID, no more investment really,
element isn't profitable, yeah, and so not on a position to raise much more investment,
having been chucking all of the dollars into matrix, now if we're playing in the ecosystem,
it's in contributing dollars at the same level, but hey, obviously it's going to be fine,
matrix is doing great, huge, strong-up to public sector, governments realise that the idea
that your country is operationally dependent on a private US tech company like Microsoft
is bananas, it makes no sense if you're like Sweden or Somedy.
And honestly, the evidence is obviously mounted since then when you see the terrifying
and easier signing key is going out the door and all of the teams comprises and
exchange compromises there have been basically people who wait up that they need to run their
own comms, which is great. And so I'm and so as hey, in order to keep funding matrix, we'll go and
focus on government implementations in a bad bid to get profitable and sustainable.
So this turns out to have two big failure modes. The government said, we want matrix, so here's
a public tender to the world, please provide us with matrix deployment. Then big system integrators
who spend their lives going and selling big IT projects to governments pitch for the tender.
They're well positioned to win because they do this all the time, they've got local staff,
they've got the billion dollars of revenue they need to qualify, they've got existing contracts,
they know the right people in the ministry and all that sort of thing. And then the tender typically
is awarded to the cheapest proposal. So in order to win the tender and keep the price term,
the SI just follows the law of capitalism and the law of the market and says, right, we will pick
up open source synapses on GitHub and we will deploy it and we will support ourselves and we will take
all of the money from the government for this tender and we will not root any of it to the upstream
project. And you think, hey, okay, that's not ideal. And it happened a few times,
exotin. And it was, and it was no bit cringy, but there we go. It turned out not to be a one-off,
particularly in 2022, basically almost every deal, I think, that we hand on the element side
for providing matrix to governments ended up disappearing to somebody who basically could win it
because they didn't have the cost of developing matrix. So this is three emojis of skull barred.
Failure mode two is a bit different. The government just says, hey, the FSFee have told me
that public money for public codes, this is a great idea. We want to make sure that all of our
development will be open source, but we don't have budget for maintenance or support fees. So what
would do is that we'll run this ourselves, otherwise, you know, we can't spend money on sort of
a recurring thing to pay for this. Well, we'll go buy some features, but sorry, we don't have
budget. Otherwise, my mind is, we'll be buying proprietary software for how expensive it could be.
So the upstream gets paid to do features, which is good, you know, all of element acts for instance
as pretty much funded by doing development like that. But then again, the features you do,
might not actually create a mainstream product. They might not be particularly coherent.
The funding is typically one-off. Say, hey, here's 500k to go and implement threads in whatever,
however, then you've got threads, which are a maintenance nightmare, and no one providing cash
to basically keep folks paid at least as their day drop to maintain it.
Boo. So survival time, this is probably end of 2023 beginning in 2024. Matrix has taken
this grunted. As a commons, hooray, we succeeded everybody. Open source creators across the
matrix ecosystem, not just element, but basically most of the matrix vendors are suffering the
same problems, because they release this open source, and there is no direct incentive for
anybody to actually pay open source project, anything. So, started to get fairly drastic at the
end of 2023. So trying to get elements available so that it can keep donating to matrix,
ironically, elements stop donating most of the work to the foundation switch from a patchy to
a GPL in order to sell a GPL exceptions to the people like the system integrators who want to
customise it. R&D projects get shelved in favor of focusing on stability and quality.
I'll give you probably a good thing for the ecosystem overall, but even then, three writing is
still posing an existential threat to the whole ecosystem. Three writing is the technical
economic term for this failure mode when people take the free thing and milk it for all its
worth and don't maintain it. Interestingly, the press is starting to notice this. There's an article
yesterday in the press about the German healthcare deployments of matrix for health insurance
companies, where there's a recurring theme that folks are picking up open source implementations,
whether it's servers from element or clients from other matrix vendors and going and using the
including as a GPL without reaching any cashback. Now, these are large amounts of money to go and
provide a service for tens of millions of citizens and users and so we're basically starting to
talk into the press and saying like this is a bit of a scandal really because it's not sustainable
if they're going to do these tenders and it then falls apart because there's nobody to write
the software, it's not going to look very good. So the press is starting to pick it up, but there is hope
there is a really simple answer. Basically, if you are buying a commercial matrix deployment
you should mandate that the upstream project is funded by buying that upstream products if they have
one. Now sometimes it's just going to be a little open source project, but these things are
complicated or when they look as if they're successful even the one man bands go and say right
I'm going to try to pay my rent using this and set up a small outfit in order to support the
development costs and the role of firm the idea is that you as somebody wanting to run a commercial
matrix deployment should just pay for what you use in order to keep the project free, free as in
labor. So only buy from people who are actually going to fund upstream maintenance and that can
be a system integrator. It can be anybody as long as you actually have a paper trail showing,
but some of that cash might go back to the paying the rent of the people who are going working on it.
So the idea is that you would normalize paying for open source products and that's as folks pay
for baratry ones. I mean we were looking at the costs, I think one of the German ministries
of how much they pay Adobe for like acrobat licenses every year or was it Microsoft for licenses
too and we're literally talking towards the billions of euros a year and then they say oh yeah
but we can't possibly we don't have the two million a year that would be needed to go and
provide some support for the matrix stuff. It's really weird thing and we just want to normalize it
so that it's not embarrassing to actually pay the people who write open source software and people
might say oh but the upstream is trying to vendor lock you and it's evil element tool whoever
going and trying to force people to buy their thing and you know there are other implementations out
there if the upstream product isn't suitable then you switch and this would then be tree
public money for public code and some people get it really right. I think the flagship here is
the center of digital sovereignty in Germany where they're literally done this. I think they work
with eight different vendors yeah brand of applause for vendors. Seriously thank you because it was
a very very helpful for the vendors to say well we were with eight different soon folks to
incorporate them into open desk we got element we got next cloud we've got open project we've got x
wiki we've got open exchange but all of these and our grand rules are that we will actually just go
and pay for their profession you supported product for stop and it was like oh my god I wish that
everybody did that and Sweden again doing the right thing. US NATO doing the right thing UK kind of trying
to do the right thing so some people definitely get it anyway where are we now? It's 2025 by the way
I would say that matrix is closer to mainstream adoption than ever. We're obviously not there yeah
no it's well 400,000 or 30 years as was the graph on the first page. The path has been winding
like a lot of matrix vendors including element but others as well have ended up focusing on
gov tech and health care to survive and as a result you end up with enterprise features getting prioritised
over the mainstream consumer and community centric features. That said what's good for gov tech
is often good for mainstream uptake to the competition here is basically what's Apple,
Signal, Snack or Teams. Now on the matrix side the strategy has been the most important stuff now
is to actually get everything fast beautiful or able to support beautiful apps and basically excellent
not necessarily chase shiny mainstream features but make sure that the underpinnings are rock solid
so the other folks whether that's people or elements or fluffy chairs or anybody have the best
possible infrastructure and APIs to build whatever killer app that happens to be and so matrix
coupon O is basically that long running project to try to ensure the matrix can support mainstream
uptake so matrix coupon O first announced to two years ago to the day in foster them on the stage
whole idea is that you make it work make it work right now and coupon O you actually make it not
so you make it fast and useable you can outcompete the mainstream apps implementations to prove
that the MSC is for matrix coupon O can work landed in September 2024 and they are next
show north which gives you a log in and two-factor off and multi-factor off native IDC and also
sort of amazing good stuff implemented all over the shop now there's a dendrite PR very kindly
contributed by someone called midnight and LNX fractal I think landed it last Friday as well
and the idea on this is that it will get turned on on matrix dot org basically as soon as the
MSC passes FCP so that we drag everybody on matrix dot org instance kicking and screaming into
the brave new IDC world feature and I will show you how cool and why that is a good thing in a few
then we've got simplified sliding sink this is instant logging instant launch instant sting
natively implemented and snaps nice will the con do we wait has landed it to
or he says PR for it this is very close to being FCP on the MSC it has one edge case I believe
remaining about handling deleted state and then matrix coupon O matrix RTC is a native
encrypt to group by calling implemented an element cool web and element acts I believe that the
famously stack also has matrix RTC support in this one we asked an incorporating feedback from the
MSCs from the September launch and then finally invisible crypto some people don't understand
invisible crypto at all and say oh this is crap that removing all of the warnings it will not be
safe anymore this is the opposite of what indisible encryption is the whole idea is to make it more safe
by removing the unactionable cryptic if you see what I did that warnings about message authenticity
or verify devices and also add identity pending to this is a big change it will require users
to verify their devices at log in but then we can just simplify the experience massively don't have
this legacy concept of where devices hanging around which are probably an attacker because they
didn't prove that they were owned by their actual owner so when we launch this at the matrix
conference in September showed off a bunch of demos and everybody said well that's nice how do I
use it and we said oh crap we kind of forgot to actually ship this in a community friendly
distribution sorry about that good news though is that on the element side there will be open
so I'll say GPL helmetshots and coming out soon and coming months in the meantime though I have a
hacky work around which is going to be very interesting to demo without my lamp so how are we
going to do this so if I can break in time it is not up and actually shell into my dangerous post
it might interest anything can you hold mic for me because we don't do break in mic anymore
burnt thank you right let's see if I can just shell in now it was literally what I was hoping
would have been fixed let me see if I can switch back to my lamp's up
I need to hurry up with this coming up
I'm going to have fun here so the problem here is I need to figure out how to shell into my
myself obviously so to come in so for a second I'm hoping that somebody might have done this but
so I'm just doing a talk
right almost there
okay so the fact that I'm using the interest demos here is going to be from the chances of
the screenshot are working and presumably now K-R-M-R we pray there we go right
that is a single most stressful SSH restart I've ever done in my life
come on please let me in no I should have messed around with SSH keys instead
and that's of course that's just a wrong password I'm probably not having a password on it
okay that's because I reset my password for me thanks guys
well at least they tested it right okay so the interest demos is this location BPS which is completely
naked and new I do have a test checkout here called element docket demo which I am going to
go yesterday and mine post
i've gone unchanged my password for me right and I am going to cut this
something out of fresh. So this is a really basic Docker compose set up that I did just
to go and be able to show off Matrix 2.0 stack for things like this. Do not use it in production.
It is. God, but not using subversion anymore, are we? Come on, focus Matthew.
The connectivity is giving me about two seconds of latency on typing here. Right. So this thing is a really, really, really simple repository.
If I go and look at it, you can see here. You've got some scripts. You've got a template for some configuration.
And if we look, what we have here, there's a set up script. So I'm going to run a set up script.
And I'm going to say, I'm going to create a new server called foster.dentress.net.
I'm going to not use MKSR. I'm going to use Let's Encrypts. I'm going to check it over to Matthew and Matrix.org.
And we're going to set up Let's Encrypt quickly. And yes, it will be nice and that the FF spam me.
And I'm pray that Let's Encrypt is not going to write limit my IP or something because that would be bad.
Right. And it's gone and set up. That's some trips to get for me. Then I do Docker compose up and we're in.
That's it.
Let's see if it even works. Oh, yeah. Come on. So again, look in the background. There's synapse.
Desperately flying around the place. And here's an element in.
Now, wait a little enough out of the box. It doesn't have.
I can't registration turned on. So I guess I should have set this running in the screen session, shouldn't I?
Let me control see on that. And perhaps set that running in a screen session instead.
Docker compose up. Right. So in the background. And I go and look at the read me and it gives you a little.
Come on, blind to run, which is to register a user. So this is using mass.
This is the Matrix 2.0 next run all stuff. And if I run that, it will say, hello. Do you want to go and create a new user?
I'll create one called Matthew. And I will give it a email address.
And I will give it a password.
Right. And that's it. Create the user. Confirm? Yes. Brilliant. So I should now be able to go over to
and sign in. Hit continue on this. And it takes me to mass. So this is now the authentication system provided not by the client by the server.
So I can help them to the username here. And trying to remember the password I just said.
And now this is quite a different setup. In the, we're giving this over.
Well, this client access to my account. Hit continue on that. Make sure that you trust it.
And hopefully, let's go back and see what's happening in my screen session.
Lots of turning around. Come on. There we go. Woo. So now enter this brand new server.
So I will disable notifications. And I will go, and then publish, I'll DM you.
Okay, right, fine. So I'll go and put an md on matrix. All here and see if Federation is going to work.
Oh, there she is. Go. Hello.
Goes in creates room. Set up recovery. Probably good idea for us to do recovery stuff.
Yeah. That was, yeah. So what happens if you type on someone else's laptop.
All right, let's get back up successful, brilliant. So do you read me?
Well, whilst I'm indeed logs in, thank God for that.
Hey, Federation.
So let's go look at the next thing, which is the matrix RTC, the native calling.
So we do still have old one to one calling, but in practice everything should be using element call these days.
We need to migrate from legacy to element call and the matrix RTC stuff.
And allow this time, and I'm going to hide my thing there. Then what this is done is to basically use a
Metroscopy widget to embed the element call web app into here and start a video call.
And Emily in there is just logging in on her phone there and hopefully going to turn up.
And even though she's on a matrix.org server, we have Federation stuff happening there.
Now you don't have Vicerin stores. I'm not going to be up to screen show my phone nicely.
So I have to use the analog gap for this bit, which is a shame because it's in some ways the best bit, but let's use.
So now let's see one of the benefits of matrix authentication service, which is I can just go here to link new device.
Give me a QR code scan, and I'm going to take.
So can you point this or, oh, you know, this is really not going to be able to show me.
I'm going to just go and scan that.
So obviously it's like, oh, so my problem that my phone doesn't have internet connectivity.
It tends that you need internet connectivity for this to work.
Right. So now it's actually done it. It gives you a check code to make sure that it was me who scanned that.
I've then gave the access to my account here and can you point this.
Yeah.
Okay. Oh, sure. Yeah. So you are.
Right. So let's get rid of this.
So you can now see there is a new login on the IP address there.
And all analog gaps sharing. This is what has happened on the iOS.
If I hit OK, then go into here to the chat with Amazon's in.
You can literally see that conversation with its end-to-end encrypted history has been synced in like that onto iOS.
So it's certainly didn't say it happened in real time, but it happened basically instantly once I gave it connectivity.
That I've now logged in on my phone on this brand new server on this brand new account using a QR code.
And if I open up the chat view here, you can see the, oh, in fact, really obviously I could do a bit to just join the call.
I'm just joined the call on this new login here.
So there I am going to unmute the video on that too.
And it's actually working.
So, sorry. Thank you.
And what this is showing here is also, we've got multiple device support now in matrix RTC.
This started off as a one-to-one call, but then we just casually added a new device.
Literally a new device in the middle of the call and just go and put a spate on it too.
If we had more time, I'd now do a screen share and take you through all the things.
But you get the idea that it's rather cool.
This, I would say, is starting to fill mainstream.
We've got discord style QR login that just works with all of the encryption state.
I didn't need to specify my home server.
I didn't need to specify my recovery key.
I didn't need to even remember my username or my password.
I just split the link and it took me in there with the same identity.
Verified out of the box.
Woo!
I'm so running out of time, but let's keep going for it.
Then other things in 2025.
No, September 24 we did the first ever global matrix conference.
It was really cool.
I highly recommend going to the next one.
Hopefully in front next year of this year in September.
But one of the things that truly struck me is that this is not.
This is a properly heterogeneous ecosystem.
You've got, obviously, the native rust stack.
Matrix rust SDK that is powering the element stack.
But now you've got a totally separate stack without any lines of code overlap at all.
Over then I guess the crypto and the form of flutter.
It requires pot and multi-platform of tricks.
Like wise go, which I think.
I'll be using go, oh yeah.
Yeah, too.
So there's no code overlap at all.
I see Brad say maybe.
Yeah.
And then react native.
So this is a new one coming from, you know,
made an fulfillment.
You've taken rust SDK and put a really good react native binding over the top.
I was playing it with it the other day.
It's literally about 10 lines of react native to get your matrix stuff up and running.
There's plus times like matrix client from echo and many, many more.
So when people say matrix is controlled by element and it is not a tree ecosystem,
I say bullshit.
Look at this list of folks who have implemented
entire separate stacks independently.
And the talks were amazing.
Not quite as good as fostering, but still amazing.
Around about 50 years and you can see all the thumbnails there.
I'm relatively small.
How many people were there by the way?
Okay.
So you should all come next to you.
We'll be great.
And some of the highlights we heard from TI Messenger in Germany,
which is running our matrix for all of healthcare.
We heard from Open Desk and the Zendes folks I mentioned earlier,
who are using us as the sort of chat sub system for this team's killer initiative.
You've got E post in Switzerland.
No, this is really exciting where they are pivoting the Swiss postal service from snail mail to Matrix.
Obviously.
Why wouldn't you?
And that may sound crazy, but it's literally what they're up to.
Going and deploying matrix and servers on premise for big corporate customers,
providing a SaaS hosting to themselves,
and then building a great big super app on top,
where all of the businesses have their own identity is a bit like,
we chat or something like that,
but also communicating out to the wider network.
You've got chat in France.
Did you lead to the great talk?
Yeah, it must be the biggest public sector deployment with about 300,000 monthly active users,
millions of messages sent to the moment for each ministry,
getting its own home server.
The stance for this, by the way, a public starts to incubate,
to beat it up to FRL or something.
If you want to go and look at their database,
dashboard and see how many people are logged in right now.
No, for really interesting one was NATO,
using a fork of element called nice for low-side communication
to replace what's happening signal.
So, that's where things are today, what comes next.
Well, one of the big initiatives, which I don't have time to talk about,
is state res V3.
This is an overhaul of state resolution that we're in relatively late stages doing.
This involves TARDIS, which stands for time-agnostic room-dagon inspection service,
which lets you visualize precisely, I'm glad somebody likes my joke.
This is one of my projects with civilisation,
so you can see what's happening in your rooms and debug them.
And then an ounce today, in about half an hour,
will be chaos, actually one hour.
Chaos is a new tool, which is basically a chaos monkey,
petition testing tool for home servers.
It causes networks, breaks network,
in a deterministic fashion, and then checks,
where things converge or not.
You can see why this might be useful when debugging
state res issues.
And you can see this, and you can see us talk at two in the devrim.
MLS, if I had another three hours, I would talk about MLS and great detail.
Lots of work on the ITF and to end encrypted and standard over the years.
The main one on our side, and the call team,
has been decentralized MLS, but it's a bit exotic,
it deviates from how RFC MLS is meant to work.
We now have two MSEs out there, one from Travis and myself,
one from BWY, proposing slightly different ways,
which you could add MLS to matrix.
We also have things like linearized matrix,
and Mimi, which is pretty similar.
Progress on MLS is frankly blocked on funding right now.
It is a very active topic of research.
Also, post-content, last fall student,
he teased and pulled out some PQXDH implementation
for for those maps.
And we assume that somebody would leap out to the audience
and say, oh my god, post-content matrix, I'll fund that.
And they didn't.
So here we are.
Yeah, later, and absolutely nothing has happened on it.
So if anybody wants post-content matrix,
please can you put some money behind the bar.
Likewise, MLS is experimenting with PQS,
as well, so we might get PQ3 with MLS,
maybe, but again, for progress, blocks on funding.
Then, Rust SDK has been evolving first.
Loads of fun stuff.
I'll talk about probably in the states of the union in five minutes.
But big stuff is offline support,
persistent event cashes, threads coming pretty soon.
Space is coming a bit later,
also we're seeing these additional bindings I mentioned.
We're considering there may be a world
without matrix JSSDK,
with Wazon bindings on the horizon,
thanks to Mozilla,
and filament,
who are implementing Uniafify,
or Unify support for Wazon,
so that we can take the existing Rust SDK bindings,
the support iOS and Android,
and just target them for the web.
Very quick, final demo.
So I'm not going to be able to show you on MLS laptop,
which sucks,
but come to the matrix every human CT mode,
because there's actually his project,
where his taken dioxys,
as a quick hack,
to take Rust SDK and put it in a browser,
and I got on the skin that looked like element,
and it would have been a really cool demo
to see element X web,
as a possible approach using dioxys.
Lots of mainstream features,
messing,
both on the client,
and the server,
lots of trust and safety work to be done.
We are expanding the team there,
and making some progress.
And then finally,
perhaps matrix 3.0 in future.
We don't know what this will be.
It could be all about CNS.
It could be MLS.
It could be converging with Mimi.
It could be peer matrix.
Place your books.
But the foundation is key to this.
The foundation is the future of matrix,
in terms of protecting it from the commercial
of the institutions of vendors like element,
or anyone else.
And the next 10 years of matrix
will be nurtured by the foundation,
if it has funding.
Right now,
we have a bunch of funding members.
We'd very much appreciate them.
Thank you for putting money behind the bar
to keep the foundation alive.
We need more.
We elected the governing board in May.
There are now 24 people,
I think,
looking after the overall direction of the foundation.
If you're not a member already,
or even better bully your employer to join,
if they like matrix and use matrix.
I'm looking at you,
big tech companies,
use matrix,
perhaps a bank communication,
but I'm members of the foundation.
Please.
Then governing board,
24 people,
11 orgs,
come,
listen to Greg in the dev room,
say what's going on there.
And we need help.
Please,
support matrix,
commercially,
probably from upstream vendor.
Doesn't have to be element.
Can be any upstream vendor,
build on matrix,
follow us on,
ask it on,
please go and spread the word.
Thank you very much.
Probably don't have time for questions.
Come to the dev room if you want to ask questions.