mayhem: (replying to something from way back) - that is clearly a keyboard
jasje: akshaaatt: icon changes, exiting! Hopefully sticking to the ones we discussed :P
Also, remember that in the style guide we avoid using 100% black, we have a different ‘black’ colour
reosarevok: when you’re online can you check the report I sent? Would be good to have it looked at soon, and have the community managers input before re-allowing editing rights (let me know if you can’t)
akshaaatt
Hi prabalsingh! Thanks a lot for your contributions :) We would love any help we can get for our projects. Feel free to pick up bugs and submit a PR for them. Let me know if you need some help understanding anything or fixing any issues.
akshaaatt: we should probably use viewpager for this'
akshaaatt
Yeah. Infinite loading will be the key
You are already making it for feed, right jasje?
jasje
yes
akshaaatt
Then you would be the right person to update it for profile as well
jasje
but i need to edit the endpoints themselves first
akshaaatt: or
akshaaatt
Not the endpoints but the params which go in
jasje
iss complicated
bitmap
zas: is 15 UTC ok for the database downtime?
akshaaatt
It's not. I have the code for things if you want me to work on it.
jasje
akshaaatt: but anyways i see you removed preloader from listens screen
akshaaatt
Yes that was causing a crash
jasje
akshaaatt: im talking about feed
akshaaatt
There seems be to be some fault from glide
jasje
akshaaatt: its kinda restrictive but works good when it does
coil is so shit
akshaaatt: since we have removed the preloader
lucifer
akshaaatt: load the listens in smaller batches. `https://api.listenbrainz.org/1/user/prabalsingh24/listens` will give 25 listens at max by default. look at the listened_at value of the last listen in that list and then next time query with that as `max_ts`, `https://api.listenbrainz.org/1/user/prabalsingh24/listens?max_ts=1685294816` so on.
jasje
might as well add the fallback cover art innit?
bitmap
zas: anyway I prepared a google doc & invited you & others
avane has quit
SothoTalKer has quit
KassOtsimine has quit
vscode has quit
jasje has quit
Freso has quit
atj has quit
bitmap has quit
vscode joined the channel
KassOtsimine joined the channel
jasje joined the channel
theraspberry has quit
Freso joined the channel
atj joined the channel
SothoTalKer joined the channel
avane joined the channel
bitmap joined the channel
yvanzo
O’Moin
bitmap: ok for me
tux0r has quit
jasje
monkey: up?
lucifer: ?
just added the test to the new endpoint
also wanted to know
what max limit do you suggest for getting follow listens?
current is 2
per user
and 10 overall
akshaaatt
Cool lucifer. We'll do that soon. Just wanted to confirm that the api had no issues
mayhem
moooin!
aerozol: key-board. ha, love it!
aerozol
Moin!
mayhem
after this weekend its going to take a bit to readjust to work -- spring in BCN is really lovely with loads of stuff going on.
Hold on, for "processing replication changes" actually.
aerozol
jasje: It’s limited in the other feed, sure
reosarevok
yvanzo: oh, ok :)
aerozol
If it’s limited we might need to reconsider the UI/UX jasje, to indicate that people aren’t getting all the listens of their follows in chronological order (which I would assume)
jasje
aerozol: current feed shows only 2 listens per user and total 10 listen events only
aerozol
jasje: Yup, no point in making the same feed in another tab though, right!
jasje
yup i was thing 4-5 per user and 25 as the limit
was thinking**
the frontend can then fetch next 25 by using min_ts of present list
autoAddReplicas is dropped from Solr 9 anyway, not going to use it.
jasje
monkey: about the listens section in feed
monkey
Just reading the backlog now. I agree with aerozol, I think for this feature of your friends' listens, maybe we shouldn't limit the number of listens, and instead just show listens chronologically
We limited it originally in the feed so that it wouldn't take over other feed events, but I'm not sure that's what we want if we separate the feature
jasje
alright
if you still wanted to limit somehow
so that a single user cannot just take up the whole listens section because their listens have the timestamp priority
monkey
Sorry, i'm not sure of what you're asking
I understand we could have cases where one user's listens takes most or all of the page, but I think that's more logical (to me at least) than arbitrary limits. As aerozol said the UI would need to be different in ways I don't really know yet if we wanted to do that
It makes pagination more complicated, and probably not reproducible
as in moving form one page to another and then back, you might not have the same page
yvanzo
zas: DELETEREPLICA gave a more useful error message: the replica identifier is "core_nodeX" rather than core name "annotation_shard1_replicaY"