Diablofan
commented
8 years ago Why limit to Emby? We could extend support to Plex, Kodi, and others. All of them are self hosted media streaming solutions, which I would think is more okay than unofficial streaming services because you have to have the media yourself (don't know how you'll get it, I'll assume legally) so you'd be limited to your collection.
Now, for implementing this, we probably could go through the standard Web Browser recognition if you're streaming it to your browser, detecting on other devices (tablets, phones, tvs, consoles) is out of scope for Taiga. Plex for instance uses the nomenclature of {SHOW TITLE} - {S#} * {E#}, eg: "And you thought there is never a girl online? - S1 * E7". That should be enough information to allow Taiga to identify what we're watching.
We also have to make sure that you personally control the server. There isn't really a good way to determine that. For local network connections its simple, check if the remote system (grab hostname from URL) is on the local network by resolving its hostname ot an IP and check if the IP is in the same subnet. Simple enough right?
The problem escalates when the server we're watching is now not on your local network, eg streaming anime from home to where you're at. The problem then becomes how can we be sure it /is/ your server. To taiga initially it looks like a generic streaming site, even if it is your server. One way would be to add a config option saying this particular remote site is okay, but that is exploitable to allow for (indirect) support for KissAnime and other actual streaming sites, which is something that should be avoided for this kind of support. One way I can think of to check it is to query the server and check the reply. For instance, Plex when you go to http://server/web will bring up the web ui, and going to http://server/ will bring up a bit of XML. Then we could compare it to a stored plex email address and see if it matches, though this then requires having a plex account which I think should be avoided as well. Remote server support might not happen because of this problem with no real clear way to cleanly implement it without any sort of real hassle on us, especially since each server software does things differently.
Basically it comes to, how can we teach Taiga that Self Hosted Servers are okay, should we teach it to look at remote sites, how do we teach it to remote sites and check if its okay? Ultimately @erengy is the only one that can give the okay on what we can teach Taiga.
If we do get the okay, even if it is just local network, I'd be happy to add initial support for Plex, I think I could do Emby Support as well (my server did have emby installed at one point, I can just readd it as a test for Taiga).
Personally I would be happy even with local media server support, since its now what I primarily use to watch my anime, my browser through my server, as I can't use my server out of my home network because of my blasted slow att internet connection.
Edit: I'm an idiot and forgot about Plex and Kodi being supported already. I see no reason to not add it with those being supported already. Lemme check what needs changed and I'll get cracking on it, shouldn't be too much.
Akamaru
DrRandomacts
yocally
InFerNoBeasTz
ZeroOmar
With the nature of emby being open source I imagine it at least should be 'possible' but obviously I don't know how long it would take.
I did notice that there is a trakt.tv plugin that works wonderfully.
I suppose a shortcut could be to have tiaga pull from trakt.tv and that would actually work pretty well.
Although a native plugin or something would be amazing.
https://emby.media/ https://trakt.tv