Claudflare?
Fraudfare
Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
161–170 of 231 posts
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#162So the original post had this added to the top: > This post was updated at 11:15 a.m. Pacific time to clarify that the use case described here is a proof of concept. Some sections have been updated for clarity. But then the bottom still says: > Our team is using Matrix on Workers, handling real encrypted communications. It is fast, it is cheap, and it is arguably one of the most secure ways to deploy a homeserver tod…
I guess they're dogfooding something that's wildly insecure and incomplete internally. Kind of surprising that's allowed on CloudFlare's internal network if true, but I guess shadow-IT is everywhere.
[deleted]
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#163So the original post had this added to the top: > This post was updated at 11:15 a.m. Pacific time to clarify that the use case described here is a proof of concept. Some sections have been updated for clarity. But then the bottom still says: > Our team is using Matrix on Workers, handling real encrypted communications. It is fast, it is cheap, and it is arguably one of the most secure ways to deploy a homeserver tod…
I don't believe "Our team is using Matrix on Workers." The repo is in someone's personal Github and a pretty incomplete and insecure implementation.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#164That the original post to HN linked in the blog was done on a throwaway kind of implies a level of awareness (on the part of the dev) that the code/claims were rubbish :) https://news.ycombinator.com/item?id=46780837
[deleted]
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#165Earlier quoted context omitted.
Btw, after I wrote that initial article ("Cursor's latest "browser experiment" implied success without evidence"), I gave it my own try to write a browser from scratch with just one agent, using no 3rd party crates, only commonly available system libraries, and just made a Show HN about it: https://news.ycombinator.com/item?id=46779522 The end result: Me and one agent (codex) managed to build something more or less t…
Would be interested to know what people think of the locking implementation for the net worker pool. I’m no expert but it seems like a strange choice to me - using a mutex around an MPSC receiver, so whoever locks first gets to block until they get a message. Is that not introducing unnecessary contention? It wouldn’t be that hard to just retain a sender for each worker and just round robin them
I suspect this is just an LLM hallucinating generic thread-safety boilerplate. In an async serverless runtime like Workers this pattern creates blocking risks and doesn't actually solve the distributed consistency problem.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#166I hope this isn't in bad taste, but I applied for the editor-in-chief position at Cloudflare back in August when they had it open. I'm still very interested in the role. If anyone at cf is reading this, my email is bro @ website in bio.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#167My charitable read on this is that an individual vibe-coded both the post and repository and was able to publish to the Cloudflare blog without it actually being reviewed or vetted. They also are not an engineer and when the agent hallucinated “I have built and tested this and it is production grade,” they took it at face value. You can tell since the code is in a public repository and not Cloudflare’s, which IMO is…
I agree, but it's probably not just about being "able to" do it, but about what the incentives and pressures are in that organization.
Cloudflare apparently considers blog posts to be a key deliverable for many roles. Not just marketing or devrel but engineering too. That sets up a lot of incentives for slop. And then all you need for a disaster is a high trust environment with insufficient controls, which they probably have since the process had worked for a decade without an insufficiently reviewed article blowing up in their face.
Going forward there will be just a little bit less trust, more controls, and more friction that will make it harder to get a post out in a timely manner. It's just the way all organizations evolve. You can see from the scar tissue where problems existed in the past.
What I can't believe is that they haven't retracted the whole post by now, but are allowing the author to make an even bigger mess trying to fix the initial problems.
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#168My charitable read on this is that an individual vibe-coded both the post and repository and was able to publish to the Cloudflare blog without it actually being reviewed or vetted. They also are not an engineer and when the agent hallucinated “I have built and tested this and it is production grade,” they took it at face value. You can tell since the code is in a public repository and not Cloudflare’s, which IMO is…
This person works for Cloudflare. What else are they "vibe coding?" How long until Cloudflare shuts off half the internet due to a "mistake" again? How much longer are we going to accept that these are mistakes?
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#169Earlier quoted context omitted.
They aren't really a multi-billion dollar corporation. A lot of it is them just pumping up their valuation. Stuff like this proves that in a lot of ways.
They are running > 300 DC's...
They have equipment in > 300 locations. How much per location? More than a rack cabinet?
Re: Cloudflare claimed they implemented Matrix on Cloudflare workers. They didn't
#170My charitable read on this is that an individual vibe-coded both the post and repository and was able to publish to the Cloudflare blog without it actually being reviewed or vetted. They also are not an engineer and when the agent hallucinated “I have built and tested this and it is production grade,” they took it at face value. You can tell since the code is in a public repository and not Cloudflare’s, which IMO is…
This person works for Cloudflare. What else are they "vibe coding?" How long until Cloudflare shuts off half the internet due to a "mistake" again? How much longer are we going to accept that these are mistakes?
> How much longer are we going to accept that these are mistakes?
How much longer are shareholders** going to accept that these are mistakes?