I had to disable multilingual plugin on discourse, it causes multiple issues, and caused a major failure after discourse upgrade. It doesn't seem to be well maintained.
Maxr1998 has quit
Maxr1998 joined the channel
julian45[m] joined the channel
julian45[m]
bitmap: sending you an invite to the authentik instance shortly; you should be prompted to set up a password and MFA (ideally in near future we can get back to a passwordless-first approach like kanidm), and then you should be able to log into google workspace after setup is complete (tested with a test user)
The existing code, scans the entire listens table in passes with increasing window sizes. In the current solution, the passes are limited to 3. so (1 + 3 + 9 = 13 months).
however, i am thinking about api use cases where the user can specify just the min or max ts.
if the search terminates after 13 months from the min ts with no results but there are results in the following yet unscanned range, it can be misleading.
mayhem[m]
Understood
lucifer[m]
it wouldn't happen in the existing code, because we do passes until the entire table is scanned.
mayhem[m]
Which is not ideal either...
lucifer[m]
so i am wondering if we should have two modes of search, one for our frontend which can query the api again when one api call couldn't find results.
but the default api to always search for the entire table.
this is for maintaining existing behavior. but this can always be very resource consuming and an easy way to get ddos-ed.
mayhem[m]
That
lucifer[m]
so maybe we should say that if you specify min or max ts then just 1 year ahead or before is searched.
and if you specify both, the both cannot be more than 1 year apart.
mayhem[m]
If we had a field in the DB that says: the previous listen to this one is x seconds ago.
If we had such a field, this would be a whole lot easier
But adding that field is basically making a linked list in the DB
lucifer[m]
yeah that could work but it would need to be updated on every insert and delete.
mayhem[m]
What if we had a script that inserts these values for when there are large gaps?
It just runs in the background. If you read a page and it ends with such a hint, you know where to seek to.
If you find no hint go to the previous page
lucifer[m]
hmm i see.
i'll think more about the implementation.
whether we want to keep in the listen table or a seperate one.
because we could also maintain a list of months or years for which a user has listens in the listen metadata table.
_BrainzGit
[musicbrainz-server] 14mwiencek merged pull request #3520 (03schema-change-2025-q2…mbs-13964): MBS-13964: Some recordings are missing a first release date https://github.com/metabrainz/musicbrainz-serve...
