Not sure how to avoid the binary incompatibility since I needed to change the WebSocketContext api. Open to suggestions or which branch I should PR to for binary incompatible changes?

Yeah, this is a tricky one :) the good news is that it is possible to make the change binary-compatibly.

You'll have to make WebSocketContext into an ordinary class and manually restore all the missing case class methods (if you are good at reading MiMa issues, they will guide you with which methods to add). Also because case classes are encoded differently on Scala 2/3 it will necessitate splitting sources.

We recently did this in #5758 and 566fb53 although that was complicated by type erasure problems as well.

Binary-breaking changes can go to main, but it won't help you if you are expecting a stable release anytime soon.

So I looked into this a bit more, and I'm a little confused about why we need to make any changes to WebSocketContext at all actually.

1. The PR that added the filterPingPongs API also implemented support for this feature in Blaze. So it's possible to implement this without modification to WebSocketContext.
   Added new WS API which allows receiving Ping messages from the client #3136
2. In fact, Blaze's implementation doesn't appear to use filterPingPongs at all. AFAICT the parameter is used only in WebSocketBuilder2:
   

   http4s/server/shared/src/main/scala/org/http4s/server/websocket/WebSocketBuilder2.scala

   Lines 162 to 166 in 6e13209

   	val finalReceive: Pipe[F, WebSocketFrame, Unit] =
   	if (filterPingPongs)
   	_.filterNot(isPingPong).through(receive)
   	else
   	receive

3. The PR adding this feature made the following change to Blaze:

- case Ping(d) =>
+ case p @ Ping(d) =>
  //Reply to ping frame immediately
- writeFrame(Pong(d), trampoline) >> handleRead()
+ writeFrame(Pong(d), trampoline) >> F.pure(p)

So I think your PR is on the right track ...

I'm inclined to approve. Is there an easy test we can add to lock-in this behavior?

I think I should be able to whip one up. I'll get one added this week. 👍🏻

@CharlesAHunt Following up. Just don't want to lose track of this one.