When will the share playlist update come out? Is it only playlist sync that is out?
It would be super if one of the Plex Devâs would close this thread and force the requests for sharing onto its own topic⊠[-O<
Wouldnât it though⊠Plex needs to hire some more forum moderators.
Weâre about 20 pages too late to split this thread now. Weâre just going to let this thread keep going so we donât lose the likes.
@MovieFan.Plex said:
Weâre about 20 pages too late to split this thread now. Weâre just going to let this thread keep going so we donât lose the likes.
Maybe you can edit the title/first post?
I edited the first post.
If someone would like to create a new feature request thread for âshare playlistsâ (and then share a link to it), we can basically get things split here. Please be sure to be specific when describing the feature in the new post, since âshare a playlistâ is somewhat ambiguous and could mean a couple of different things.
âIf someone would like to create a new feature request thread for âshare playlistsâ (and then share a link to it), we can basically get things split here. Please be sure to be specific when describing the feature in the new post, since âshare a playlistâ is somewhat ambiguous and could mean a couple of different things.â
Chris:
What would happen to all the âLikesâ if we do what you suggest?
Would it not be simpler to add a completion date for when the sync option was released and leave this request as still open?
In your opinion what are the couple of different things you refer to?
@MovieFan.Plex said:
I edited the first post.
Should append some details about what was implemented [sync - how/what] and what the remaining request is. The OP seems to have maybe abandoned it.
@âChris Câ said:
If someone would like to create a new feature request thread for âshare playlistsâ (and then share a link to it), we can basically get things split here. Please be sure to be specific when describing the feature in the new post, since âshare a playlistâ is somewhat ambiguous and could mean a couple of different things.
How many different things could it mean?
Within the context of a Plex home Iâd think it just means being able to share a created playlist with other home members since playlists live local to a server. That way all the video references are intact. Could it mean something else?
I had interpreted the Sync part of this request to essentially be the component of the playlist sharing remaining in sync once shared. i.e. if itâs a smart playlist, content will get added on all users copies of the playlist.
@RandyJCA said:
What would happen to all the âLikesâ if we do what you suggest?
There isnât any ideal solution here. There is no way to know how many âlikesâ were related to the sync feature and how many were for the share feature; itâs fundamentally impossible to know that because the feature request included multiple things. (This is why any feature request should be very specific about the single thing itâs requesting.) That said, based on comments, the majority of the votes (but we canât know the exact ratio) were almost certainly for the âsyncâ side of the request.
So, the best solution seems to be to take this existing thread and treat it as the âsyncâ request and have a new one for the âshareâ request so that things can be handled separately and appropriately. Not an ideal solution, of course, but an ideal solution simply doesnât exist here.
In your opinion what are the couple of different things you refer to?
@Xen0sys said:
How many different things could it mean?
âShareâ could pretty easily be interpreted in a couple of different ways:
- the ability for the creator of a playlist to make it available to (read only) view/use by one or more shared users
- the ability for multiple different users to share one âcommunalâ saved playlist so that anyone could edit it
I rather suspect that most people interested in âsharing playlistsâ are likely much more interested in the former, but you never know. Even if someone is interested in both of those (or even some other interpretation), theyâre different features and so requests for them should be handled separately.
@âChris Câ said:
In your opinion what are the couple of different things you refer to?
@Psytropic said:
How many different things could it mean?âShareâ could pretty easily be interpreted in a couple of different ways:
- the ability for the creator of a playlist to make it available to (read only) view/use by one or more shared users
- the ability for multiple different users to share one âcommunalâ saved playlist so that anyone could edit it
I rather suspect that most people interested in âsharing playlistsâ are likely much more interested in the former, but you never know. Even if someone is interested in both of those (or even some other interpretation), theyâre different features and so requests for them should be handled separately.
Well to that I just say âyesâ - both of those things should be possible to consider it a polished feature IMO.
So far as I can tell, being able to sync x number of episodes from a series wasnât explicitly requested yet itâs in there and I simply would have expected it for the feature to be well polished.
@âChris Câ
I agree that a separate thread should be created. If itâs really needed then enough people will vote for it.
@Xen0sys said:
Well to that I just say âyesâ - both of those things should be possible to consider it a polished feature IMO.
Sure, both might get released at the same time as smaller parts of a larger meta-feature. But regardless of whether you personally think they should be âpackaged togetherâ, theyâre still separate individual features that could conceivably be released separately. Hence why they should be tracked separately.
@âChris Câ said:
@Psytropic said:
Well to that I just say âyesâ - both of those things should be possible to consider it a polished feature IMO.Sure, both might get released at the same time as smaller parts of a larger meta-feature. But regardless of whether you personally think they should be âpackaged togetherâ, theyâre still separate individual features that could conceivably be released separately. Hence why they should be tracked separately.
They are distinct sure and could stand on their own independently but consider this:
Say only the 2nd feature gets implemented. Half of the folks who wanted it could have placed higher importance on the 1st feature and would then clamor for that.
Likewise, if only the 1st feature were implemented then thereâs also every possibility that half of the folks who wanted playlist sharing were primarily after it for the 2nd feature.
To that end, to save headache and to not have to make yet another explicit feature request it just makes sense to do both in one fell swoop.
From the sound of it, the 1st feature could be globbed onto the 2nd feature as simply a read-only tag for non-creators/non-plex-home-owners.
I started a new Feature Request Thread
I like it!!! I hope others do
@Xen0sys said:
They are distinct sure and could stand on their own independently but consider this:Say only the 2nd feature gets implemented. Half of the folks who wanted it could have placed higher importance on the 1st feature and would then clamor for that.
Likewise, if only the 1st feature were implemented then thereâs also every possibility that half of the folks who wanted playlist sharing were primarily after it for the 2nd feature.
To that end, to save headache and to not have to make yet another explicit feature request it just makes sense to do both in one fell swoop.
From the sound of it, the 1st feature could be globbed onto the 2nd feature as simply a read-only tag for non-creators/non-plex-home-owners.
Iâm not a programmer, but I donât think itâs quite as simple as a read-only tag. Allowing users to edit a playlist created by someone else will require a significant amount of work beyond simply sharing.
As for whether half the folks want one piece or the other, creating separate requests and letting people vote on them is how we answer that question. Personally, if I were inclined to share my playlists with someone else, I would most definitely not allow them to edit my playlist. So I would vote for one, but not the other.
@beckfield said:
Iâm not a programmer, but I donât think itâs quite as simple as a read-only tag. Allowing users to edit a playlist created by someone else will require a significant amount of work beyond simply sharing.As for whether half the folks want one piece or the other, creating separate requests and letting people vote on them is how we answer that question. Personally, if I were inclined to share my playlists with someone else, I would most definitely not allow them to edit my playlist. So I would vote for one, but not the other.
I am however I think there was maybe a misunderstanding regardless.
Yes it isnât trivial to make playlists shareable and editable by others - this is essentially feature #2 if you will.
What I am referring to as a simple task is adding a read-only checkbox that essentially just disables this extra editing capability for non-creators.
There is already an ownership mechanism and presumably (after #2 is there) there will already be a sharing mechanism (not trivial). As I see it, itâs just one extra boolean flag tacked on to the playlist object itself thatâs basically a true/false for only-owner-edit or whatever. That and a checkbox in the GUI somewhere that controls it.
You are basically asking for #2 and #1 since you want playlist sharing & you want to control itâs read-only state. This actually supports my argument that multiple request threads could be problematic/irritating since you would want to vote for both.
If only the primary general request (#2) gets in, you will be waiting for #1 to finish before you can block access to editing for others. (I also want read-only support and wouldnât want my shared playlists editable)
For the sake of clarity I am reffering to these two as #1 & #2:
- the ability for the creator of a playlist to make it available to (read only) view/use by one or more shared users
- the ability for multiple different users to share one âcommunalâ saved playlist so that anyone could edit it
For anyone else coming into this thread here is the separate feature-request: https://forums.plex.tv/discussion/117742/request-share-playlists
@MovieFan.Plex said:
I edited the first post.
Could you put this in place of the âshare playlistâ request in the first post? (https://forums.plex.tv/discussion/117742/request-share-playlists) - That way folks will know where to go.
(Original post has been updated and the âsharingâ aspect of the original request is handled through the Share Playlists request thread. Please go there to vote if you want that feature.)
The ability to sync playlists is part of our new sync technology. That is already available in both the Android and iOS mobile apps. Weâll continue working to bring that to our Windows/Windows Phone app, too.
(Closing this thread because people keep posting about playlist sharing. Thatâs a different request.)
Below are some features (ideas) that I could use for âShared Playlistsâ. I understand that for various reasons all requested features may not be doable, may not be required or wanted by others, or will need other features added. This list can be considered as a starting point for a âNew Feature Requestâ or not should someone have a better idea:
-
There needs to be 2 classes of playlist users:
a. Those who can only use an existing shared playlist.
b. Those who have more capabilities that would include creating, sharing, maintaining or making changes to a shared playlist. Deletion is another matter see below. -
There needs to be multiple types of playlists:
a. One that have been designated as âSharedâ - can be the default value.
b. Those that are not shared â single user use.
c. Playlists that have specific users able to use them (think of it as parental controls). -
Playlist functionality:
a. Whoever creates a Playlist has complete control over that list. They can name, change, delete items, assign as use-only, assign other users to maintain this list short of deletion. This would need the ability for the server administrator to either assume the role of the original creator or to outright have those abilities.
b. Only the original creator or server administrator can delete a playlist. A feature that displays who is using or copied the list may be of some value.
c. Merge/copy existing shared playlist(s) into a new playlist.
d. No duplicate names allowed each list must have its own unique name.
e. Once in use a list cannot be renamed only deleted. A feature that can display who is using the list or copied it may be of value. Single user lists can be deleted or renamed by the creator at any time.
For now, thatâs as far as my thinking takes me. Any other ideas?
