Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Epic: Obsidian & Logseq community integration (vault parser + plugins + launch)

Aperta
#603 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
rust, tauri, wasm
Ambito
desktop, devtools

Direzione di ricerca

Start by reviewing the execution order and child issues #604-#608, beginning with the Obsidian format parser and its planned aliases, wikilinks, tags, and synonyms support. Use the listed exit criteria to define done: both plugins published, all three formats parsed, and the launch materials completed.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

architecture enhancement

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
  • #604 Obsidian format parser (aliases, wikilinks, tags) -- ~4h
  • #605 Concept relationship layer (wikilink edges in rolegraph) -- ~1d
Plugins
  • #606 Obsidian community plugin (WASM terraphim in Electron) -- ~2d
  • #607 Logseq community plugin (WASM terraphim slash commands) -- ~1d
Community Launch
  • #608 Launch positioning, blog posts, HN/Reddit/forum announcements

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)
Lingua principale
Rust
Stelle
62
Fork
5
Merge medio
2h 27m
PR unite (30g)
1

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di terraphim/terraphim-ai

Tutte le issue di terraphim/terraphim-ai

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.