~lomanic

Recent activity

[PATCH cloudtube v4] Proxy captions via new /proxy route 2 months ago

From Lomanic to ~cadence/tube-devel

We can add more authorized paths to authorizedPaths if we need
more resources to be pulled from the NewLeaf/Invidious backend
on the same domain.

This route forwards to the client a few headers like Bibliogram
https://git.sr.ht/~cadence/bibliogram/tree/ea7cd5d5/item/src/site/api/proxy.js#L28-29
so we can also use this route to possibly proxy videos in the
future.

We are strict about the url parameter not overriding the
NewLeaf/Invidious backend (instanceOrigin) by ensuring
fetchURL has instanceOrigin as prefix.
---
 api/captions.js | 25 -------------------------
[message trimmed]

[PATCH cloudtube v3] Proxy captions via new /proxy route 2 months ago

From Lomanic to ~cadence/tube-devel

We can add more authorized paths to authorizedPaths if we need
more resources to be pulled from the NewLeaf/Invidious backend
on the same domain.

This route forwards to the client a few headers like Bibliogram
https://git.sr.ht/~cadence/bibliogram/tree/ea7cd5d5/item/src/site/api/proxy.js#L28-29
so we can also use this route to possibly proxy videos in the
future.
---
 api/captions.js | 25 -------------------------
 api/proxy.js    | 24 ++++++++++++++++++++++++
 api/video.js    |  5 +++++
 3 files changed, 29 insertions(+), 25 deletions(-)
 delete mode 100644 api/captions.js
[message trimmed]

Re: [PATCH cloudtube v2] Proxy captions via new /proxy route 3 months ago

From Lomanic to ~cadence/tube-devel

I just forgot this remark indeed.

As-is it's only made to relay requests to the
NewLeaf/Invidious backend on the same
domain, the question to ask is more about if 
videos streams will go through both the 
NL/IV backend and the Cloudtube frontend or 
not. I wouldn't like to mix both proxies, to YT 
and to the backend, on the same route. 

I had the mindset to have only NewLeaf directly
talk to YouTube, and the frontend only care about presenting the data from the NL/IV API
(to be agnostic between backends), so looks
like /proxy will relay streams via the backend,