Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Subject: YouTube rate limiting
From: "Mason Hock" <chaosmonk@riseup.net>
To: <~cadence/tube-devel@lists.sr.ht>
Date: Wed, 23 Sep 2020 15:39:42 -0700
Message-Id: <C5V3YQIKSL4T.2RLPS41CAI88P@libricia-thinkcentre>

For the last few days, when I try to watch any video on
tube.cadence.moe, I get

```
Error
Could not extract video info. Instance is likely blocked.

RATE_LIMITED_BY_YOUTUBE

That error was generated by https://second.cadence.moe.

Watch on YouTube =E2=86=92
```

Shutting down second.cadence.moe so that users stop making requests
until your IP address gets unblocked might fix this in the short term.

In the long term, spreading the load across multiple instances of Second
and/or Invidious might prevent this from happening.  Having to switch
between different frontend instances creates friction for users
(in the form of migrating subscriptions, preferences, etc.), but unless
there is a reason CloudTube needs to be running on the same server as
Second, perhaps CloudTube instances could rotate between a list of
Second and/or Invidious instances as their backend to spread the load.
When a Second or Invidious instance gets blocked, CloudTube instances
could fallback to a non-blocked instance and avoid using the blocked
instance for a certain period of time to allow it to come back online.