gcrk My intention was that collections are supposed to be the major way to share content. Therefore you cannot share single tracks. How would they make their way into your collection then?
I don't understand how this is incompatible. Why you couldn't share single tracks ?
A want to share a private track Ap to B. A click the share button, a link is generated to an automatically generated collection that is only share with B. B can't do whatever he wants with the track, but it will only be visible to him sinc the rights are manage by A.
More generally : A wants to share its private content (Ap) with B. B add the private content Ap to his public collection (Bc). B share the collection with C. C can access the collection of Bc but cannot access the private content Ap.
mjourdan your own curated collections could be altered by file owners or external events
If the owner change the metadata ? This issue also exist with the followed content. Its not a problem only for collection. If you want your collection to be immutable you can create one without any foreign content.
Personnaly I would not allow metadata modification on my instance and would only accept song tagged with mbids to avoid this kind of issues and duplications. But this is another issue.
mjourdan unpredictable access rights when sharing your collection with other people
has I explained in my previous post the rights are manage by the owner of the files (eg : the uploader)
mjourdan encouraging people to make collections of content they don't own, would make the feature like an echo box for remote and unavailable content, making harder to find collections that actually share something
Depends how we want to power collections or music discovery. Unplayable content is hiden most of the time. So if an collection is empty for me we just don't show it. We can also count the number of accessible tracks and only show collections with a minimum amount of content. We could also create a hierarchy on the collection based on ownership. For exemple if we want to list the collections where a track is present we could show the owners collections first and then the collections sharing this content.
mjourdan Yes, and that's a problem, isn't it? If B make a collection to share with C, both B and C will expect to find the same music in it.
That's true, but can be resolve easily : we could prompt a warning when a collection contain private content not shareable to everyone.
mjourdan How so? Exploration is for discovering content you are not aware of. I cannot see how it would benefit of collections you already sorted yourself?
Because exploration means nothing without a way to save what I discovered in my adventures. I'm navigating into a friend collection F, I find an amazing hardcore track, I want to add it to my hardcore collection because I don't want to add the F collection to my library. And I don't like this track so much so I don't want it to be mixed up with my liked songs.
mjourdan Because if we don't how should I organize the content I follow ? We should create another kind of collections ?
You would not have to, the owner organized it for everyone they share their collection with.
Music classification its very very complex and subjective. I don't think you can only count on other people work to create classifications you like. And what if I only want a part of the collection and not all of it ?
