Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) by mail-b.sr.ht (Postfix) with ESMTPS id E1A50FF124 for <~cadence/tube-devel@lists.sr.ht>; Sun, 27 Sep 2020 19:57:33 +0000 (UTC) Authentication-Results: mail-b.sr.ht; dkim=pass (1024-bit key) header.d=riseup.net header.i=@riseup.net header.b=N3QW+ucw Received: from bell.riseup.net (bell-pn.riseup.net [10.0.1.178]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4BzxJY0XTFzFdrk; Sun, 27 Sep 2020 12:57:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1601236653; bh=/ZQAIKczdOYzASoAyB2AXdtov/W9nD1zMYxBXA+9JbQ=; h=From:To:Subject:Date:In-Reply-To:From; b=N3QW+ucwi9awbdE/A2I6aALczHGIXnLZdEEAstEZcPvPIhtzfoRYNnKdk/64ctrjD Ng8w2ddXxePD7Fcrcu4vLdspBR7Tzz2cxbBwLQqAznReyH5GMYbc0Pp4HT6u+DyCCs XYbcwx/SMyc/aT2FaiwQ1JXOepF0b1tKbwuhQwDs= X-Riseup-User-ID: 257BBAC57BD7AD64F43DFEF9DB7CD3ABBEAC86336C741DFAC6D62670ABAFC16B Received: from [127.0.0.1] (localhost [127.0.0.1]) by bell.riseup.net (Postfix) with ESMTPSA id 4BzxJX4hwlzJnVB; Sun, 27 Sep 2020 12:57:32 -0700 (PDT) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 From: "Mason Hock" To: "Cadence Ember" , <~cadence/tube-devel@lists.sr.ht> Subject: Re: YouTube rate limiting Date: Sun, 27 Sep 2020 12:38:25 -0700 Message-Id: In-Reply-To: <08cd8ca9-9140-4511-9707-c8eac2871b87@disroot.org> On Sat Sep 26, 2020 at 4:43 PM PDT, Cadence Ember wrote: > People can actually already manually change the backend Second or > Invidious instance that the CloudTube frontend uses. Nice! I hadn't noticed that, but it's helpful. Thanks. > 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. It might be a little smoother if from the error message page the user could select and switch to a known working instance and immediately start watching the video they were looking for using the new instance. Cadence instances could have an internal list of known Invidious and Second instances, and periodically check to see which are currently rate limited by attempting to pull the information for a test video. > I also plan to add support for anti-captcha to Second so that it can > automatically unblock itself. anti-captcha isn't automatic. It is an online CAPTCHA sweatshop that has human workers solve CAPTCHAs manually. Some users and/or instance admins may not be comfortable with this, so it would be nice to have some alternative options as well. Automatic instance switching to spread the load across instances might reduce the frequency with which instances get rate limited, and perhaps users could have the option of occasionally solving a CAPTCHA or performing some action to attempt getting an instance unblocked, similar to a script I recall being prompted to run when encountering a blocked Bibliogram instance. > Automatically switching instances may be possible, and I will consider > this after I complete anti-captcha. Thanks, and thanks for all your hard work.