In Ferron, because of strong memory safety guarantees provided by Rust, you won't be able to run arbitrary code via HTTP/2, or anything similar in this class on vulnerabilities π
If you run NGINX below 1.30.7 with HTTP/2 on, anyone can run code on your server.
Can't upgrade immediately, do this:
http2 off;
nginx -t && systemctl reload nginx
Zero downtime.
Then upgrade.
Also, we want to build a web server where debugging is easier and issues could be resolved faster.
AI slop is opposite, it makes debugging harder (looks good on surface, but fails subtly), operators get tired reading AI slop documentation and code, and everything crumbles.
I'm now spending time removing AI slop from zincio, zincio-http and Ferron codebases...
Already did the first two, will do it for Ferron (although it would be more complex, with E2E tests, docs and quite some Rust crates as components).
We're flooded with too much AI slop software. This is unacceptable.
What if someone deploys AI slop server and their infrastructure crumbles and website stops working? Customers will go angry!
And the next-token predictor would workaround, but it would break unrelated stuff...
@tarasshyn@mddanishyusuf The first one (Plausible CE) is what I'm using, while the third one (Umami) already supports revenue tracking
https://t.co/1GSydHBfw9