I think you are going to believe what ever you want to believe. All I know is when you click through one of those links to other services we don’t make money, which is what I said. There may very well some other master plan I am not aware of and I am not going to get into a debate about what may be.
As far as timeframes we just have a lot of apps that have to sync up development and we set dates and try to meet them not because some outside company said we had to do it by X date. If we had caught the various bugs, especially the adult content showing for managed users, we would have delayed.
But you still released it in beta to everyone, with no option to delete, and when the problems were discovered instead of removing it, we had to wait weeks until you fixed it.
Maybe that’s why the betas are released for people who choose to try them, so that the rest of the world doesn’t have to suffer…
I get it, and I imagine it’s incredibly frustrating for all of you who have to eat all of this, even though most likely none of you were to blame. But this has been a few years in the making, with signs everywhere, and it still seems like a lot of people are still unhappy. Honestly, the best solution would be more open communication with Plex, but I understand that’s not going to happen.
Saying the ability to roll back (Un-stir) an update or give the ability to completely disable a feature is BS. Do you not use version control? Just be honest and say Plex is choosing to force this on the users that do not want it.
I do not see how this is a useful feature to me at all. I am sure someone does and good for them. To me, it makes it a real challenge to tell what movies I already own when I am buying them. Oh look it is in my search results. Nope, that is from some other service that is not mine. A service I have no interest in, will never use, and only muddled the results of a search of my own server.
As someone who runs the development of a software company myself, I can tell you I would be firing people if this occurred with my employees.
Why did Plex not have messaging created for support before the rollout? (Normally you would have at least a hot sheet with explanations of the changes and what they impact for support staff. This helps with understanding the change and gives a common message.) Why was there not a beta stage? Why was there no rollback plan in place? (All changes have bugs. A rollback plan is always necessary) Why was there no marketing announcements prior to the rollout?
This was a cluster of a rollout and IMO a cluster of a response to the fallout.
Even if you couldn’t disable the additional results (which you have been able to do since not long after Discover rolled out) they are clearly separated from anything found locally.
The issue you’re ‘facing’ has already been solved.
Perhaps BigWheel can provide some facts to help us know what to believe on this item:
Every other time Plex has offered media content from outside sources (Live TV, Movies & TV, Music) the users have been provided the option to Disable that content. A Disable switch was not offered on Discover.
Plex, so far, has never clarified whether is this was an oversight or a deliberate design choice. Can you please provide us with the fact on this matter?
Not really, It is not at a glance fixed. I have to look to see if my server is listed or not instead of it just not returning a result. This is generally done on my phone. My eyes are not getting better.
Thanks. Now if there was only a way to turn all of those settings off all of my clients at once. Maybe it could be called “Fully Disable Discovery & Search” or something. I assume there is an equivalent setting on each client?
I don’t know if it will be called that but afaik it will be an account level setting to disable all Discovery and sub settings to disable some bits but not others.
I have no personal feelings about it one way or another. I simply think it is unlikely that we will make separate clients doubling the amount of clients we already make which will inevitably lead to folks wanting bespoke separate features in each
I mean isn’t that exactly what a Beta is for? & why Beta is for those who choose to help by giving feedback & reporting bugs & take the risk of problems for the benefit of 1st look at new things?
Not really, the ability to fully disable it & the ability to do that on an account level instead of a client level are different.
The “Fully Disable” Plex has roundaboutly said “No” but has given the ability to disable MOST of it.
As for the Account-level we have been told that is coming, it just hasn’t come through yet. So @Leavemealone’s request is approved just pending, the other is still being fought to get as much Disable-ability as possible, but will almost certainly never be fully accepted.
