we should in the future have an API endpoint where we provide a list of recording_mbids and get back that list of recording_mbids with last (or never) listened at.
the thing is, all other patches will need this too.
well, not so much new jams, but artists radio does.
lucifer
i think TS can support that fast once we resize the chunks.
scan the 8-10 latest chunks only.
mayhem
it would be nice to not have to make yet another dataset.
lucifer
that gives us whether the track was listened to in the last 3 months
mayhem
that should be sufficient.
I forget, we still had a rewrite of the listens table planned, but that hasn't happened yet, right?
lucifer
i'll add that endpoint and once we resize the chunks i hope it to become faster.
mayhem
resizing chunks should be done at the same time?
lucifer
not necessarily,
but we planned to do it at the same time.
the rewrite is pending on figuring out how to display the timezone data to users.
mayhem
ok, sounds good. that will improve the run time of the upcoming patches. they keep getting more and more intensive. :(
how to display it or how to store it?
lucifer
figure out how to display so that we can work out what exactly to store.
Ah, I see, that's why I was asking if it was a background :) It won't work that way then. Let me take a look
mayhem
oh, sorry, I didn't quite understand that question correctly.
monkey
No worries.
CSS, amirite?
mayhem
yerp
antlarr has quit
antlarr joined the channel
monkey
OK, maybe not the absolute most bare-bones approach, but definitely the easiest way to do this is to add the `flex-center` class to the parent element.
This is one of our custom classes that makes the parent a flex container and centers the children.
monkey: ^^ I think changing the breaks is the only thing that is left. any tips on how to do that?
olbld has quit
olbld joined the channel
atj
this is bootstrap right?
monkey
Yes, media queries. But this means departing from bootstrap scaffolding
I'm trying out some of the existing BS breakpoints to see if they could match those dimensions close enough
mayhem
ok
atj
can you not use bootstrap breakpoints?
ah
monkey
Other wise it will mean removing the BS scaffolding classes, and writing custom CSS to manage the element width as percentages depending on screen size. Not toooo ticky.
mayhem
is that worth it? for this page?
monkey
It's only a few lines of CSS in the end
mayhem
ok
reosarevok
zas: oops, I just noticed you replied only to the account admins account with that French email
Because for some reason reply-to is kept when they answer me?
I'll forward it to them
monkey
We're too limited by BS breakpoints I think mayhem.
Instead of using BS scaffolding classes (col-xx-xx), you'll need to give the card container element a class name to target.
Then here's what the css would look like for those elements:
mmm, something not quite right with one of the card images, let me dig
trolley has quit
trolley joined the channel
trolley has quit
trolley joined the channel
trolley has quit
Right, the cover art collage image when resized is smaller than the 171px we need to fill the card image container, which results in this weird layout. one fix is to change the .explore-card-img-clip `max-height` css property to `height` instead, which will fix the layout (but not the image ration as you can see in this screenshot:)
It looks like the linting of your less files is what's failing, unless I'm missing something. Try running `npm run lint:less` if you have node installed locally, or `./test.sh fe -f` for docker version