Extended Kodi Source Types / Information Providers - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Discussions (https://forum.kodi.tv/forumdisplay.php?fid=222) +--- Forum: Kodi related discussions (https://forum.kodi.tv/forumdisplay.php?fid=6) +--- Thread: Extended Kodi Source Types / Information Providers (/showthread.php?tid=379432) |
Extended Kodi Source Types / Information Providers - izprtxqkft - 2024-11-16 Currently there is no shortage of Streaming Media Servers namely Jellyfin, Emby, Plex, Mezzzmo which utilize Kodi Addons to bridge their server content to Kodi. As I see it this is a perfect pairing adding functionality to Kodi that otherwise is not even Kodi's intended goal as Kodi is a great standalone. Being standalone however means exactly that, it stands alone, a lot of effort can be made to share a library between Kodi instances utilizing MySQL f.e. but this can have it's own downsides and still requires a Server instance to sync the data. What I am wondering is if there is significant interest to work with these 3rd party Media Servers to provide a seamless integrated library. What I envision would be a simple (not so simple) addition to the Sources that Kodi can handle which would allow these media servers to act as file servers and metadata servers. As Kodi uses SMB, NFS and even HTTP as a Source adding Jellyfin, Emby, Plex, Mezzmo as a handled data source type. Obviously trying to wrap 3rd party protocols and try to keep them updated as those 3rd parties update things would be NEARLY impossible for a single project. But what if there were an added protocol adapter in which would be a simple framework for a Source that can be coded for by Jellyfin then they can just simply keep their own protocols up to date within the framework. The result would be that you don't have rogue addons inserting into the Kodi database and you could have simultaneous Sources to build your library combining SMB+NFS+HTTP+Jellyfin into a single library. Local Information metadata could be read from their respective Source servers. Most of all it would have to be a collaborative effort between Kodi and 3rd parties doing these Media Servers but the end result for users would be a great benefit as well as increasing Kodi's user base to include users from those 3rd party servers. Increased user base means increased interest which in turn should mean increased developer contributions. The entire question I am asking here is simple; "Would the Kodi developers even be interested in trying to develop these relationships with 3rd party developers to bring everything together under a single roof?" Yes it's a lot of work, yes it's a little bit ambitious, yes it would be quite some time before there were anything usable, most of all yes it would greatly benefit users and developers alike. Thanks for your time in reading and for any consideration of this incredibly complex end goal. RE: Extended Kodi Source Types / Information Providers - Fuzzard - 2024-11-17 https://forum.kodi.tv/showthread.php?tid=224794 I'm.guessing that's maybe what your after in a hand wavey fashion. If anyone looks to continue montellese's work, it's probably a good starting point. RE: Extended Kodi Source Types / Information Providers - izprtxqkft - 2024-11-17 (2024-11-17, 00:07)Fuzzard Wrote: https://forum.kodi.tv/showthread.php?tid=224794 i have seen this project, it tries to do far more than i am suggesting being both the media server side code and the kodi side the half that communicates with kodi is plenty at it's simplest i just mean a universalized version of the already existing "HTTP Source" that an api can be coded for by a media server instead of it parsing a very specific and generic HTML file listing - while being able to provide the metadata for those files listed RE: Extended Kodi Source Types / Information Providers - PatK - 2024-11-17 Politics aside, your enthusiasm and interest is not in question but when there is $ involved, practicalities and administration are beyond mortal values; we do appreciate the thought. |