It's kinda like a private SaaS platform. I just run it for me and a couple of friends right now and just hosting a ton of little fun side projects on it.
e.g. https://tim-efa.valar.app which brings Munich's public transport schedule to your terminal (try it with curl, looks way better)
It supports all kinds of things like bring-your-own-domain, e.g. I run my portfolio page https://espe.tech on top of it. It is partly open-source (actually only the CLI for now) but I plan to fully open-source it in the future after cleaning up the code a bit and improving testing and stuff :)
As far as I understood it: the premise of added security is based on the fact that the other WebRTC peers only see Cloudflare's IP instead of your own. Also nobody knows who you are exactly talking to except Cloudflare. I would still expect that the media channels itself still remain encrypted when even when multiplexed by Cloudflare's network.
edit, yes it's encrypted:
> Finally, all video and audio traffic that passes through Cloudflare Calls is encrypted by default. Calls leverages existing Cloudflare products including Argo to route the video and audio content in a secure and efficient manner.
Cloudflare provides an immense value for small sites. Doing DDoS protection with specialized firewall hardware was one of the most expensive things you could do, so it wasn't really affordable for lots of people. They win by solving a problem. I believe that the issue of Cloudflare as a man-in-the-middle is a smaller issue for people running websites than the damage done by potential attacks.
Great to see new features being implemented. I'm using DuckDB for a thesis project and integrating it into my own Python CLI/web tool has been super easy -- I especially love the direct integration with DataFrames, it makes things really seamless.
> Litestream has a new home at Fly.io, but it is and always will be an open-source project. My plan for the next several years is to keep making it more useful, no matter where your application runs, and see just how far we can take the SQLite model of how databases can work.
As far as I understood it, Fly.io hired the person working on Litestream and pays them to keep working on Litestream.
I guess in the long term the product will at least pay for itself, in the short term it will just be a marketing campaign and gives people a good reason to switch from their Amazon stack in case they don't depend on things like EC2-S3 transfers. When comparing to Backblaze B2 [1], Cloudflare's storage cost is 3x but you don't pay for egress as a tradeoff (compared to 0.01$/GB for Backblaze).
I discovered this book today and have been reading it all afternoon. The interviews with Brad Fitzpatrick and Peter Norvig are very entertaining (and informative)!
Isn't this solved by a large scale find-and-replace for existing scripts? Sure, the changes can be inconvenient but it's not like a major API change or something. They've also been printing out warning messages since December 29th according to the issue, so I'd expect that people would have updated their pipelines by now.
TLDR: Your Let's Encrypt certificate may have an RSA private key. Go's TLS implementation is far better optimized for ECDSA keys. Switching from RSA to ECDSA saves about 95% of CPU cycles due to the better implementation.
I discovered it when looking into runtimes for my Bachelor's thesis. So far it's serving me quite well, especially after they reworked the Sentry file system abstraction (when I started file access was horribly slow). Networking works very well although they reimplemented it themselves. It also allows me to do base image layering using Overlay since I only keep binaries/source code/assets after a successful build.
Have been building a similar project in the past few months called Valar (https://valar.dev, it uses gVisor instead of Firecracker and is still in private beta), but I prioritized university studies so it took too much of my time to actually release it publicly. Great to see a similar product being released, really looking forward to test it. Best of luck to you!
It's kinda like a private SaaS platform. I just run it for me and a couple of friends right now and just hosting a ton of little fun side projects on it.
e.g. https://tim-efa.valar.app which brings Munich's public transport schedule to your terminal (try it with curl, looks way better)
It supports all kinds of things like bring-your-own-domain, e.g. I run my portfolio page https://espe.tech on top of it. It is partly open-source (actually only the CLI for now) but I plan to fully open-source it in the future after cleaning up the code a bit and improving testing and stuff :)