~chaosmonk

~chaosmonk/justos

Last active 9 months ago

~chaosmonk/public-inbox

Last active 9 months ago
View more

Recent activity

Re: YouTube rate limiting 6 months ago

From Mason Hock to ~cadence/tube-devel

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.

Re: YouTube rate limiting 6 months ago

From Mason Hock to ~cadence/tube-devel

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

YouTube rate limiting 6 months ago

From Mason Hock to ~cadence/tube-devel

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 →
```

[PATCH v2] Demonstrate that I can use git send-email 7 months ago

From Mason Hock to ~sircmpwn/email-test-drive

---
 mason-hock | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 mason-hock

diff --git a/mason-hock b/mason-hock
new file mode 100644
index 0000000..66cb3d4
--- /dev/null
+++ b/mason-hock
@@ -0,0 +1 @@
I have successfully used git send-email!
-- 
2.28.0
[message trimmed]

[PATCH] Demonstrate that I can use git send-email 7 months ago

From Mason Hock to ~sircmpwn/email-test-drive

---
 mason-hock | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 mason-hock

diff --git a/mason-hock b/mason-hock
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/mason-hock
@@ -0,0 +1 @@
I'm about to try git send-email
-- 
2.28.0
[message trimmed]