I'm stoked to see the webhooks get an overhaul. I was just about to use them for a project, and this'll be a great help. I wish they'd do similarly for the ser

I'm stoked to see the webhooks get an overhaul. I was just about to use them for a project, and this'll be a great help. I wish they'd do similarly for the services. Currently, editing multiple services across repos is a bit of a pain, due to the length of the list and how it jumps you to the top on any interactions. (Originally, I thought this announcement meant they'd revamped that as well) Out of curiosity, is there a generally-accepted best practice for rate-limiting / authenticating webhook pushes? I'm planning to run a daemon that listens for them, and while the effect of somebody finding the URL and hammering it isn't likely to be catastrophic, I'd still like to rate limit it if I can. Alternately, are GitHub's webhook-sending IPs static enough to put in an IP set and add to my firewall?