3 ms·
So 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 co
by ncruces 9mo ago
So 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 today.
Which one is it?
- philipwhiuk 9mo agoI 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 9mo ago[deleted]
- corvad 9mo agoI 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.
- ncruces 9mo agoEdited again at 11:45 to remove that as well. Now reads: > I have been experimenting with the implementation and am excited for any contributions from others interested in this kind of service. A few of the versions of the blog are available at: https://archive.ph/https://blog.cloudflare.com/serverless-matrix-homeserver-workers/ https://archive.ph/https://blog.cloudflare.com/serverless-ma...
- rsynnott 9mo ago> Our team is using Matrix on Workers, handling real encrypted communications. ... Oh, dear.