Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#603 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
rust, tauri, wasm
Área
desktop, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)
Lenguaje dominante
Rust
Estrellas
62
Forks
5
Merge medio
2 h 27 min
PR fusionados (30 d)
1

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de terraphim/terraphim-ai

Todos los issues de terraphim/terraphim-ai

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.