3 ms·

Couldn’t this be addressed by standardizing around a protocol? That way client and server are decoupled and existing clients can work with new media server proj

Couldn’t this be addressed by standardizing around a protocol? That way client and server are decoupled and existing clients can work with new media server projects.

djbusby 3y ago
Like if my TV could just open the webpage of my in-home media server and let me browse and play.
- jwells89 3y ago
  Well maybe, but smart TV and streaming box browsers are unlikely to implement all the functionality pertinent to a high-grade home theater experience. Apps are better here, so what I had in mind was closer to standardization around existing popular protocols like that currently used by Kodi and Plex, both of which have high quality clients for just about every platform out there.
petepete 3y ago
Is that not what DLNA is?
- jwells89 3y ago
  Kind of, but as I understand it’s pretty barebones and can’t support an experience like that provided by Plex.
jsf01 3y ago
There is some interoperability between other clients today. For example, I have a Jellyfin server but in order to connect to it on my Apple TV I use the Infuse Pro app. I think that works more because of a standardized file structure that each app creates its own indexes for, so an actual protocol that they share would still be an improvement.
- zoriya 3y ago
  Infuse implemented code specifically for jellyfin and it uses jellyfin's own API. The only common protocol is dlna, but it's pretty limited and only really used on local networks.
  - deleted 3y ago
    [deleted]
  - oarsinsync 3y ago
    How insane would it be to expose a jellyfin compatible api?
    - zoriya 3y ago
      That would slow down development and new idea down a lot, I don't think it's even worth considering. It's probably easier to implement it on Kodi/Infuse/any other clients.
      - oarsinsync 3y ago
        > It's probably easier to implement it on Kodi/Infuse/any other clients Yep, it's definitely easier to get third party clients to implement your protocol. Kodi you can write your own plugins for, Infuse... requires their devs to care about your implementation. Chicken, meet egg? That said, I also fully admit I have no knowledge of your codebase, nor any knowledge of how extensive / complicated the jellyfin (or any other comparable media server) client api looks like, and I assume you have a better idea! Best of luck with this! I hope it succeeds!

Couldn’t this be addressed by standardizing around a protocol? That way client and server are decoupled and existing clients can work with new media server projects.

djbusby 3y ago

Like if my TV could just open the webpage of my in-home media server and let me browse and play.

jwells89 3y ago
Well maybe, but smart TV and streaming box browsers are unlikely to implement all the functionality pertinent to a high-grade home theater experience. Apps are better here, so what I had in mind was closer to standardization around existing popular protocols like that currently used by Kodi and Plex, both of which have high quality clients for just about every platform out there.

petepete 3y ago

Is that not what DLNA is?

jwells89 3y ago
Kind of, but as I understand it’s pretty barebones and can’t support an experience like that provided by Plex.

jsf01 3y ago

There is some interoperability between other clients today. For example, I have a Jellyfin server but in order to connect to it on my Apple TV I use the Infuse Pro app. I think that works more because of a standardized file structure that each app creates its own indexes for, so an actual protocol that they share would still be an improvement.

zoriya 3y ago
Infuse implemented code specifically for jellyfin and it uses jellyfin's own API. The only common protocol is dlna, but it's pretty limited and only really used on local networks.
- deleted 3y ago
  [deleted]
- oarsinsync 3y ago
  How insane would it be to expose a jellyfin compatible api?
  - zoriya 3y ago
    That would slow down development and new idea down a lot, I don't think it's even worth considering. It's probably easier to implement it on Kodi/Infuse/any other clients.
    - oarsinsync 3y ago
      > It's probably easier to implement it on Kodi/Infuse/any other clients Yep, it's definitely easier to get third party clients to implement your protocol. Kodi you can write your own plugins for, Infuse... requires their devs to care about your implementation. Chicken, meet egg? That said, I also fully admit I have no knowledge of your codebase, nor any knowledge of how extensive / complicated the jellyfin (or any other comparable media server) client api looks like, and I assume you have a better idea! Best of luck with this! I hope it succeeds!