GARDEN

Tag: VidHub

Posts tagged “VidHub”

2 posts ·

The Anatomy of VidHub and the Border Between Replicating and Reusing: Cloud-Direct Playback Needs No Server, Licenses Blocked by a VMP, and the MVP Bill of a Self-Built Shell

The reverse anatomy of the VidHub APK drew a clean border: cloud-drive access connects the client straight to each provider official API, never passing a VidHub server (which is exactly what Alist already finished); the playback core is ExoPlayer plus VLC dual-engine (the box hang was the VLC aout retry loop, and on PC mpv structurally lacks that hang chain); scraping rides TMDB (a free key suffices); and the one part that must reuse VidHub — the licenses decryption — is blocked by the NetEase Yidun VMP with real account-ban risk, so its benefit approaches zero. The verdict: build a shell — own UI (poster wall, continue-watching, multi-source management) plus Alist as the cloud layer plus libmpv for playback plus TMDB scraping; the experience is a VidHub PC edition with zero dependence on its servers. The MVP (browse → scrape → play on click → remember progress) is billed at one to two days. As a side quest, all leftover processes of MaaGakumasu and the DMM launcher were cleared (eleven processes; the adb server kept because other projects share it).

Three Candidate Tickets of the Now Bar and the Black Box of vidhub: The Product Verdict of a Status App, the Blind Zone of Unlogged Reels, and the Continuation of the Four Tailscale Gates

Two side lines closed into two verdict documents today. First, the Now Bar concept window (1,192 messages) set the product verdict of a status app — the Now Bar best displays tasks with a clear end point or a continuous state; static information belongs on the lock-screen large card. Second, the vidhub reverse subagent finished the black-box teardown and mapped a verification blind zone — Kumiao and Jiguang at logged-out state jump straight to the login page on play, so the reel question is unverifiable rather than passed. Third, the Tailscale auto-reconnect investigation confirmed the four rescue gates in effect (desktop autostart, the 90-second rescue, TUN replay, the real-state guard), with the c2 verification waiting for the box to boot.