Obsidian PublicTxt Plugin
overview
- Adds collaborative features - to ‘connect’ Obsidian.md wikis to other PublicTxt Wikis
- Should work well with Obsidian PublicTxt Facets Plugin – which replaced the Obsidian Search Facets Plugin
Follow other people’s PublicTxt repos, see what changed since you last looked, and fork the pages you want into your vault. Each fork records where it came from in its front matter.
Status: early development. Nothing is released. The data model and the git layer are built and tested. The settings tab, check view and fork command are in progress.
Requirements
- Obsidian desktop. The plugin uses the git CLI, so it doesn’t run on mobile.
- git installed. If Obsidian can’t find it on your
PATH(common on macOS when Obsidian is started from Finder), set Git executable in the plugin settings.
How it works
- Sources are remote repos you follow, optionally narrowed to some folders.
- Each source is kept as a bare partial clone in your vault’s
remotes/folder. File contents are fetched only when needed. Consider addingremotes/to your vault’s.gitignoreand excluding it from Obsidian Sync. - A fork is a note copied from a source, with
fork_repo,fork_path,fork_bloband related keys in its front matter. Those keys are how the plugin tells when the original has changed.
Settings
| Setting | Default | Meaning |
|---|---|---|
| Fork folder | vault root | Where forked notes go |
| Remotes folder | remotes | Where the git clones live |
| Git executable | git | Path to git |