# Client identifiers in listen data

**URL:** <https://community.metabrainz.org/t/client-identifiers-in-listen-data/446632>\
**Category:** ListenBrainz\
**Tags:** listenbrainz\
**Created:** [October 7, 2019, 5:44pm UTC](https://community.metabrainz.org/t/client-identifiers-in-listen-data/446632 "2019-10-07T17:44:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![outsidecontext](https://community.metabrainz.org/user_avatar/community.metabrainz.org/outsidecontext/32/90_2.png) [@outsidecontext](https://community.metabrainz.org/u/outsidecontext)\
**Post date:** [October 7, 2019, 6:26pm UTC](https://community.metabrainz.org/t/client-identifiers-in-listen-data/446632/3 "2019-10-07T18:26:17Z")

</div>

> [@A proper foobar2000 submission component](https://community.metabrainz.org/t/a-proper-foobar2000-submission-component/446404/6):
>
> I suppose adding the component name to additonal\_info is a possibility but I’d much rather see something standardised first before I go making things up.

For the Rhythmbox plugin I added sending a “source” field in the additional data. But this is a bit different. Since Rhythmbox allows not only playback of local files but also from external services like e.g. lastfm or jamendo, the source gets set to this service. I personally find this more interesting then the playback software being used, but of course this also could be sent. I very much would like to see some standardization here an LB making use of this information.

---

_[View the full topic](https://community.metabrainz.org/t/client-identifiers-in-listen-data/446632)._
