My Question is pretty much the same as last year: What is the state of the supposed alternative for 3rd party Metadata Agents?
Last year, it was stated that you wanted to “double down” on the Server side and with the removal of 3rd party agents on the Shield, that there will be an alternative to the python-based metadata agents.
What is the state or progression on that? Will there be a grace period of some time to give developers the ability to bridge the two systems so that we are not caught off-guard because there was no announcement of the final removal on other server platforms as well?
Another thing is the new API, last year it was stated that metadata agents should use the “same API spec” as the official Plex agents. My question here would be how you imagined this to look like? I mean, from the API, it looks like those 3rd party metadata agents are now separate programs instead of part of Plex which wouldn’t really make them “first-class citizens in PMS and server owners” as it was stated last year, especially if you need the “old” token or the new JWT for it to access Plex.
So the question still is: What is the future of 3rd party agents? Is the goal to let developers create their own applications that need to run separately from Plex or is the Plan to have them in some way integrated in the Plex infrastructure, like they were before? I can’t really imagine that a user would be happy with having to run X separate apps next to Plex just to have different sources for metadata.
Fireside Awesome Question! Answer Post
Last year, it was stated that you wanted to “double down” on the Server side and with the removal of 3rd party agents on the Shield, that there will be an alternative to the python-based metadata agents.
What is the state or progression on that? Will there be a grace period of some time to give developers the ability to bridge the two systems so that we are not caught off-guard because there was no announcement of the final removal on other server platforms as well?
