Any plans to introduce client interceptors?

The Twirp canonical implementation supports both [server and client interceptors](https://twitchtv.github.io/twirp/docs/hooks.html). This allows us to do similar things for both clients and servers, such as emit specific metrics based on type of request. In the Ruby stack, this facility exists only for the server side. Are there any plans to introduce client interceptors as well?

As a side note, what twirp-ruby calls service hook is actually server interceptor in the canonical lingo. Any reason for this naming choice?

Start by reading the linked Twirp hooks documentation and inspecting twirp-ruby’s existing server-side service hook implementation. The issue names no files or tests, so the scope and API for client interceptors would need to be established first; completion would require an agreed client-interceptor facility and clarification of the service-hook naming.

Written by the indexing model from the issue text.