Sporiff
In particular, I want to know what you think about the limitation around adding remote content to collections.
This question relates to this other one:
Was your intention that the favorites collection just be another collection that houses all favorited content, or that it should be the mechanism by which we sort favorites?
As of now, people can add any accessible track to their library, by adding them to their favorites. These are the only remote content that currently appear in the library, but it is enough to create confusion by mixing uploads and remote content in a user's library. As we only aim to make things easier to understand, no change of mechanism would be required I think.
On the other hand, adding albums, playlists and artists to favourites could benefit from such a change.
Matthieu's spec explicitly mentions adding remote content, so this may be a point of disagreement.
Oh no, I don't believe there is a disagreement. I don't think I talked about adding remote items to local collections for instance. What I did mention though was adding full remote collections to library. I think content we own (uploads) and content we follow should be kept in separate libraries, the only exception to this being favorites (and maybe playlists…).
I basically see a basic problem with implementing additions of foreign content to my collections.
If I am not mistaken, access to foreign content is an issue we already have with:
What if the owner of the foreign content stops sharing with me?
Then the content would not be accessible anymore, and the collection would appear grayed out in the collections list. With something like a forget/unfollow button?
Since my collections are sharable, can I basically reshare content which is owned by third parties?
Nope, because that's not your collection, that's theirs.
A workaround might be the following:
- If a Collection is public, I can "pull" its content into my Library (Technically this will create new entities of the audio which are owned by me).
- This wont be available for shared entities, since they are not public.
I'm not sure I understand this two points.
- You mean to add a remote collection to your library you can or you must pull its content?
- The owner of the new entity would still be able to set the visibility they want, right?
@mjourdan Does this sound like a fair deal to you?
Content replication is the kind of things I considered too. It has downsides, like quite a radical change of philosophy in how access rights are managed, encouraging unreasonable duplication of content, and requiring people to choose between uploading or adding remote collections to their libraries. This sounds like too much tradeoff over what is currently done. Also, Funkwhale claims to be a social thing. I feel like considering that when Funkwhale users leave or whole instances shut down, it's fair to see the conten they used to share go away too.
