This sums up my thoughts pretty well.
+1 Enable the option to remove / edit listens.
Music recommendations and or similar users history based on my listen history.
Spotify URLs even for entries where they haven’t been submitted.
+1 Player client history based by user agent used to submit listens.
More predefined (ready to load Sql) Queries at BigQuery.
An android app/client that submits MBID’s.
2 posts were split to a new topic: Android player MBID submission support
More than anything I’d love to see some tools to be able to get some rudimentary per-user profile statistics like:
- Top 10 songs of the week
- Top 10 singles of the year
- Top 10 songs of all time etc.
- Artists discovered this year.
I tried to get some of this data via Big Query but there seemed to be a bug with how the data was stored which was preventing me from going deep into the past.
Hi @punkscience, welcome to the MetaBrainz forums.
If you are interested in ListenBrainz statistics and metrics, you might find this thread interesting. Feel free to leave some feedback there:
Would really like to seem time based charts. Lastimer.com was the one I remember using on Last.fm prior to the purge. There was also Normalisr which didn’t involve quite so much database traffic.
I also really liked the stream visualisation from Last chart (http://www.lastchart.com.s3-website-us-east-1.amazonaws.com/). My Last.fm user icon is the last successful graph I got from them.
I would also like to see the possibility of embedding BBcode in profiles, as was possible with the old Last.fm. Allowing the community to grow and express itself organically like that seems like something to be aimed for.
Cheers
Hey, just a heads up, we’ve written up this feature and released it now. It should be in your profile page (Sign in - ListenBrainz).
Thanks everyone for all the feedback! Please keep it coming. We’re a bit resource constrained in terms of contributors but we are listening to you and making LB better for everyone slowly but steadily!
Thanks @iliekcomputers for the follow-up and all the good work
Thanks so much for the follow up!! So glad to be able to take part again
Hi,
I moved here from Last.fm and I sorely miss the daily, weekly and yearly break downs of listening history (per user and globally). It would be great to have the possibility to see the following for different time ranges (maybe even custom ranges):
- top artists, albums, genres, songs, countries
- new artists, albums, genres, songs, countries
- biggest relative change e.g which artist or song jumped the most places
- most diverse day, week, month, year by genre, country, artist
For sure other can come up with more. It would great to have a page for all of those or even where people can make and share their own queries.
Then it would even be possible to have stats on the queries and for people to check out the most executed queries.
Thank you for making the “Artists” page finally work too!
Cheers
I checked out the projects github and the issues tab is disabled. IMO that’s probably what’s stopping contributions (at least it stopped me). I don’t know what to do or how to help and I don’t want to search a forum for suggestions.
Issues tagged as “help wanted” or “good first issue” go a long way to get new contributors.
All issues/tickets for the MetaBrainz projects are located at https://tickets.metabrainz.org, tickets for ListenBrainz can be found here.
(BTW, this is also linked from the website’s footer, next to the GitHub link and from the README on GitHub )
We are actively working on infrastructure for this and should have something by the end of summer!
If you wish to help or have suggestions, feel free to come over to irc or send me an email at param [at] metabrainz [dot] org (or post here).
Thanks, this is great feedback. I definitely agree that we can make things easier for new contributors.
Do you think a page explaining what to do and linking to the tickets page would have been helpful? We do have a page like that but I have a feeling it is outdated.
My wish is that I could add a property that indicates which player(/streamer) is playing the music, so that LB front-end could show (and filter) on players.
We’ve started tracking clients / players in the listening_from
field in additional_info. We’re gonna look at how to surface that information on the frontend and add filtering etc. In the meanwhile, you can submit the listening_from field for future listens!
Are there any recommendations of how to fill this field? E.g. is it more about the specific client, or more about the source?
What I mean is for example something like Rhythmbox: I could submit “Rhythmbox” in the listening_from, then one knows with which client software the listen has been submitted. But Rhythmbox also allows integration of various music services, e.g. Last.fm or Jamendo. For me that I have been listening to something on Jamendo is the more interesting I formation. So I could submit e.g. Jamendo as the source for listening_from.
Also used like this the field can complement the information present in the User-Agent header: The User-Agent can show the exact name and version of the client software, where listening_from more indicates the source of the music. For this it would be interesting if LB would store the User Agent for each listen as well.
When I suggested this I was thinking specifically of the name of the program, rather than the streaming source of the audio (OK, this is a bit ambiguous for Spotify, but there is only 1 client and 1 service here).
I think that proposing a new field for source could be interesting.
I’m not sure if a User-agent is a good idea - my concern is with how much data you want to add to it. Is it “Rhythmbox” or “Rhythmbox 2.1 (Ubuntu 18.04 gnome (like kde) xwindows)”? If it’s longer than just the name, how do you know where to chop it when showing on the website? What value do you get by being able to specifically differentiate the version of software used?
I’m definitely in favour of just the player name only.
Yes, I would be in favor of this. The Rhythmbox plugin already sends a field “source” for this purpose. I already proposed this for LB in
Would be great if this could be added as an official field. And I’ll extend existing clients I have implemented to include the listening_from field with the name of the application.