In what context an playlist will be federated ?
If pod a follow pod b, then pod A will receive playlist from pod B (blocked by https://forum.funkwhale.audio/d/209-domain-follow-feature/6)
The user manually follow the playlist
I think per the discussion in the other thread, the first scenario definitely counts. A playlist is another object which can be shared to the Service Actor's outbox if it is set to be public. Users can also ask to follow a playlist using a similar flow to following a user.
Manually follow playlist :
Follow here is seen has an activitypub activities, but in the UI this should be displayed has “Add this playlist to my playlist collection”
I do think including the "Follow" terminology is still helpful here. If you say you are "Adding" the playlist to a collection, it might feel like it should add the playlist as it is at that point in time. But users might change those playlists, which will update them for all followers. So "Subscribe" or "Follow" feels appropriate. @mjourdan might have some good insight on this.
If a user can add a playlist to its collection, the user playlist page (/library/me/playlists ) should be update to make the difference between user playlist and followed playlist
Yeah I definitely think there should be a separation here.
Do we want to update the playlist page (/library/playlists/playlist_id) for this ? (display the remote link for example)
I think that's a good idea, or at least making it very clear who the owner of the playlist is (in the same way @mjourdan has mocked up for shared collections).
What about playlist content ? Do we want the playlist content to be added to the user collection ?
I'm not sure about this from a UX perspective. In my head, all content is part of a collection. A playlist refers to content in different collections. As a user, my expectation is that if I add content to a playlist, it should inherit the visibility of the collection it's in.
As a user, I could add content that's hosted on my pod to a playlist. It might belong to me, it might not. It's not my choice to give other users access to that content.
So, I think what I'm saying is that the content in the playlist should inherit the visibility and permissions of its containing collection. If it's public, then anyone can add it. If not, users that don't have access should only see the metadata of the entry but not be able to play it.
