Thanks… I’m feeding back and pressing my case to get the whole hub disabled.
1 Like
Looks like a vote every 2 minutes, its at 606 right now.
Will Plex listen to the users? Vote and find out!
Just to note - that feature request, if you don’t include the implemented features, I believe has hit the top ten of all feature requests - ever - inside of a week.
aww man looks like i put the final nail in discovers coffin… lol
just want to point out that the users in that feature request thread are screaming about not having a choice while also asking to make the choice for all of their shared users. so there’s that…
Wow, I was wondering how it was ranking. That is amazing.
Not to mention all the people who voted with their feet and moved to other streaming platforms. Emby and Jellyfin have been getting a lot of free promotion and previews this weekend. I honestly didn’t know anything about them until now.
I believe those users will be happy if they can guide their shared users through the steps to disable Discover and etc.
TO ALL:
Short of calling senior executive management on the phone,
I’ve forwarded everything stated and linked.
2 Likes
Respectfully, I don’t think counting likes on that single comment will be representative of the whole. It relies on people reading this thread, and finding that comment. I think the vote count on the feature request is more accurate. I had to shift a vote to get counted there.
5 Likes
disable completely? thats uncalled for. just give users an option to disable for users who dont want it.
i like discover. it just need customization of user preference what they want in it.
I know. Please ignore.
I did a deep dive of the forum and came up with a better answer
1 Like
It seems like you are trying to engineer this on the fly to put out fires. No one is going to be happy with the result.
I would recommend the following:
-
If you are able, roll out the version that existed for all clients prior to April 5 (before these features were rolled out). I assume you have some kind of version control in place that would allow this. Do this today.
-
You have now bought yourself whatever time is needed to engineer this properly, examine the results of what caused and occured during this fiasco, and re-engineer it in a way that meets the needs of the users and the goals of Plex.
-
Before your next system wide roll-out, institute a proper beta test cycle, with users who are willing to help you test, before a massive rollout. You literally have an army of tech savvy users here, many of whom would be willing to help beta test this in a limited rollout and give feedback in a controlled beta environment. We understand what Plex is trying to accomplish with this rollout and we want Plex to succeed. Some of us will probably even use the features when they are rolled out again.
There is no downside to this, just a little humble pie to be eaten.
4 Likes
I really think the Plex management needs to do a serious reflection on this whole feature and the implementation. I am not sure I could think of a worse way to handle it.
Test an invasive beta feature on all customers, check.
Force that feature on all customers without notice, check.
Force users to accept that beta feature on each and every device they use independently, check.
Introduce content that was unasked for, check.
Send personal queries that a user assumed would be sent to their own server to 3rd parties, check.
This is a dumpster fire. If senior executives are not already heavily involved, it is worse than I thought.
If Jellyfin or equivalents start putting out ATV etc. clients, Plex is in trouble.
I really do take this whole ordeal as a slap to the face as a user. Not good.
4 Likes
Honestly, I’m surprised they haven’t already been pulled in on something like this.
They made this decision to mandate these outside sources on their user base; they should know how it is turning out.
Plex isn’t some sort of Fortune 500 company.
yup the users request are just as extreme as plex’ roll out.
IT’S ME AGAIN
I’ve chatted with the folks in charge of Discovery.
-
NSFW is their top priority and deploying the fixes as fast as the work is completed.
-
They know about the request for better control and are already on that but NFSW took priority.
-
Please be patient. There’s a lot of stuff happening today behind the scenes that you’ll see as soon as they finish their work.
9 Likes
But they also aren’t this small little startup. And the fact that they doubled down, insisting on whatever it is that they want, makes this worse.
There is no reason the Programmers should be making these types of decisions. This is C-Line level decision making.
The choice right now should be to pull down the features.
Then rethink how to proceed with an Opt-IN feature.
Thank you for taking notes and being an advocate. I really appreciate you being here.
4 Likes
Folks:
I am going to step back for now.
I have a S*** ton of work to do and this preempted everything.
I can always be paged but am otherwise not going to “watch” the thread for every post.
I will post again as soon as I have more info
6 Likes
