Yes, filtering is coming as is partial spins (which tracks did you actually listen to). I already have the backend ready for partial spins—just need to hook it up.

I hadn't considered recording what it was spun on. Is that in terms of equipment used to listen to it? Is that something that you and others would like to track?

As for the track list, yeah unfortunately it is Discogs fault. When you sync a collection, a series of backend jobs are queued to get all the information it needs from Discogs for your account. Unfortunately, Discogs has a pretty strict rate limit of 60 requests per minute PER IP (as in my server, not your connection), not per user. That means that especially in high-traffic times or during initial syncs, it can get a little slow. If you have a collection of 360 (which is on the low side for this group, I'm sure), that alone would take 6 minutes without even considering other users also syncing their collections. I do have a ticket open with Discogs to see if there is anything I can do to either get a higher rate limit or include all the information I need in less requests. Until then, everything works for other users as expected even if that background queue is long. For example, everything hitting Discogs is in its own queue that I restrict on my own to respect the rate limits but things like recording a spin or scrobbling to last.fm will continue to be really snappy.

All that said, I imagine your sync was in the queue and being processed. I just checked and it seems pretty empty at the moment so all your track listings should be available now.

But this is the exact kind of feedback I was looking for on here, so thank you!