Well, RIP nginx, long live freenginx: http://freenginx.org/pipermail/nginx/2024-February/000000.html
@janl sad to see this. However I am torn who I would trust more these days - large enterprise developing great open source product (even if in non-external-contributor-friendly-way) or a Russia person physically located in Russia 😬
@janl Most burning question: How to pronounce it? https://ruhr.social/@guerda/111936145836342610
@janl Oh dear. "The new owners are fiddling with the security dials" is a worrisome thing to read. I wish the new project lots of luck.
@janl pardon me, but if im reading this right, maxim is just being an asshole
a security bug in an experimental module is pushed to prod
f5 order to assign a cve and make it public because despite the fact the module is off by default some people already have it enabled in prod
maxim disagreed because it's experimental and said it should've been pushed as just as a minor bugfix
he leaves his volunteer position and forks nginx into freenginx, saying f5 are trying to run the project against the devs' wishes
@janl whoa, damn. I use Nginx heavily in my homelab/self hosting setup, will need to look at migrating now.
@janl Oh hallefuckingluiah. So freaking sick of the corporate leeches hanging onto nginx, ever since lighttpd crashed and burned and there was no other good option. Let me cache my images dammit!
I haven't looked at lighttpd since HTTP/2 started getting bandied about everywhere, and that's been quite a few years. Looks like they did implement it though in 2020.
@janl indeed, but it felt better that there was an international company behind them for checks and balances