mike

Joined 2 months ago

Last active 4 days ago membership youtube yt-dlp

This guide documents the complete process for downloading YouTube membership-restricted videos using AWS EC2, Docker containers, yt-dlp, and various anti-bot bypass techniques. This method is necessary because YouTube membership videos have strict protections including geo-restrictions, bot detection, SABR streaming protocol enforcement, and JavaScript challenges.

0 0 1

YouTube Membership Video Download Guide

Overview

This guide documents the complete process for downloading YouTube membership-restricted videos using AWS EC2, Docker containers, yt-dlp, and various anti-bot bypass techniques. This method is necessary because YouTube membership videos have strict protections including geo-restrictions, bot detection, SABR streaming protocol enforcement, and JavaScript challenges.

Success Requirements:

  • EC2 instance in a region where the video is available (Hong Kong worked for Chinese content)
  • Fresh browser cookies from authenticated YouTube session
  • PO (Proof of Origin) token generation via bgutil
Last active 1 month ago
0 0 1

Claude Desktop 3P Mode with LiteLLM

Claude Desktop has a third-party inference (3P) mode that allows the Desktop application to route inference requests through a custom gateway such as LiteLLM. This is configured separately from the normal Anthropic account login. Recent Claude Desktop configurations use a Claude-3p configuration directory and an inferenceProvider: "gateway" configuration. ([Gist][1])

Important: When configuring the LiteLLM gateway URL in Claude Desktop 3P mode, do not include /v1 in the Base URL. Claude Desktop adds the /v1/... API paths itself. For example, use http://localhost:4000, not http://localhost:4000/v1. A working 3P gateway will ultimately receive requests such as /v1/models and /v1/messages. ([GitHub][2])

1. Enable Developer Mode

Open Claude Desktop and go to:

Last active 1 month ago

Diagnosis and remediation for workspace pods stuck in Creating due to stale CSI mounts / kubelet volume queue deadlocks

0 0 1

Stale CSI Mount — Workspace Stuck Pending

Summary

Workspace pods (b70553ae, ebafc5da, d048256b) were stuck in Creating phase for 7–17 days. Root cause: a deleted Longhorn PV (pvc-81b676e6) left a stale device mount on worker-04, which blocked the kubelet's serialized NestedPendingOperations queue. Every pod needing a CSI volume mount on that node was deadlocked.

Symptoms

  • Workspace CRD stuck in Creating phase
  • Pod is Pending with PodScheduled=True but zero containers