I noticed something really odd going on when fetching listens that have been inserted a long time after they got listened to.

I started slowly but surely adding listens on the 01 of june 2023 for recordings I knew I listened to in the past, but not sure when. This has for consequence that the listened_at and the inserted_at date being widely different:

{{

{"inserted_at": 1714719745,"listened_at": 1688194938}

}}

 

But one thing I noticed, is the huge response time on the web UI, and api requests just straight up being timed out. Here's a link to demonstrate

https://listenbrainz.org/user/RustyNova/?max_ts=1702569461

https://api.listenbrainz.org/1/user/rustynova/listens?max_ts=1702569461

 

It is probably not good for the postgre server either to go fetch those listens, so would be great to have it fixed