You know, with @elan comments, and @gbooker02’s dismissive response, makes you wonder why more and more people are moving away from Plex. You can make all the arguments you want, and because it’s something they don’t see a value in, or a way to profit from, it’s not going to be done. It seems Plex thinks none of us are engineers, developers, programmers, etc and that we don’t understand what we’re talking about.
I never said “Support all the databases”. While I did say ‘supporting multiple databases’, this could be as easy as continuing to support SQLite and adding support for mySQL or Postgres.
@gbooker02 's response to me regarding this was:
Which again goes to show that Plex thinks we’re all dumb users with no knowledge. And as someone who has written software that supports multiple databases, and as others have done, we use an abstract layer, and try to stay away from things that are specific to one DB, but understand this isn’t always avoidable, and you plan for that.
It boils down to this; they’ve invested a good amount of time in developing PMS for use with SQLite. They have no intention on moving to a different DB. As Elan stated:
Which either he doesn’t monitor the forums/reddit/etc or is just refuses to accept that this is just not true. If this was the case, there would not be numerous posting on how to repair plex database corruption, etc. Further, unless I missed something in the privacy policy, Plex doesn’t know what media we have, or how much media an individual user has, so to make that statement is baseless and without data to back it up, unless Plex is collecting more media information than they let on And even the information that is sent to collect metadata information, the policy states:
- Usage Statistics for Personal Content . We may collect usage statistics for Personal Content. This includes information about your interaction with the Services, such as device information, duration, bit rate, media formats, resolution, and media type (music, photos, videos, etc.). Where possible, we will generalize this information to avoid identifying your Personal Content. Usage statistics do not include specific content titles or filenames. We may use information related to your usage to run and improve our Services, to provide, customize, and personalize communications and other content that we deliver or offer to you.
This is a reason I’m excited about the Olaris project. Out the gate they support MySQL and Postgres. While it’s not there yet in terms of everything Plex offers, it’s getting there and their developers are more than happy to take input, and implement things the community wants. Case in point, their invite system – I asked for a way once you invite someone to generate the full URL with the invite code, instead of just the invite code. Something simple, and instead of having to wait until the, was implemented. The project is open source, and they welcome PRs. I’m running it side-by-side and even displaying the content in libraries is blazingly faster than Plex rendering. I’m testing both their SQLite and MySQL backends and I’ve been impressed. As soon as they have a few more native clients, I think we will be leaving Plex behind all together.
It really feels like Plex has become somewhat complacent and feel like they are the Microsoft, Apple, etc of streaming and that users will just take what they give them and deal with it. Understand that there are more competition out there, and one day you can be knocked off your throne.
