Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
	by mail-b.sr.ht (Postfix) with ESMTPS id 12EEDFF108
	for <~cadence/tube-devel@lists.sr.ht>; Tue,  6 Oct 2020 19:06:44 +0000 (UTC)
Authentication-Results: mail-b.sr.ht;
	dkim=pass (1024-bit key) header.d=riseup.net header.i=@riseup.net header.b=N9+n5ho6
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 4C5Rll1vh8zFfGb;
	Tue,  6 Oct 2020 12:06:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
	t=1602011203; bh=AOd2NOAYouVgWZPX3S+ajilmvwBcW3z40u0qswxd0XI=;
	h=From:To:Cc:Subject:Date:In-Reply-To:From;
	b=N9+n5ho6bh3ptZ10UvowDBJ4nwg1BYji00xaMqb4v0ymapAFqKNmuTZJP6SKMEWq8
	 WFS/bWbY5TGWUe9KbLdk20T+6QU473m9vpBCkagtdrBTmlIzKsU5EJ6fSyRQB0Zl/B
	 pvFe/c3zGhbMyR0KO48IDIKyzJhDi/0Pk4PEWIBI=
X-Riseup-User-ID: C0F0C8571987CC0118DD40F10F2A833FC3DF137B1C71B0FCAEF43A4E4692CB2C
Received: from [127.0.0.1] (localhost [127.0.0.1])
	 by bell.riseup.net (Postfix) with ESMTPSA id 4C5Rlj4GC2zJqNw;
	Tue,  6 Oct 2020 12:06:41 -0700 (PDT)
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
From: "Mason Hock" <chaosmonk@riseup.net>
To: "Cadence Ember" <cadence@disroot.org>
Cc: <~cadence/tube-devel@lists.sr.ht>
Subject: Re: YouTube rate limiting
Date: Tue, 06 Oct 2020 12:01:29 -0700
Message-Id: <C661GQHI7C2D.SURD2J38BTD6@libricia-thinkcentre>
In-Reply-To: <ca51f257-aa43-41b9-a1a6-d5b7957fe402@disroot.org>

FYI, tube.cadence.moe is rate limited again.

I've thought of another suggestion which may be a little less ideal than
automatic instance rotation, but potentially simpler to implement:  In
addition to a default Second/Invidious instance, also define a fallback
instance to attempt when the default instance does not work (e.g. due to
rate limiting).  For now a relatively reliable Invidious instance like
invidious.snopyta.org might be a reasonable choice, and the user could
customize their fallback instance on the settings page like they can
with their default instance.