From r/ObsidianMD π
β’ π 6 upvotes β’ β 9/10 β’ π high
*Analysis generated: Jan 12, 2026*
π Source: View on Reddit
—
Summary
The user expresses frustration with Obsidian’s alias system, contrasting it sharply with Logseq’s approach. They highlight that Logseq allows for retroactive creation of aliases in daily notes, which automatically unifies references across the vault. In Obsidian, adding an alias later requires manually finding and rewriting all existing, fragmented links, which impedes ‘delayed sense making’ and organic knowledge growth when concepts are identified as the same long after initial writing.
Key Insights
1. Obsidian’s alias implementation breaks delayed sense making because changes are not retroactively applied to existing references.
2. The desired feature is automatic unification of references when a new alias is defined, similar to Logseq’s mechanism.
3. Manual link rewriting severely hampers organic knowledge consolidation over time.
Enhancement Suggestions
1. Alias Auto-Update on Rename: Extend Obsidianβs rename functionality. When a file is renamed, *automatically* update all aliases pointing to the old filename. This directly addresses the core pain point of manual rewriting, offering a partial solution without full retroactive alias application. This is lower complexity than full retroactive linking but provides immediate value. (Productivity Idea, System Improvement – 2x value)
2. “Alias as Redirect” Option: Introduce a toggleable option for aliases: “Alias as Redirect.” When enabled, the alias functions as a true redirect β any link *to* the alias immediately follows to the primary note. This mimics Logseqβs behavior and allows for retroactive unification *without* altering Obsidianβs core linking philosophy. (Added Second Brain Feature, Improved System – 3-5x value)
3. Contextual Link Replacement Tool: Build a tool that identifies all instances of a term used as a link *within* a specified scope (e.g., current file, current folder, entire vault). The tool then offers a one-click replacement of those links to the newly defined alias. This isnβt fully automatic, but drastically reduces the manual effort compared to searching and replacing. (Productivity Idea, Focused Workflow – 2-3x value)
Analysis
This post articulates a significant friction point regarding retroactive linking and alias management, directly comparing Obsidian’s static linking model with Logseq’s more dynamic/automatic alias resolution. The core issue is the lack of automatic backlinking/unification when a new alias is added to an existing file.
—
*Curated by AI for Paul’s Vault Members*