Anybody running #haproxy on #FreeBSD?
And if so, does your instance(s) take for-fracking-ever to restart when you do a:
service haproxy restart
?
I usually end up killing the haproxy process just to make it restart faster. I haven't dug into too much because it is so easy to work around, but maybe my setup has something egregiously wrong, or there is an obvious fix?
Edit: And fixed! See replies.
Do we want to work for Google for free?
I feared this day was coming — this is the first site I see closing down, because Google has stolen their content.
The owners of this cycling inspiration site asks: What is the reason to continue creating content, when Google just steals it and serves it as AI answers to keep all the traffic to itself?
It seems our EU politicians are soundly asleep at the bike handlebar.
https://www.holland-cycling.com/blog/321-holland-cycling-com-stops-in-2026
Via @saarmuller.
@randahl @saarmuller For now, most of these LLM search engine / crawlers adhere to robots.txt
Meaning, blocking these activities of stealing traffic and content is largely solved by a well crafted robots.txt file:
You can easily setup a proxy like #haproxy to always serve a particular static robots.txt for all your domains in one go.
Additionally, with or without enterprise features, you can block all LLM traffic entirely in haproxy.
https://www.haproxy.com/blog/how-to-reliably-block-ai-crawlers-using-haproxy-enterprise