Germany
Germany
Sounds like a sensible idea, I will look into after I've finished working on the current set of features.I'd like to avoid such steps for new API. I have an idea how we could reuse code in a better way: could you provide a standalone dll for the trakt API as Nuget package?
Germany
Any news on this topic? There are some user requests about the broken feature in MP2 already. I can help with nuget packaging and can also do the upload to our MP feed (I do so for TVE3/3.5 also).Sounds like a sensible idea, I will look into after I've finished working on the current set of features.
I've never created a Nuget package, presumably it's straight forward. From memory there is one thing I would need to remove from the API class and that is the ApplicationId that MP1 uses, I think everything else should be okay.
Does this mean that current auth does no longer work at all? Or it does still work with "special permission"? If the latter, I think we should get this permission also for MP2.A little note about Authentication, since this would technically be a new API v2 app it would not be able to use the same authentication method, the type of authentication that is currently used by MP1 required special permissions and is now deprecated.
Hey @morpheus_xx, I don't believe the special permissions are available any more for the authentication method that MP1 usesDoes this mean that current auth does no longer work at all? Or it does still work with "special permission"? If the latter, I think we should get this permission also for MP2.
The linked authentication steps are quite complicated...
Germany
Germany