When a user "deletes" a listen, it is only staged for a batch deletion every hour.

If a user opens their listens page later on (before the actual deletion), the deleted listen will still be there, which is confusing.

We should implement a more robust way to hide these listens in limbo.

This probably requires an endpoint to fetch a user's deleted listens.

We could also involve the browser's local storage to store that information temporarily if need be, but not sure it will be needed.