This post is hidden because you reported it for abuse.
Show this post
Hi all,
I am sorry to have to inform you that we are having to turn off two Discogs features that we have been experimenting with over the last year - the Tracks feature, and the updated Collection feature. The reason for both are technical challenges in making the features stable and fast enough for us to run reliably for everyone.
I realise this may disappoint many of you. It is very disappointing for us as well. However, we have learned a lot from your feedback and usage of both features, and plan to bring them back in improved and stable forms in the not too distant future.
Thank you for your feedback and enthusiasm for the 20-year Discogs project: the best music database and marketplace in the world. We are committed to the continued success of Discogs and everyone who uses it.
This post is hidden because you reported it for abuse.
Show this post
Looks like I may have to update my new thread from just today. As a dev/product manager/tech lead at various times I feel your pain in mothballing something you have invested so much in! As a user of Discogs I have to say there really is a lot needed to make these useful to me, although Tracks at least had potential.
I'm sure you have your own plans and priorities, but is it worth revisiting Tracks as a contributor-driven rather than auto-generated feature? This would complement my new thread https://www.discogs.com/forum/thread/803012 by attaching properties to tracks to reference a common ID (although I guess it's more in the model of release->master rather than composition-> external identifier). It depends where your performance and stability problems lie, but I do think that contributor-driven is worth exploring; it may be more slower but also more reliable.
