FR: Submit tracks (add listens) without requiring to play to them

[redactedscribe]

Sometimes I notice wrongly tagged listen submissions on my ListenBrainz history feed and decide to delete them. Instead of having to re-listen to all the fixed tracks (typically a release), it would be useful to be able to select the tracks I want to resubmit and have them submitted with custom inserted_at and listened_at values.

Resubmit 4 tracks now (a mix of over and under 4 minute track lengths):

track#4 (10:00): Both *_ats = now - (-4:00 + 100% of track#4) track#3 (2:00): Both *_ats = track#4's listened_at - 4:00 - 50% of track#3 track#2 (5:00): Both *_ats = track#3's listened_at - 50% of track#3 - 50% of track#2 track#1 (9:00): Both *_ats = track#2's listened_at - 50% of track#2 - (-4:00 + 100% of track#1)

(example calculation may change depending on #17)

To customise the submission times, allow choosing between "now" or some past time (in milliseconds would be easiest to implement but not so human-friendly, but also not impossible to work with). See ListenBrainz' Add listens button (the reason why this isn't sufficient for manual resubmissions is that what is added won't reflect the metadata of local files, or include media_player etc).

If this feature could be abused, a limit could be put on how often these manual submissions can be made: Total time of previously manually submitted tracks must have passed since the last manual submission before making another (i.e. 26 minutes based on the example above). But, I don't see why a limit should be introduced since I don't think ListenBrainz' own Add listens feature has one either.

Thanks.

[phw]

Definitely useful. Also fits well into a customizable player like fb2k. Similar tickets include #6 and #7, each with a slightly different focus (noting this here just for reference).

Just two notes:

• inserted_at is not something that is specified. That is the time of import into LB and set there.
• There is some discussion in the MB forums about which timestamp exactly should ideally be used for listened_at. Different tools do different currently. Once this has been clarified I'll update the plugin accordingly.

But, I don't see why a limit should be introduced since I don't think ListenBrainz' own Add listens feature has one either.

Agreed