Whoops! post-receive is Git specific. Also "webhooks"

[Jeff Lindsay]

So when I started looking into GitHub's modern web hook system, they
would call the endpoint for their main hook a "post-receive URL" and I
figured this was their way of describing the handler endpoint. Right?
A URL that receives a post?

The other day, after actually looking into Git's hook system, I
realized that's the name of the event for when the repository receives
a push update. Silly me! In my attempt to integrate emergent community
lexicon, I started referring to these endpoints in general as post-
receive URLs.

I guess the next issue is whether I will truly stick to that attitude
and start calling them "webhooks" as so many people are. I've always
been one to jump ahead and merge words like website (I hated when that
was considered misspelled) and webservice (still not very popular),
but I've been resistant here.

I suppose as a "movement" it makes more sense as webhooks, but the
original idea was that at the core it's about "hooks"... just, on the
web. Since I consider hooks to be the complement to API's (in this
case web API's), I figured someday when this concept is popular, we'd
just call them hooks, like we say API's.

Maybe this is a silly meta conversation at this point.

-jeff