Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEA] Support for incorporating negative signals, i.e. song skipped by a user #702

Open
animesh-wynk opened this issue May 16, 2023 · 2 comments
Assignees
Labels
Milestone

Comments

@animesh-wynk
Copy link

🚀 Feature request

It would be great if there is a support for using negative signals as inputs to the model. In the context of a music-streaming platform, a song skipped by a user is a negative signal which can be useful for understanding the preferences of a user.

Motivation

Negative signals, just like the positive signals, contain useful information about the preferences of a user, and being able to use it for training recommender systems can be helpful in delivering enhanced experience to the users. An example of a positive signal could be downloading a song. And an example of a negative signal could be skipping a song within 30 seconds. Using skip signals have shown to improve the user engagement as mentioned in this paper by Spotify.

@rnyak rnyak added this to the Merlin 23.06 milestone May 19, 2023
@rnyak rnyak added the enhancement New feature or request label May 23, 2023
@rnyak
Copy link
Contributor

rnyak commented Jun 28, 2023

@animesh-wynk can you give more details how these negative signals are defined given a positive? Meaning if someone downloads a song now, but skip another song two hours later, are you using this skipped song as negative signal for the song downloaded two hours ago? Basically how positive-negative pairs are integrated? thanks.

@animesh-wynk
Copy link
Author

animesh-wynk commented Jun 28, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants