← Back to changelog2026-06
Obsidian goes official — plus a new landing, faster analysis, and launch hardening
🔌 Official Obsidian plugin
- Listed in the community plugin directory — StackTube 0.1.0 is live in Obsidian's official directory. Settings → Community plugins → search "StackTube".
- Notes land in your vault — plain Markdown with YAML frontmatter. Zero duplicates (keyed by video), resumable sync, one-click sync from the ribbon icon. Uninstall the plugin and your files stay put.
- Public API + key issuance — new
GET /api/v1/notes endpoint (Bearer auth) and an API key panel under Settings → Obsidian. Keys are available on Pro and above (trial included).
- Landing and guides updated — Obsidian row in the output matrix, an official-plugin card, a 3-step connection guide, and a Help FAQ entry.
🎨 New landing and logo
- Landing rebuilt in three acts — problem → how it works → arrival, rewritten from scratch in an editorial structure.
- New symbol logo — full lockup and favicon set replaced.
- Note gallery — browse real analysis-note signatures at
/notes/gallery before signing up.
- Delivery "arrival sequence" motion — one note flowing out to five channels, visualized.
- E-ink section, four devices — Kindle · reMarkable · Boox · Supernote as equal cards.
⚡ Faster analysis
- The note shows up first — instead of waiting for the whole pipeline to finish, your note appears the moment it's ready; PDF and delivery continue in the background. Perceived wait time is down by nearly half.
- Parallel fetch, slimmer input — metadata and transcript are fetched at the same time, and the analysis step drops data it doesn't need, cutting total processing time.
🩹 Reliability & self-recovery
- Auto-monitoring recovered — fixed the root cause of new videos on your channels not being auto-detected for a stretch. Detection is back to catching everything.
- Steadier transcript fetching — a dedicated transcript API is now the primary path, reducing cases where a video was summarized from metadata alone. Note quality stays consistent.
- No charge for empty results — added a safeguard so an analysis isn't counted against your quota when a note wasn't actually produced.
- Payment → plan reliability — closed a rare case where a plan didn't apply after a successful payment, and made it retry automatically on failure.
- Hardened retries — widened automatic retries for transient API errors (rate limits, brief outages) to reduce failed analyses.
🖼 Scenes make it into your notes
- Video thumbnails embedded — the video thumbnail now rides along in the note (web, email, PDF, and the monthly digest).
- 📷 scene deep-link markers — at visually important moments (diagrams, code, charts), a "see this moment in the video" marker jumps you straight to the exact timestamp.
📖 Monthly digest PDF edition · E-ink rendering
- PDF edition of the monthly digest — delivered alongside the EPUB. Recommended for reMarkable, Boox, and Supernote.
- reMarkable rendering fixed — resolved black blocks covering pages, a runaway page count, and raw metadata leaking into the body.
💳 Plan gating
- Plans now behave exactly as the pricing table says — worker-side gating implemented, so items like Starter's weekly monitoring match the actual processing cadence.
- One source of truth for plan copy — landing, billing, and dashboard all describe plans identically.
- Help FAQ refreshed — outdated spec descriptions brought in line with current behavior.
🔄 Integration reliability
- Dropbox token auto-refresh — fixed uploads silently failing about four hours after connecting.
- Drive filename handling — fixed duplicate uploads triggered by apostrophes in titles.
- Delete-sync consistency — deleting a note now reliably moves it to archive across Obsidian, Drive, and Dropbox.
🔧 Other improvements
- Gallery filled with real notes —
/notes/gallery is now populated with real analysis notes instead of placeholders, so you can see the actual output before signing up.
- Public contact form — reach us from
/contact without signing up.
- Korean login stability — fixed a session issue that intermittently forced Korean-locale users to log in again.
🔒 Security
- Recurring code review + tighter access control — internal data functions locked down to service-only access, with a recurrence-prevention checklist added to our development rules.