feat: add support for encrypted query parameters

[Fijxu]

Closes #29

Requires support in Invidious if videoplayback is going to be proxied trough Invidious, but that doesn't make that much sense since companion already does that. Same thing applies to piped-proxy

[absidue]

Why are you encrypting all query parameters, instead of only the ones you consider sensitive? This will break multiple audio track support as well as detecting when the streaming data has expired in 3rd party clients like FreeTube.

Then again I doubt most people are using Invidious with FreeTube anymore these days as public instances have the API disabled and it's a lot easier to use FreeTube's local API than self-hosting Invidious.

[Fijxu]

This will break multiple audio track support as well as detecting when the streaming data has expired in 3rd party clients like FreeTube.

You are right. I was only thinking on the Invidious side of things when I was doing it. I'll fix it

[unixfox]

Why are you encrypting all query parameters, instead of only the ones you consider sensitive? This will break multiple audio track support as well as detecting when the streaming data has expired in 3rd party clients like FreeTube.

I agree too, "ip", "pot" parameters would have been enough. The rest is OK for anybody to know the value of these parameters.

And encrypting everything adds unnecessary load, on top of the fact that just dealing with two parameters would be easier to implement in piped-proxy.

[Fijxu]

I was also thinking to add a configuration option to insert a list of query parameters that need to be encrypted. Something like this: server.protected_query_parameters = ["pot", "ip", "someparam"] so we can add more query parameters without the need of modifying the source code each time youtube adds a query parameter that needs to be secret. May be overkill for now, but if no one is against, I could add it

[alexmaras]

I'd look at using the fact that URLSearchParams objects are just arrays of arrays to avoid a bunch of string appending and handling you're having to do here. It's a lot more fallible than doing everything you need to do with a URLSearchparams object and then calling .toString() once at the end.

[unixfox]

I was also thinking to add a configuration option to insert a list of query parameters that need to be encrypted. Something like this: server.protected_query_parameters = ["pot", "ip", "someparam"] so we can add more query parameters without the need of modifying the source code each time youtube adds a query parameter that needs to be secret. May be overkill for now, but if no one is against, I could add it

I think we can make it evolve in the code instead as more parameters comes out.