Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers. They didn't, their post and README is AI generated and the code doesn't do any of the core parts of matrix that make it secure and interoperable. Instead it's littered with 'TODO: Check authorisation' and similar

https://blog.cloudflare.com/serverless-matrix-homeserver-workers/

Let me just pick a few examples from the code, because this is so bad

This is a core part of the protocol, that's not exactly simple (https://spec.matrix.org/v1.17/server-server-api/#authorization-rules)

They just have TODO comments, and happily accept anything, even if it's blatantly forged

Rather than implementing the critical state resolution algorithm that's the core of Matrix, they just directly insert the latest state into the database. That'll instantly lead to diverging views of the room and incompatibility with every other implementation - and it's also a massive security hole.

Oh and to top things off, they make trivially false claims in their post. Tuwunel and its predecessors do not and have never used Postgres or Redis.

Honestly this is almost insulting to me, as someone who has spent a nontrivial amount of effort developing a Matrix homeserver, with how low effort it is. And what’s the point? Marketing? I’m not gonna be trusting anything Cloudflare after this.

The pricing comparisons are stupid, by the way, too - a bunch of us in the matrix chatrooms got out how many HTTP requests per day we were serving and the per-request cost of Workers would be more expensive than dedicated VPSs - not even counting CPU time or storage costs!

For those of you that don't know, I develop https://continuwuity.org - a Rust based Matrix homeserver that actually works, and that you can run on a Raspberry Pi, rather than someone else's centralized cloud infrastructure

I'm also giving a talk about some of the actual work that goes into building this software in a few days at FOSDEM, if you want to learn more:

https://tech.lgbt/@JadedBlueEyes/115956965835059690

Oh look, they’re trying to cover up what they did too

https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463

Archive link for posterity:

https://web.archive.org/web/*/https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463

@JadedBlueEyes it’s wildebeest (cloudflare fedi software that leaked dms to the public) all over again

@JadedBlueEyes eeeew yuck that’s so fucking embarrassing. not like those feds had any reputation to worry about whatsoever, but still

@JadedBlueEyes

I’m not gonna be trusting anything Cloudflare after this.

as if you should’ve been doing this in the first place

@JadedBlueEyes And even if they did, centralize a decentralised system on cloudflare what a good idea

@lexinova @JadedBlueEyes I think it is fundamentally interesting to try and port software to run on cloudflare workers. Like, it’s a stack with very different assumptions and tradeoffs. Having alternatives is always nice. I don’t think it’s bad for this to exist. I don’t see how that leads to centralization.

But the execution is bad. Lmao.

@sodiboo @JadedBlueEyes because Cloudflare own half of internet ?

if it's not centralizing even more ... what is this ?

@tauon @JadedBlueEyes true but this is the giant rock excavator hitting a whole new substrate of rock bottom

@JadedBlueEyes slopflare