#metabrainz

<JuliaHusar[m]> "Quick question, is there a..." <- not yet. but before too long, I want to make that happen too.

<jasje[m]> "There is some refactoring that..." <- jasje: the current implementation of sockets does not include the current song progress so when we need to show the listening now from sockets should we only show the mini player with the song details or can the current implementation of sockets be changed to also include the progress too?

<GautamShorewala[> "jasje: akshaaatt i was looking..." <- As of now, we should only show the song without progress.

jasje[m]: Support for showing will cost more on the server side but that is up for debate

jasje[m]: Cc lucifer:

jasje[m]: Maybe we could send play pause events with utc timestamp but still up for debate

[listenbrainz-android] 1407jasjeet merged pull request #554 (03feat-playlists…feat-createplaylist-hemang-mishra): MOBILE-214: Create-Edit Playlist Screen implementation https://github.com/metabrainz/listenbrainz-andr...

mayhem: LB was down for a few minutes. i didn't find any hung up queries in the database so weird and not sure what happened. but looking at the current listen fetch patterns, i am wondering if there are some new troi changes deployed or playlists being generated which might have contributed to it.

<jasje[m]> "Support for showing will cost..." <- Since we are planning to integrate remote playback from Spotify and youtube the listening now may not be used as much.

The only places it will be used is when the user is listening to one device and want to switch to another device.

GautamShorewala[: Gautam Shorewala: listening now will still be used

jasje[m]: We could have a short way to update listening now offline, but mostly it would be like this: Play song -> Listen Submission service picks it up -> LSS sends it to backend -> Backend updates us.

Hello everyone, I'm Monu, a CSE student and a passionate coder. Really excited to make meaningful contributions to MetaBrainz and other [(...)Brainz] projects. Would love any guidance or help by mentors : )

<lucifer[m]> "mayhem: LB was down for a few..." <- but the last release was v2025.01.29.0, so why would we find problems now? recent changes have not been merged, nor released.

<mayhem[m]> "not yet. but before too long..." <- Ok gotcha, gotcha. Would it be collaborative filtering, content-based, or a mixture of both methods?