Video summary

🪨 Об Obsidian по чесноку

Main summary

Key takeaways

Technology

Technological / Product Concepts Mentioned (Obsidian + Personal Knowledge Management)

PKM definition / positioning

The speaker notes that Obsidian is often framed as “personal knowledge management (PKM)”, but finds the label a bit pretentious—because in practice it’s mainly “just notes.”

Core idea of Obsidian

  • A note-taking app that stores notes as text files with markup.
  • Notes can link to other notes using references.
  • The speaker likens it to building your own “local Wikipedia” (i.e., a personal, searchable knowledge graph).

Architecture & storage (“Volt” concept)

  • Notes live inside a user-created folder/repository structure (the speaker calls these “Volts”—storage locations).
  • Notes are regular text files plus related assets (e.g., screenshots/photos in the same folder tree).
  • Key emphasis:
    • It’s not an encrypted database.
    • Content is easy to copy, can survive if the app disappears, and can be opened using standard tools (text editor / image viewer).
  • Integration via file access: since everything is files on disk, other tools can integrate through filesystem sharing.

Synchronization

  • Obsidian itself is free, but sync is paid (cloud sync between devices).
  • If you don’t pay, the speaker claims you can still sync using community plugins that use Google Drive / Dropbox as a “broker.”

Plugins & extensibility

Obsidian is presented as having a large plugin ecosystem, largely built by community contributors.

Search and organization

  • The speaker values search across text files (finding notes by keywords).
  • He argues that he doesn’t need heavy cross-linking in his workflow, because each video project is mostly self-contained.

Handwriting plugin discussion (limitations)

  • Handwriting note-taking plugins exist, but handwriting is described as slow.
  • Exported handwriting annotations are described as unclear/awkward.
  • The speaker claims only PDF native support for handwritten annotations is reliable; other approaches often require device-specific exporting.

“Data lake” vs structured system

The speaker mentions wanting a Data Lake-like approach:

  • dumping information into a “pile,”
  • structured later for retrieval,
  • and connecting this to how he organizes folders and related assets.

Export / workflow for video production

His practical goal is storing materials for future YouTube videos, including:

  • note fragments, sketches
  • screenshots
  • comments
  • photos
  • memes
  • possibly videos

He also describes periodic housekeeping:

  • After making a video, he deletes the assets folder to free space (he mentions nearly ~1 TB).

Critique / fit-for-purpose analysis

He experimented with Obsidian as a possible system upgrade but concludes it didn’t provide benefits beyond his existing folder-based approach, mainly because:

  • Over-complexity for his needs
    • Requires learning markup commands.
  • Inconvenience for simple tasks
    • Especially checkboxes/to-do-style workflows; it’s optimized more for typing/text-first habits.
  • For basic organization, he prefers folders and conventional file management.

Review / Guide / Tutorial-like Guidance Given

The speaker frames advice as “how to try Obsidian” and highlights common beginner mistakes:

  1. Don’t over-import everything at once
    • Even though migration/import is possible, importing everything can turn into “incoherent crap” and derail the system.
  2. Don’t use Obsidian for everything
    • For example, task planning / kanban/scrumboard-style tools should be handled by specialized apps rather than forcing everything into Obsidian via plugins.
  3. Avoid littering your setup with many community plugins early
  4. Folder strategy warning
    • He criticizes creating many topic folders where the same note might belong in multiple places (confusing storage logic).
    • Suggests: create one folder per note type.
      • Example: a general repair note (“how to unscrew a stuck bolt”) applies to multiple repair contexts, so it shouldn’t be duplicated across many topic folders.

Anti-guru caution

He warns that Obsidian’s creators (and adjacent ecosystems) sometimes market:

  • expensive courses/newsletters/PDFs
  • “digital garden” / “PCM system” content

He advises skepticism toward monetized infocigan/guru-style systems.

Key Evaluation / Conclusion From the Speaker

  • Obsidian is technically promising (file-based backup, linking potential, plugins, sync).
  • But for his specific YouTube workflow—centered on:
    • search
    • folder-based video material storage
    • eventual deletion

—Obsidian feels too complex and not worth switching.

  • He ultimately returns to his hard-drive folder approach for video editing workflow.

Main Speakers / Sources

  • Single main speaker: a YouTube creator speaking in first person (no other named co-speaker).
  • Referenced tools/services mentioned:
    • Microsoft Outlook / widget
    • Apple Notes
    • Evernote
    • Yandex website
    • Google Drive / Dropbox (as sync “broker”)
    • Claude / “ChatGPT-like” AI (mentioned as examples)
    • Vim (used as an analogy for markup/keyboard experience)

Original video