Summary
Integrate terraphim with the Obsidian (~50k stars) and Logseq (~35k stars) PKM communities through parser extensions, community plugins, and a coordinated open-source launch.
Terraphim's KG parser already uses Logseq's synonyms:: property syntax -- which is the same syntax as Obsidian's Dataview inline fields. This gives us a bridge to both communities without inventing a new format.
Issues
Parser & Core
Plugins
Community Launch
Execution Order
#604 Obsidian format parser
|
├──> #605 Concept relationship layer
|
├──> #606 Obsidian community plugin
| |
| └──> #607 Logseq plugin (shared WASM core)
|
└──> #608 Community launch (after plugins ship)
Positioning
"Deterministic semantic search for your vault -- 15 MB RAM, zero LLM, zero cloud."
Unique differentiators vs existing solutions:
- vs Obsidian built-in search: synonym expansion, concept matching, sub-200ms
- vs Smart Connections plugin: no API key, no embeddings model, deterministic, private
- vs Logseq built-in search: full-text + semantic concept matching via Aho-Corasick
- vs any LLM-based solution: works offline, deterministic results, zero cost per query
The Bridge
Logseq property synonyms:: foo, bar = Obsidian Dataview inline field synonyms:: foo, bar
One syntax, two communities. Extend to also parse Obsidian-native aliases: from YAML frontmatter, [[wikilinks]] as concept edges, and #tags as categories.
Launch Targets
- HN Show HN (Tue-Thu 8-10 AM ET)
- Reddit: r/ObsidianMD (300k), r/logseq (30k), r/PKMS (25k), r/rust (300k), r/selfhosted (400k)
- Obsidian community forum + Logseq Discord
- Medium Obsidian Observer publication
- 3-min demo video
Exit Criteria
- Obsidian plugin published in community registry
- Logseq plugin published in marketplace
- Blog post + HN/Reddit announcement
- Parser handles all three formats: terraphim, logseq, obsidian
- 500+ Obsidian installs, 100+ Logseq installs, +200 GitHub stars (first month)
Summary
Integrate terraphim with the Obsidian (~50k stars) and Logseq (~35k stars) PKM communities through parser extensions, community plugins, and a coordinated open-source launch.
Terraphim's KG parser already uses Logseq's
synonyms::property syntax -- which is the same syntax as Obsidian's Dataview inline fields. This gives us a bridge to both communities without inventing a new format.Issues
Parser & Core
Plugins
Community Launch
Execution Order
Positioning
"Deterministic semantic search for your vault -- 15 MB RAM, zero LLM, zero cloud."
Unique differentiators vs existing solutions:
The Bridge
Logseq property
synonyms:: foo, bar= Obsidian Dataview inline fieldsynonyms:: foo, barOne syntax, two communities. Extend to also parse Obsidian-native
aliases:from YAML frontmatter,[[wikilinks]]as concept edges, and#tagsas categories.Launch Targets
Exit Criteria