I understand spark is needed to generate recommendation for users, I suppose what change is that analytics are move from troi to spark. I also suppose when it’s done Lb api is update so the palylists can be accessed directly instead of being generated by troi.
But why delete the patch in troi when they could be updated ?
Also I don’t know if you recall this discussion about allowing custom endpoints for recommendations : Sort troi patches by stability and use - #22 by yuioen. It’s not a problem to keep this for later but I think we might want to sort the patch stability issue, because it will be a poor user experience if patchs disappear randomly.
We could also drop troi at funkwhale and only use lb api endpoint that are stable (even if this is only two endpoint : Recommendations — ListenBrainz 0.1.0 documentation). I just need to know since I already spend some time working on this and would like to avoid loosing it jaja