On Fri, Jan 23, 2026 at 10:40:13AM +0100, Willy Tarreau wrote: > > It's still popular but some websites decided unilaterally that is was > > obsolete > > without any particular reason, just because it's an old standard. But a lot > > of > > tech websites are still providing it. (phoronix, lwn, HN, etc) > > > > I do know a lot of people still using it, but there's probably less than a > > few years ago since websites are silently removing them... > > > > By the way, on the haproxy.com blog, there's a feed: > > https://www.haproxy.com/feed > > Thanks for sharing your perspectives on this, William. If you're > interested in this, we can see together how to add this to the publication > process. Last time I did this, I did it completely blindly, I don't even > know a client that consumes and validates such data, nor do I know how > people use them.
Sure, we can take a look, I don't think it would be more complicating than duplicating news.html with a template in RSS format instead of HTML. > On a side note, I had plans to try to automatically update the news.html > page with LLM-assisted summaries of the announce message, maybe it's worth > combining the two efforts. For example for the previous announce I'm getting > this, which I find pretty satisfying, though it will require some tooling > to be placed there: > > HAProxy 3.4-dev3 adds larger thread-group limits (up to 32768), runtime > warnings for slow password-hash algorithms, CLI control to publish/ > unpublish backends and use force-persist in frontends, flexible systemd > unit with conf.d support, JWE AES decryption/conversion converters, > session-aware fetch helpers, and a dump_all_vars fetcher for easy > variable export. > > Maybe it could be helpful in the RSS feeds though. > Willy That could be useful indeed! -- William Lallemand
