You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I share my self-hosted configuration URL with friends and family, once they start using Comet, they can see JWT details, including our information like debrid APIs, in the browser's network tab. Is it possible to encrypt the JWT with a secret key in the URLs so that only the self-hosted Python files can understand it?
The text was updated successfully, but these errors were encountered:
If you still need that feature you can try my fork comet-uncached. Mainly for uncached support but also has the env TOKEN . You can also find a example env file for that fork here. When provided it will encrypt the config in the url and then decrypt it when received for example when playing a video. Hiding the config when traveling over the network.
Would appreciate any help any feedback to find bugs faster an make the pr possible faster of that fork.
If I share my self-hosted configuration URL with friends and family, once they start using Comet, they can see JWT details, including our information like debrid APIs, in the browser's network tab. Is it possible to encrypt the JWT with a secret key in the URLs so that only the self-hosted Python files can understand it?
The text was updated successfully, but these errors were encountered: