we have been getting slammed by bots/AI scrapers, i'm afraid
2025-10-20 29348, 2025
julian45[m]
zas has been working on anti bot measures for the better part of at least today
2025-10-20 29338, 2025
jesus2099
Ach. AI sucks in all ways.
2025-10-20 29354, 2025
MonkeyPython
jesus2099: hi!
2025-10-20 29306, 2025
MonkeyPython
and yea, trute!
2025-10-20 29306, 2025
monkey[m] joined the channel
2025-10-20 29306, 2025
monkey[m]
lucifer: I think there might be issues introduced with the listens caching (only thing I can think of): I can see listens I am listening to currently on the LB prod website, but not on the beta website (which I updated today, contains the caching PR).
2025-10-20 29307, 2025
monkey[m]
I get that we are supposed to cache responses, but I think it breaks the main functionality of the website at the moment. I'm worried about one of us deploying a new prod version of LB with this caching
2025-10-20 29321, 2025
jesus2099 has quit
2025-10-20 29328, 2025
jesus2099 joined the channel
2025-10-20 29317, 2025
lucifer[m] joined the channel
2025-10-20 29318, 2025
lucifer[m]
[@monkey:chatbrainz.org](https://matrix.to/#/@monkey:chatbrainz.org) the timescale writer containers need to be updated with the caching PR as well
2025-10-20 29327, 2025
lucifer[m]
If those are updated, and it is still broken I can revert the changes.
2025-10-20 29357, 2025
rayyan_seliya[m] joined the channel
2025-10-20 29358, 2025
rayyan_seliya[m]
<lucifer[m]> "[@monkey:chatbrainz.org](https:/..." <- Hi lucifer: could the IA. Search issue related to the recent caching changes ? I saw u mentioned that listens caching or might have broken the functionality and that the timescale writer container needs an update may be that is affecting the IA search ? Just guessing !
