@feditips

Unfortunately it is not that simple.

The server could do it based upon age of when the user last saw the boost. The problem is that this adds more complexity to the server to manage. And, there is no guarantee that the user actually saw (eyeball read) the boost in the first place.

I think this is best managed client-side, and that requires the client to track which post was boosted, and then would likely not be over 24 hours before it is aged out of a cache. Though, if you have the ram, you could make the expiry time longer.

Needs to be client side, but continue to waste bandwidth as happens now.

It is important that the original post creation timestamp is NOT a factor.