Thanks! At the moment there's nothing for which soliciting donations would be worthwhile, but I will post if that changes.

This is unlikely to happen, but here's a simple Chrome extension that will let you control the volume for any site:

everynoise.com/site-volume-...

Download, unzip, go to chrome://extensions/, turn on Developer Mode, hit Load Unpacked, pick the unzipped folder.

(As best I can tell, since it also has no list.)

NRbG uses the reverse of "related artists in", essentially, and the two are not necessarily symmetrical. But if you also hook up Curio, you can use "myartists" as an NRbG genre to search all your liked artists. I do that plus a bunch of particular genres...

But if you'd rather have an unweighted shuffle by artist, just group before shuffling:

tracks/artist....shuffle.1:@<=100

You can reshuffle the created playlist from its Curio page, too.

This query randomizes all your tracks, but then groups the random list by artist and takes only the first track per artist, up to 100 total. This is effectively a weighted shuffle by artist.

E.g. here "Umbral Exorcism" is properly grayed out on _Moonbow Rebellion_, since it was previously released, but not grayed out on the single where it was new.

Oh, wait, in order to support multiple releases by each artist we need to get first dates by songkey, but mark oldness by track id:

Need some slightly less-final word than "mourn" here. But you're welcome for everything so far.

This affects several of the Listening History queries in Curio, but none of the ones that get cached, so it would likely only matter to you if you have your own saved queries derived from Listening History views, or similarly adventurous.

Previously in DACTAL this would have been:

tracks/artist...count,_count

which was an unlovely quirk left over from Thread, where aggregators all started with underscores, and appeared as magic pseudo-properties instead of a separate (and thus more easily extensible) operation type.

My guess would be that they were tracks that were released but then retracted or rescheduled. But no way to tell after the fact.

Happy to help figure out if queries could help you.

It has 7 null tracks at the beginning. Did one of my tools put them there?!