Date: Sat, 26 Sep 2020 23:43:04 +0000 (UTC)
From: Cadence Ember <cadence@disroot.org>
To: ~cadence/tube-devel@lists.sr.ht
Message-ID: <08cd8ca9-9140-4511-9707-c8eac2871b87@disroot.org>
In-Reply-To: <C5V3YQIKSL4T.2RLPS41CAI88P@libricia-thinkcentre>
References: <C5V3YQIKSL4T.2RLPS41CAI88P@libricia-thinkcentre>
Subject: YouTube rate limiting
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

People can actually already manually change the backend Second or 
Invidious instance that the CloudTube frontend uses. Second and Invidious 
are almost completely compatible (you may notice small differences in 
number formatting, quality sorting, or missing video durations, but these 
can be addressed in the frontend). The instance that is used can be 
configured in the settings page. I plan to design a special rate limited 
error message page that explains the situation and directs the person to 
the settings page to select a new instance.

I also plan to add support for anti-captcha to Second so that it can 
automatically unblock itself.

Automatically switching instances may be possible, and I will consider 
this after I complete anti-captcha.