Troi recommendation system

mayhem

Hi!

Sorry for the long silence, but life last quarter got very hectic. But once that all settled down, I started coding. I pretty much skipped xmas (so happy for that!) and spent nearly two weeks coding. And the results are rather quite impressive -- take a look at this branch I am getting ready to merge:

https://github.com/metabrainz/listenbrainz-content-resolver/tree/add-artist-element

The list of features has grown quite long!

mayhem

Now cleaned up and merged: https://github.com/metabrainz/listenbrainz-content-resolver

ppom

I may be totally out off-topic, but what do you think of using Typesense for Funkwhale search functionality? If we already have all the tracks, albums, artists synced into Typesense, that may be a very cool search engine, with little extra work. Related to #2236

mayhem

ppom Not off-topic -- this is why @petitminion add typesense to Funkwhale in the first place. The matching solution that is present in listenbrainz-content-resolver is meant to server as a non-server solution. (And works quite well for that job).

gcrk

ppom Thats actually something I was considering, however search isn't our huge focus at the moment. If you are willing to work on this, let me know!

petitminion

Amazing work @mayhem. I'm looking forward to implement this into funkwhale. Great idea to use the subsonic api to make troi aware of the local collection. We need to discuss some technical detail with the funkwhale team before starting the implementation but maybe I will make some experiments before o/ Will let you know 🙂

phw

petitminion Great idea to use the subsonic api to make troi aware of the local collection.

Just as a side note if someone wants to try the listenbrainz-content-resolver with Funkwhale: For this to work FW currently needs my patches from https://dev.funkwhale.audio/funkwhale/funkwhale/-/merge_requests/2695 for OpenSubsonic support.

It works with the current release versions of Navidrome and LMS.

« Previous Page