TeamPiped
Using other proxy instances
I'm a bit concerned about bandwidth use.
It seems technically possible[^test] to run just the frontend image without command to change the instance URLs. I'm assuming the proxy service will be the biggest bandwidth consumer.
Can we set up a piped backend service using a proxy of a public instance? (i.e., use pipedproxy-yyz.kavin.rocks as the URL for the PROXY_HOSTNAME value - this is what I saw in the network tab on the kavin.rocks instance)
My motivation is that I'd prefer to host the account/subscription data, etc for my private instance. But I'm not really fussed if another instance operator knows which videos have been watched.
[^test]: I've only tested to the point of running the 1337kavin/piped-frontend container locally and using entrypoint: ash -c '/docker-entrypoint.sh && nginx -g "daemon off;"' as the command. It seems to work as expected (not too surprising since it's a Vue app) and plays videos - I just haven't tested logging in yet
