Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers.
-
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/
@JadedBlueEyes The first paragraph smelled like total BS.
-
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.
@JadedBlueEyes@tech.lgbt Oh yeah. Wait what the fuck. Even i know this and I've never touched the codebase. It's
rocksdband there was at one point SQLite, right? -
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.
I’m not gonna be trusting anything Cloudflare after this.
as if you should've been doing this in the first place -
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/
@JadedBlueEyes@tech.lgbt reminder that half of the internet relies on these people. I'm scared for the future
-
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.
@JadedBlueEyes
It has always been RocksDB, right?
Oh, Conduit also supports SQLite iirc -
Holy crap. I would not expect this from an industry giant (Though I guess I should.)
That certainly shatters my trust in cloudflare a bit. #devops #programming #networking
@silo_bear @JadedBlueEyes Seriously.
Before this: "Well, CloudFlare at least has smart people working there I guess."
After this: "CloudFlare are sloperators."
-
@JadedBlueEyes
It has always been RocksDB, right?
Oh, Conduit also supports SQLite iirc@darkcat09 Conduit started with Sled, and then moved to a KV abstraction that let them add RocksDB and SQLite support. Conduwuit then removed everything but RocksDB, which is what Tuwunel and Conduwuit are forked from
-
Oh look, they’re trying to cover up what they did too
https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463
Archive link for posterity:
@JadedBlueEyes The comments under this commit make it at least a bit funnier
-
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.
@JadedBlueEyes
I don't think anyone should've ever trusted cloudflare before
-
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/
@JadedBlueEyes So, what you're saying, is, this is "post-quantum" in the sense that its security properties will not be significantly degraded by the existence of working quantum computers.
-
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/
@JadedBlueEyes I remember how they did same thing for activitypub, and it looked (and worked lol) like a very, very cheap & bad mastodon clone
To scale: it showed DMs in public timelines
-
Oh look, they’re trying to cover up what they did too
https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463
Archive link for posterity:
@JadedBlueEyes Oh yes, great fix. I also always resolve TODO comments by just deleting them. It'll be fine.
-
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/
@JadedBlueEyes This is almost a minor criticism in comparison to all the other crap, but I am so sick of companies calling things 'serverless' when what they really mean is "servers, but only ours and they're really opaquely billed and impossible to replace with someone else's servers so you're stuck with us, and also they're managed in a totally custom way so none of your normal sysadmin skills are portable to it but you still have to learn how to manage it"
-
@JadedBlueEyes Oh yes, great fix. I also always resolve TODO comments by just deleting them. It'll be fine.
@outsidecontext Same. It’s the fastest way to resolve it, and that means it’s the best, right?
-
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/
@JadedBlueEyes this is the best PR https://github.com/nkuntz1934/matrix-workers/pull/1/changes
-
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/
@JadedBlueEyes@tech.lgbt worst game of spot the difference i have ever played
-
Oh look, they’re trying to cover up what they did too
https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463
Archive link for posterity:
@JadedBlueEyes This takes it from "lazy and disappointing" to "actively malicious". One quick apology blogpost would fix this, but they're doubling down, aren't they?
-
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/
@JadedBlueEyes oh, what a disappointment. I don't understand that much so I trusted their post
-
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/
@JadedBlueEyes @dcousineau Nothing like :checks notes: three THOUSAND lines BS in one file: https://github.com/nkuntz1934/matrix-workers/blob/main/src/admin/dashboard.ts and it's not even good code.
-
Oh look, they’re trying to cover up what they did too
https://github.com/nkuntz1934/matrix-workers/commit/2d3969dd5e795caa3641d0e237e2b52ca0502463
Archive link for posterity:
@JadedBlueEyes I recently learned that GitHub allows one to view the activity on a repo, and you can limit it to show force pushes only, which in turn allows you to view the diff between the two states too, even if they span multiple commits.
It's fun to see what kind of things some companies try to hide. (edit: like the original history, which has some fun commits in there!)
