#listenbrainz

In LB-1658,... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* In LB-1658,... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* In LB-1658,... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

also, while submitting a listen, let's say i put the track name as XYZ... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* also, while submitting a listen, let's say i put the track name as XYZ... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

as I saw that the track name changes sometimes on Listenbrainz after linking the spotify listen to musicbrainz

suvid: there are a bunch of reasons due to which we don't want to retain deleted listens forever, one is data privacy/gdpr. i don't think we need to support the use case of deleted listens being imported again because its probably very niche. unless i am missing something. and in general we want to avoid people deleting and importing the same stuff again.

as for the other question, no the metadata is not changed completely. but added separately as a mbid_mapping field to the track metadata. you can click on the 3 dot menu, then inspect listen and see the json of the listen. listens whose metadata is changed and other listens too which have been mapped manually or automatically will have a mbid_mapping field.

Also: you wouldn’t want to automatically skip importing any and all deleted listens, because someone could have a legitimate reason for deleting a batch of listens, and then re-adding some (I think I have done this before…)

yeah makes sense, if such option were to exist it would be configurable anyway.

i think letting users specify a time range of listens they want to import from LB should be good enough. if there are use cases which require more control, we can add those later when people ask for it.

also suvid, i am not sure what the duplicate listens issue you are pointing to but the one that is most common and exists in current importers is imported listens being a second or two ahead or behind the listens that already exist in the database. so even if you considered deleted listens there would be duplicates.

lucifer[m]: Ohh

I get it now

So not much can be done regarding this right?

at the moment no.

Hello, I’m currently working on the ListenBrainz iOS app and would like to know who I should contact for guidance regarding Swift-related questions. I’d be grateful for any suggestions. Thank you!

<lucifer[m]> "at the moment no." <- ohh i see

thanks for the clarification 😊

<lucifer[m]> "i think letting users specify..." <- should it be from starting date to end date? or is starting date to present is also fine?

should I also add the end date for the imports? 🤔

s/is//

the UI should have options for the user to specify both start and end date.

ok i'll edit it 👍️

both being optional.

<lucifer[m]> "the UI should have options for..." <- Updated! :)

krishnacosmic: Probably jasje, who has been coordinating LB app development

Not sure if relevant, but FYI there is a Swift wrapper for the LB API, here: https://wiki.musicbrainz.org/External_Resources...

<sparksphereinspi> "Hello, I’m currently working..." <- Hi! You can start by posting your messages in the development channel #metabrainz (this is a community channel) and tag me or akshat for any queries

ok

<monkey[m]> "m.amanullah7: don't start..." <- monkey: Thanks!! for the info, as of now i just wants to work on a real world project and wants to learn and explore! Keeping ur guidance i'll also work on proposal.