# How-to implement recordings feedback?

**URL:** https://discourse.mopidy.com/t/how-to-implement-recordings-feedback/5952
**Category:** Ideas
**Created:** [May 19, 2024, 11:47am UTC](https://discourse.mopidy.com/t/how-to-implement-recordings-feedback/5952 "2024-05-19T11:47:03Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)
#### Post date: [May 19, 2024, 11:47am UTC](https://discourse.mopidy.com/t/how-to-implement-recordings-feedback/5952/1 "2024-05-19T11:47:03Z")

</div>

Hi,

I’d like to extend [Argos](https://github.com/orontee/argos) client with a “love / hate” track feature (aka feedback).

I imagine a three state button “love / hate /no feedback” for each track and a read-only playlist populated from loved tracks.

At present time, [Iris](https://github.com/jaedb/Iris) implements the three state button on its own using [Last.fm](https://www.last.fm/) API; If I remember well it doesn’t rely on Mopidy for this. It thus expects each Iris instance to configure an access token to that API, and the Mopidy server has no knowledge of the user preferences.

An alternative to Last.fm is Listenbrainz. Their [Feedback API](https://listenbrainz.readthedocs.io/en/latest/users/api/recordings.html#feedback-api) has few paths related to recording feedbacks (submit and get user feedbacks, etc.). My plan is to use Listenbrainz, I found their [privacy policy](https://metabrainz.org/privacy) easier to read, understand and more open.

What would be a future-proof design for such a feature in a Mopidy client? Should everything be implemented client side? Should Argos consume an API provided by Mopidy-Listenbrainz? Should Mopidy be extended with a feedback API and back-ends allowed to implement feedback providers (and Mopidy-Listenbrainz would implement such a provider, Mopidy-Scrobbler another one)? Has any work already happened on this topic?

My intuition is that the future-proof design is the last one, but I’d like to hear from others on this topic.

Thanks for your… feedbacks!

---

<div class="post-metadata">

### Author: ![Matthias\_Meulien](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/matthias_meulien/32/2260_2.png) [@Matthias\_Meulien](https://discourse.mopidy.com/u/Matthias_Meulien)
#### Post date: [June 18, 2024, 4:33pm UTC](https://discourse.mopidy.com/t/how-to-implement-recordings-feedback/5952/2 "2024-06-18T16:33:08Z")

</div>

No idea on this topic, really?

---

<div class="post-metadata">

### Author: ![system](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/system/32/1_2.png) [@system](https://discourse.mopidy.com/u/system)
#### Post date: [December 18, 2024, 4:33am UTC](https://discourse.mopidy.com/t/how-to-implement-recordings-feedback/5952/3 "2024-12-18T04:33:33Z")

</div>

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
