#metabrainz

Thanks aerozol ! Will look on monday and do some rebasing

Hi bitmap, reosarevok! I was trying to add https://swiperjs.com/react for a section

Facing this issue. What would be the best way to resolve this?

[musicbrainz-server] 14akshaaatt opened pull request #2453 (03homepage-revamp…akshat/supporters): Supporters Section in Homepage https://github.com/metabrainz/musicbrainz-serve...

lucifer I was thinking we could have an artist page on listenbrainz

Since we are going to have sitewide stats soon for LB, it makes sense to have the artist page with their respective stats in it as well

that would be really neat

XYZ artist has been listened by 123 users over 11,000 times for example. And the other minimal data can be fetched from MB while keeping their latest album cover as their profile picture

Me, aerozol and monkey could design the UI for it.

We can have this as one of the ideas for GSoC

Shame that artist images are so hard to come by

Yeah elomatreb[m]!

Top albums/recordings/etc would be other good statistics, similar to what's shown on a last.fm artist page

++ elomatreb[m]!

blame the copyright troll :/

akshaaatt: i am not sure i think those artist pages maybe a part of the MetadataViewer sprint we are going to work starting mid-next week. but either way i have been already working on the spark side of the things and so a lot of the backend part will hopefully already over by the time GSoC starts.

*not sure but i think

That's great news lucifer!

We can exclude it from the thoughts of GSoC ideas then

👍

akshaaatt: which version of swiper are you using?

v8 lucifer

i see, do you know if MB use ES modules? i didn't see a type: module in the root package.json so a quick guess would be no. in that case you'll have to use v6 or lower according to https://swiperjs.com/migration-guide#node-es-mo...

yup it doesn't https://github.com/metabrainz/musicbrainz-serve... so v6 or lower should work.

Right. Hence I think bitmap could suggest what's the best way to deal with it. Migrating to lower version or making some changes to get the latest versions working. Either is fine by me :)

yeah makes sense. getting latest versions would be hard (er?) though, esm modules require increasing browser targets. i wanted to do those in LB but browser compat was one reason i gave up last time.

Oh! That makes sense.

Also lucifer, what do you think about the idea of keeping the picture of the artist as their latest album cover? That would beautify the UI to a great extent.

Talking about MB and LB both

akshaaatt: unsure about that. maybe instead show ~5 albums with cover art on the page?

Works for me

lucifer after connecting our Spotify account, did we miss importing our playlists from Spotify to LB?

That feels like an obvious thing to do according to me

yeah its a pending task currently. it depends on the spotify metadata cache. need a way to map spotify track uris to recording mbids.

I also noticed that we are missing any stats for users based on the length of the tracks which they listen to

Does Listenbrainz track this sort of thing? It's not included in the JSON submission API

well, I guess it could be retrieved from the MB recording

right, MB has recording lengths but not all recordings too and not all listens are mapped to recordings. so one thing to consider what to do about tracks for which we can't obtain duration.

Put those through the Missing MB data page?

sure but what to do with those tracks on in the track length stats. completely omit or set to some default duration or something else?

You could just ignore tracks with unknown duration for the purposes of an analysis based on duration

I would say omit those and frequently alert the users that those are being ignored

other than that, implementation concern is either do it like the artist country endpoint or regularly import MB dumps in spark (we need this for release radar stuff anyway though) so. so its on the cards but hasn't been implemented yet.

Gotta onboard new editors to MB anyway

MusicBrainz is a gem btw. I used it a lot today and god damn got to know a lot more about my favourite artists and songs!

lucifer I think BP does not have a queue system currently.

Like if I can add tracks to the queue and those will be played accordingly. Also, a section for the queue can be added to the BP which can allow us to add/remove tracks from it

https://open.spotify.com/queue Looks like a good inspiration for doing this

yeah afaik it doesn't. sounds good. monkey too probably has thoughts about it.

This sounds like a good 175hrs LB project to me

👍

lucifer I had a question about 'Send a track to another user as a personal recommendation' GSoC idea listed. What would the share include? Because I don't think we have any streaming link available to share. Rather we should have a separate page for the track on LB, but MB already does that excluding the streaming facility.

In short the question is: What link will the share point to?

afaiu, a listen card like recommend a track does. the actual/exact UI hasn't been decided yet.

For example if I want to share a track to someone from LB to WhatsApp, the share would only include a picture/text about the track or will it lead the user to lb through a link?

I think if the feature is to present it on the feed like the recommend a track feature, we could have an option for the user to share it only with a few people from their followers list and on the frontend only show it those who are in that list and skip those who are not

ah no those are different things. acc to my understanding, this task is send a track on another user on LB. not share outside LB. though this could be added as a follow up.

That makes this project a one day task

Right lucifer

it won't be a one day task because it probably needs some backend work as well to add sharing to selected people only (although i can help with that if the fe work is more). monkey has more ideas about what the frontend might look like and what work it entails so he'll able to describe better about the idea.

Right. I think external share can be added to the project if the work would be less. Great.

Is the blend feature a big task for us btw lucifer?

Combining the listening habits of 2 users and making a playlist out of it

should be a decent length task. depends on how you want to combine the listening habit. for YIM, we did top tracks of 3 similar users - your tracks so could probably modify it.

I would like us to differentiate on that aspect by letting more than 2 users collaborate and make a playlist which combines all their favourites in maybe the listening order?

Also, can this blend be dynamic in nature?

Such that it updates as the users continue listening

LB allows multiple users to make a playlist manually. but blend is automatic i think.

Right

Automatic is the key here

yeah you could regenerate the playlist weekly or daily i guess for that.

That would be awesome!

I think even if this task takes 350 hours, it would be worth it!

But according to you lucifer, how lengthy will such a project be?

other troi playlist tasks are 175 hrs so this probably should take the same.

Great! I think mayhem would be interested in this idea btw

Coalesce can be a good name for this feature on LB

sounds good

Now coming to the MB android ideas, I think reviews from CritiqueBrainz can be a good 175hrs project to be added in the fragment where ratings, tags, etc are present Lucifer?

Or maybe we could have a separate fragment for the reviews

yes that sounds like a good idea. +1

Great!

For a 350hours project on the app, I think adding the ListenBrainz profile, showing the charts including the UI for it and fetching the data from backend would be good.

Inclusion of the native app brains-layer would go along with it

brainzplayer*

I could help with the BP stuff

i am unsure how much value is added by showing charts natively in app vs LB webview (not totally against but there are better things to work on imo). I'd suggest to focus more on the scrobbler/listen submitter in the app on that front.

lucifer have a look at https://github.com/PhilJay/MPAndroidChart. The adding charts part will be very easy once this is integrated :) But yeah we can keep the charts addition to be the last feature for the whole idea

sure but its double work. any new one on LB website would need to be recreated here which is not the best use of our resources. so things that can't be added using webview or have a bad UX there would be higher on the priority list.

The listen submitter can be improved maybe via reverse thinking and giving the user a window of 30mins before their listen is submitted to LB automatically. In order for them to cancel any listens they wouldn't want to submit

Agreed lucifer

yes sounds good

But the listen submitter in itself would be a 175hours project

makes sense

We can provide 2 175hrs projects and one 350hrs project then for the app

The 2 175hrs can be the CB and Submitter one

What would you expect from a 350hours app project Lucifer?

thinking about it but currently don't have one in mind.