History · channels · the DBATR layer
YouTube, connected three ways 📺
Read what you actually watch, run the two channels from here, and build our own video layer underneath both — so the mission never sits on somebody else's algorithm. Efficiency first: one page, no hunting.
1. Your history 🧾
Straight truth: no application can pull YouTube watch history through an API — Google removed it. The Takeout export is the only real path, and it takes about four minutes.
- 1
Open Google Takeout on the account that owns the channels
takeout.google.com → Deselect all → tick YouTube and YouTube Music only.
- 2
Narrow it to history
Open "Include all YouTube data" → keep history (and playlists/subscriptions if you want them) → set format to JSON, not HTML.
- 3
Export once, download the zip
Google emails a link, usually within minutes for history-only exports.
- 4
Drop watch-history.json in below
The file is read on this device only. DBATR does not upload it, store it, or send it anywhere.
Drop your history in
- 💎 No app can read YouTube watch history through an API — Google closed that door. The Takeout file is the only honest path.
- 💎 Your file is parsed in this browser. Nothing leaves the device, nothing is written to the database.
- 💎 History is used to build for you, never to score you or sell you.
2. Managing the channels 🎛️
Two layers. A read-only API key shows public numbers for any channel. Signing in with Google is what actually lets DBATR edit titles, descriptions, visibility and playlists on your channel — with a token you can revoke in one tap, never a shared password.
Channel control read
Checking the channels…
What we can do
- ✅ Read either channel: subscribers, total views, video count, uploads playlist
- ✅ List and read every video, playlist, and live broadcast
- ✅ Pull comments for triage
- ✅ With OAuth on top of the key: edit titles/descriptions, manage playlists, schedule and start live broadcasts
What nobody can do
- 🚫 Read watch history or search history — removed from the API entirely
- 🚫 Read another person’s private data without their own sign-in
- 🚫 Bypass strikes, monetization rules, or content decisions
3. The DBATR video layer 🏗️
Built in order, each phase useful on its own. Phase five is where the subsidiary question gets answered with numbers instead of a hunch.
- 1
Phase 1 — Mirror
Every DBATR video listed and playable on dbatr.com, sourced from the two channels.
One address that never changes, even if a platform decides otherwise.
- 2
Phase 2 — Own the file
Native upload and hosting on DBATR storage, with captions and transcripts on every item.
A family on a prepaid phone needs low-data audio and text, not a recommendation feed.
- 3
Phase 3 — Simulcast
One live feed pushed to YouTube, Twitch and DBATR at once from a single deck.
Go live once, reach everybody, keep the archive here.
- 4
Phase 4 — The library
Topic shelves — legal steps, recovery, dogs, energy — no autoplay chain, no engagement engine.
People come for an answer. Give them the answer and let them leave.
- 5
Phase 5 — The question of a subsidiary
A written valuation and acquisition memo instead of a rumor.
Either we build the better layer or we buy the distribution. Both get costed honestly.
Video doctrine, wherever it plays
- 💎 Free to watch forever. No account, no paywall, no region lock.
- 💎 No ads, no sponsors, no product placement.
- 💎 No autoplay chain and no recommendation engine — the viewer stays in charge.
- 💎 Anyone in a video can pull it forever, one email, no reason required.
- 💎 Captions and a transcript on everything, audio-only version for low data.
The two channels and the DJ deck live at The Channels, the unedited doctrine at All Jake.