TeamPiped
Shared Playlists / Multi-User playlists
Describe the feature
The ability to add other Piped users to listen to or collaborate in a playlist. For example: User A owns "User A's Music Playlist".
User A shares a link to their playlist with User B. User B clicks a "follow" button on the playlist page, and can now see the playlist in their playlists tab. If User A adds "New Song" to "User A's Music Playlist", User B can see "New Song" on the playlist. User B can not add videos to this playlist.
User A clicks a "collaborate" button on the playlist. This could either generate a link, or User A can enter a Username, however Piped Developers decide is better for privacy. User C receives the link/is added as a collaborator. If User A adds "New Song" to "User A's Music Playlist", User C can see, edit and/or remove "New Song" from the playlist and vice versa. User B can see these edits from User C as well.
Why would this be useful to add?
This would be useful for social aspects of content consumption. This somewhat mimics a system Spotify and YouTube already have in place, and would make it easier to get people to switch to a platform that respects their privacy while being 1:1 feature complete with platforms their used to.
Concept(s)
No response
Additional context
Hi, sorry if this is a duplicate. I didn't see any other issues with this request but I'm notoriously bad at searhing GH issues
Acknowledgements
- [X] I have searched the existing issues and this is NOT a duplicate or related to another open issue.
- [X] I have written a short but informative title.
- [X] I filled out all of the requested information in this form.
Piped manages playlists fundamentally different than YouTube (and even Invidious): Since you don't have to have a Piped account to create playlists and Piped mostly works like more of a proxy for YouTube videos rather than a video platform on its own, Piped has opted to store the playlists locally in your browser. This comes with the benefit of more privacy, but the downside of making sharing harder and collaborating virtually impossible with this approach.
Sharing could work by putting every video ID into the URL, however, only to the extent that browsers allow as a maximum length. So huge playlists would not be able to be shared with this approach.
Collaborating and sharing huge playlists would require a solution where playlists would be stored on Piped's server, which would in turn require a significantly larger server storage capacity that Piped already has which would result in increased costs. This solution would also raise the question if Piped should shift entirely to server-stored playlists or offer and maintain both options.
I think, this is why Piped is less likely to implement the latter solution, especially since Google's battle with Piped (and Invidious) requires the Piped team to constantly make changes to their core proxy functionality to stay able to stream videos in the first place. Furthermore, people who host a Piped instance already are burdened with keeping their instance functional and not being intimidated by Google while continuing to offer this service for free that I wouldn't ask them to shoulder even more costs and probably maintenance.
When I still used Piped before Google started really cracking down on front ends, Piped saved playlists created by Piped users to Piped. I know this because I was logged in on Desktop and Libretube and the playlist synced to both. If this has changed then a developer is more than welcome to close this almost year old feature request.