Share Obsidian Links That Actually Work Everywhere
🔗 **Source:** [Share Obsidian Links That Actually Work Everywhere](https://joost.blog/obsidian-agent-links/)
> [!note]+ Document Notes
> tags: [obsidian, agents, note-taking]
> author: Joost de Valk
> source: joost.blog
> reference: [https://joost.blog/obsidian-agent-links/]
> date created: 2026-02-25 10:00
>
> # 🏷️ Title: Share Obsidian links that actually work everywhere
>
<!-- deep-read:sections start -->
## 🧭 Table of Contents
- [📝 Summary](#-summary)
- [📖 Main Content](#-main-content)
- [🗒️ Notes](#️-notes)
- [📚 References](#-references)
- [🗣️ Paraphrase](#️-paraphrase)
- [📰 Newsletter](#-newsletter)
- [✅ Action Items](#-action-items)
- [🧪 Hypotheses](#-hypotheses)
- [📊 Methodology](#-methodology)
- [❓ Questions](#-questions)
- [🔮 Future Research](#-future-research)
- [💡 Implications](#-implications)
- [🧠 Learning Styles Assessment](#-learning-styles-assessment)
- [📊 Accessibility Assessment](#-accessibility-assessment)
- [🌍 DEIB Assessment](#-deib-assessment)
- [✅ Logical Validity](#-logical-validity)
- [🛡️ DARVO Analysis](#-darvo-analysis)
- [🎯 Conclusion](#-conclusion)
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author introduces obsid.net, a redirect service that turns `obsidian://` note links into HTTPS URLs usable in chats like WhatsApp and Telegram.
- Why it matters: It bridges personal Obsidian workflows with agent/human chat tools, keeping links tappable everywhere.
- Key stakeholders: Obsidian users, agent developers (OpenClaw, Claude, etc.), teams collaborating via chat.
- Risks and tradeoffs: Reliance on an external redirect host; minimal privacy and availability considerations.
- Bottom line: Use `https://obsid.net/?vault=…&file=…` instead of raw `obsidian://` in any context that blocks custom URI schemes.
## 📖 Main Content
- The problem: Obsidian deep links (`obsidian://…`) work great locally but fail in most messaging apps and web environments that block custom schemes, so agents can’t reliably share Obsidian notes back to humans.
- The solution: obsid.net exposes a simple HTTPS front-end (`https://obsid.net/?vault=…&file=…`) that safely passes through to the local `obsidian://` URL handler, requiring no extra client install.
- Usage pattern: Agents (like OpenClaw or cron jobs) output obsid.net URLs in conversations; humans tap them in WhatsApp, Telegram, Slack, email, etc., and are redirected into the right Obsidian note.
- Benefits: Links behave like normal web URLs, survive logs and archives, and can be shared across devices and apps while still landing in the user’s private vault.
- Uncertainties: Long-term reliability, rate limits, security/privacy guarantees, and whether self-hosted variants or open specifications will emerge.
### 🗒️ Notes
- The author relies heavily on Obsidian for personal and agent-related workflows; all core OpenClaw files live in the vault.
- Messaging apps treat `obsidian://` as inert text or blocked URIs, breaking the feedback loop where an agent references a specific note.
- obsid.net acts purely as a redirect layer: no client install, leveraging the OS-level Obsidian URL handler already present.
- The URL format is explicit: `https://obsid.net/?vault=…&file=…`, making it easy for agents or scripts to construct.
- Using HTTPS avoids issues with logging, bookmarking, and corporate security filters that distrust custom protocols.
- Agents like Codex, Claude, or scheduled jobs can standardize on obsid.net when emitting references to notes, simplifying tooling.
- The article stresses that this keeps “every Obsidian link tappable” across chat frontends while users continue to live in their own vaults.
- The author encourages experimentation: converting old `obsidian://` links and wiring helper “skills” into agents.
## 📚 References
- Obsidian: https://obsidian.md/
- obsid.net redirect service: https://obsid.net/
- Original article: https://joost.blog/obsidian-agent-links/
## 🗣️ Paraphrase
- Paragraph A paraphrase: Obsidian is the author’s central hub, but chat apps can’t open its native `obsidian://` links, breaking workflows with OpenClaw.
- Paragraph B paraphrase: obsid.net wraps Obsidian links in standard HTTPS URLs so agents can safely share notes in WhatsApp, Telegram, Slack, and similar tools.
## 📰 Newsletter
If you’re deep into WordPress and also living out of Obsidian, you’ve probably hit the “dead link” wall when sharing `obsidian://` URLs in Slack or WhatsApp. Joost de Valk’s new obsid.net bridge turns those into regular HTTPS links that still open your local vault. It’s a neat pattern for agent-assisted workflows and documentation handoffs. Pair this with your favorite Obsidian-WordPress publishing plugin to keep private notes first while still making them easy to reference across your team’s chats.
## ✅ Action Items
#### DevRel
- Document how to generate obsid.net URLs from SDKs and sample bots.
- Create demos showing agents sending tappable Obsidian links in chat.
- Add quickstart snippets for popular languages to construct `vault`/`file` URLs.
- Publish a blog post and short video walking through an end-to-end agent + Obsidian workflow.
- Gather developer feedback on edge cases (multi-vault, mobile vs. desktop).
#### OSPO
- Assess licensing and governance model if obsid.net or similar tooling is open sourced.
- Define policies for storing note identifiers in corporate chat logs.
- Review security posture: data collected at redirect, logging retention, and jurisdictions.
- Align with SBOM and inventory practices if agents reference sensitive internal docs.
- Establish guidance for upstream contributions if the project opens up.
#### Community
- Host office hours for integrating Obsidian-based workflows in contributor onboarding.
- Encourage maintainers to use obsid.net-style links for personal notes referenced in public spaces.
- Provide contributor guides on safely referencing private docs from public issue trackers.
- Collect use cases from different teams and share patterns back with the community.
#### WordPress
- Core: Explore internal design-doc workflows that use Obsidian locally but share stable links in chats.
- Core Performance: Document performance investigation notes in Obsidian, share via safe redirect links on Trac/Slack.
- Core AI: Prototype WordPress-focused agents that return obsid.net-style links into contributor chats.
- **Core Program Team:** Standardize on link formats for private working notes vs. public artifacts.
- Mobile: Improve docs for using Obsidian notes as part of mobile dev runbooks.
- Playground: Ship examples where Playground environments are documented in Obsidian and referenced with safe URLs.
- Community: Include Obsidian workflows in organizer kits for meetups/WordCamps.
- Training: Build curricula for “local-first documentation with Obsidian,” including safe sharing patterns.
- Marketing: Highlight content workflows that start in Obsidian and surface into WordPress.
- Support: Let support teams keep internal playbooks in Obsidian while sharing stable links internally.
- Design: Encourage designers to keep exploratory work in Obsidian and cross-link from Figma/issue trackers.
- Documentation: Maintain working drafts in Obsidian; publish finalized docs to DevHub/HelpHub.
- Photos / TV / Polyglots / Accessibility / Meta / CLI / Hosting / Tide / Openverse / Themes / Plugins:
- Identify whether teams could benefit from local, Obsidian-based notes and document best practices for referencing them via HTTPS redirects without leaking private content.
#### The WPOCC
- Programs: Offer fellowships that include training on local-first note systems like Obsidian.
- Projects: Use Obsidian + safe-linking patterns for governance clinics and sprint planning.
- Funding experiments: Support open tools that provide self-hostable obsid.net-style redirectors.
### FAIR
- Technical independence: Encourage local ownership of notes while using minimal external redirect metadata.
- Policies and covenants: Clarify expectations around logging and funding for shared infrastructure like redirect services.
- Productized governance artifacts: Provide templates (charters, agreements) stored in Obsidian and shareable via neutral links.
## 🧪 Hypotheses
- H1: Providing an HTTPS wrapper for `obsidian://` links will significantly increase how often users share Obsidian notes in chat apps.
- H2: Agents that output obsid.net-style URLs will see higher user engagement and follow-up actions than those that output plain text references.
- H3: Teams using Obsidian with safe redirect links will report fewer “lost context” issues in chat-based collaboration.
- H4: Reliance on a third-party redirector is acceptable to most users if no note content is stored server-side.
### 📊 Methodology
- Design A/B tests comparing workflows with raw `obsidian://` text vs. obsid.net URLs in Slack/WhatsApp.
- Collect telemetry (click-through rates, error reports) where users opt in.
- Survey Obsidian and agent users on perceived friction before and after adopting redirect-based links.
- Run small team pilots inside organizations and measure support tickets, onboarding time, and doc discovery issues.
### ❓ Questions
- Does obsid.net log full query parameters, and how long are logs retained?
- How will multi-device setups (desktop vs. mobile) behave with these redirects across platforms?
- Can users self-host an equivalent redirect to avoid third-party dependency?
- What happens if Obsidian is not installed on the device that opens the link?
### 🔮 Future Research
- Explore standardizing a generic “local knowledge link” pattern for tools beyond Obsidian.
- Investigate offline-resilient variants that queue openings until a vault is reachable.
- Study security models for mapping external URLs to sensitive local resources.
- Integrate with identity and permission layers for team-shared vaults.
### 💡 Implications
- Practice: Easier cross-device note access could deepen adoption of Obsidian in developer and contributor workflows.
- Policy: Organizations may need clearer policies on referencing private repositories of knowledge in public or semi-public channels.
- Security: Redirectors must minimize data retention and exposure, especially where vault names or file paths are sensitive.
- Education: Training on local-first knowledge management should include safe, interoperable linking patterns.
- Funding: Shared redirect infrastructure may require sustainable hosting or community funding.
### 🧠 Learning Styles Assessment
- Reading level estimate: Roughly B2–C1 (upper intermediate to advanced), by Flesch-style heuristics (technical terms, complex sentences).
#### 👀 Visual learners
- Present: Clear conceptual contrast between `obsidian://` and HTTPS links (described verbally).
- Improve: Add diagrams of the redirect flow from chat → obsid.net → Obsidian vault.
#### 🔊 Aural learners
- Present: No explicit audio support.
- Improve: Provide a short audio/video walkthrough demonstrating tapping a link in WhatsApp into Obsidian.
#### 🗣️ Verbal learners
- Present: Concise, concrete explanations and examples of URL formats.
- Improve: Add analogies to more familiar patterns (e.g., URL shorteners) in plain language.
#### 🧩 Kinesthetic learners
- Present: Implied hands-on step (“convert one of your old links”).
- Improve: Provide a step-by-step checklist with copy-paste examples and test scenarios.
#### 🧠 Logical learners
- Present: Clear problem/solution framing and causal explanation (blocked schemes → redirect → success).
- Improve: Add a simple decision table for when to use obsid.net vs. other approaches.
#### 🧑🤝🧑 Social learners
- Present: Focus on use in conversations (chats, agents).
- Improve: Offer prompts for teams to design shared workflows around Obsidian and chat tools.
#### 🧘♀️ Solitary learners
- Present: Article suits independent experimentation with one’s own vault.
- Improve: Include reflection prompts about personal note-linking pain points.
#### 🌿 Naturalistic learners
- Present: No direct environmental framing.
- Improve: Use ecosystem analogies (e.g., local vs. cloud habitats for data) if helpful.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Likely standard article markup with headings and links.
- Improve: Ensure descriptive link text (not just raw URLs) and correct language attributes.
#### Keyboard navigation
- Present: Standard web page behavior should suffice.
- Improve: Confirm tab order clarity and visible focus styles.
#### Contrast and readability
- Present: Depends on joost.blog theme; text likely high contrast.
- Improve: Validate contrast ratios and line height; avoid overly dense paragraphs.
#### Text resizing and reflow
- Present: Modern responsive design likely adequate.
- Improve: Test up to 200% zoom and ensure no horizontal scrolling for body text.
#### Media and captions
- Present: Primarily text; minimal media.
- Improve: If adding screenshots or diagrams, include alt text and captions.
#### Forms and interactions
- Present: None critical for this article.
- Improve: N/A.
#### Standards reference
- Map any gaps (if identified) to WCAG 2.2 AA criteria on contrast, reflow, and link purpose.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Tooling-focused, culturally neutral content.
- Improve: Include examples from diverse work environments (e.g., non-English teams).
#### Inclusive language
- Present: Neutral, technical language; minimal jargon beyond tool names.
- Improve: Add a brief glossary for tools and terms (Obsidian, URL handler, agents).
#### Neurodiversity support
- Present: Short, focused article with clear topic.
- Improve: Add more headings and bullet lists to break up text; minimize context switching.
#### Representation
- Present: No people imagery; neutral.
- Improve: If adding visuals, show diverse users and contexts.
#### Psychological safety
- Present: Non-controversial, practical topic.
- Improve: Provide clear statements about privacy assumptions and limitations.
### ✅ Logical Validity
#### Strong reasoning
- Causal chain: custom URI schemes are blocked → links fail in chat → HTTPS redirect preserves functionality; this is straightforward and supported by common platform behavior.
- Practical inference: If agents emit HTTPS links instead of custom schemes, they will work in more environments; aligns with browser and app security models.
#### Fallacies
- None obvious; the article is descriptive and low on strong, generalized claims.
#### Tone of voice
- Tone: Practical, mildly enthusiastic, and conversational.
- Example: Encouraging readers to “give obsid.net a try” and wire it into agents.
### 🛡️ DARVO Analysis
- Deny: No denial or minimization of harm; the article addresses a usability gap.
- Attack: No attacks on other tools or users.
- Reverse victim/offender: Not applicable; the piece describes a technical workaround, not a conflict.
## 🎯 Conclusion
The article proposes obsid.net as a simple HTTPS redirect layer that makes `obsidian://` links usable in everyday chats and agent-human interactions. For Obsidian-heavy workflows—especially those involving AI agents—standardizing on `https://obsid.net/?vault=…&file=…` keeps links tappable across platforms while still opening notes in your local vault. Next steps: test converting existing links, integrate the pattern into your agents or scripts, and evaluate whether you need additional privacy or self-hosted options.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5–10-word present-tense claim
> [!quote] [Share Obsidian links that actually work everywhere](https://joost.blog/obsidian-agent-links/) by [[Joost de Valk]] via [[joost.blog]]. Published 2026-02-25. Accessed 2026-02-25.
> “The whole point of obsid.net is to make those notes shareable in agent-human conversations.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://joost.blog/obsidian-agent-links/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [Share Obsidian links that actually work everywhere](https://joost.blog/obsidian-agent-links/)
> “It’s just a simple https://obsid.net/?vault=…&file=… link you can paste into WhatsApp, Slack, email, or any chat that refuses to run custom schemes.”
Two lines: context and use.
[view highlight](https://joost.blog/obsidian-agent-links/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] HTTPS wrappers keep Obsidian links tappable
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Local-First-Knowledge]] [[Agent-Chat-Workflows]]
#### [Z2] Agents can safely share local note links
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Developer-Agents]] [[Documentation-Workflows]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Try converting existing `obsidian://` links to obsid.net for daily chats — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
- [F2] Add obsid.net URL generation to my agent tooling — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
- [F3] Investigate privacy and self-hosted alternatives to obsid.net — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
---
<!-- deep-read:sections end -->
[[3. Resources/Readwise/Full Document Contents/Articles/Share Obsidian Links That Actually Work Everywhere|Full Document Contents]]
## Document Notes
---
tags: #obsidian #agents #note-taking
author: Joost de Valk
source: joost.blog
reference: [https://joost.blog/obsidian-agent-links/]
date created: 2026-02-25 10:00
---
# 🏷️ Title: Share Obsidian links that actually work everywhere
## 🧭 Table of Contents
- [[#📝 Summary]]
- [[#📖 Main Content]]
- [[#🗒️ Notes]]
- [[#📚 References]]
- [[#🗣️ Paraphrase]]
- [[#📰 Newsletter]]
- [[#✅ Action Items]]
- [[#🧪 Hypotheses]]
- [[#📊 Methodology]]
- [[#❓ Questions]]
- [[#🔮 Future Research]]
- [[#💡 Implications]]
- [[#🧠 Learning Styles Assessment]]
- [[#📊 Accessibility Assessment]]
- [[#🌍 DEIB Assessment]]
- [[#✅ Logical Validity]]
- [[#🛡️ DARVO Analysis]]
- [[#🎯 Conclusion]]
### 🔗 References
- Include links cited in or relevant to the article.
## 📝 Summary
- What happened: The author introduces obsid.net, a redirect service that turns `obsidian://` note links into HTTPS URLs usable in chats like WhatsApp and Telegram.
- Why it matters: It bridges personal Obsidian workflows with agent/human chat tools, keeping links tappable everywhere.
- Key stakeholders: Obsidian users, agent developers (OpenClaw, Claude, etc.), teams collaborating via chat.
- Risks and tradeoffs: Reliance on an external redirect host; minimal privacy and availability considerations.
- Bottom line: Use `https://obsid.net/?vault=…&file=…` instead of raw `obsidian://` in any context that blocks custom URI schemes.
## 📖 Main Content
- The problem: Obsidian deep links (`obsidian://…`) work great locally but fail in most messaging apps and web environments that block custom schemes, so agents can’t reliably share Obsidian notes back to humans.
- The solution: obsid.net exposes a simple HTTPS front-end (`https://obsid.net/?vault=…&file=…`) that safely passes through to the local `obsidian://` URL handler, requiring no extra client install.
- Usage pattern: Agents (like OpenClaw or cron jobs) output obsid.net URLs in conversations; humans tap them in WhatsApp, Telegram, Slack, email, etc., and are redirected into the right Obsidian note.
- Benefits: Links behave like normal web URLs, survive logs and archives, and can be shared across devices and apps while still landing in the user’s private vault.
- Uncertainties: Long-term reliability, rate limits, security/privacy guarantees, and whether self-hosted variants or open specifications will emerge.
### 🗒️ Notes
- The author relies heavily on Obsidian for personal and agent-related workflows; all core OpenClaw files live in the vault.
- Messaging apps treat `obsidian://` as inert text or blocked URIs, breaking the feedback loop where an agent references a specific note.
- obsid.net acts purely as a redirect layer: no client install, leveraging the OS-level Obsidian URL handler already present.
- The URL format is explicit: `https://obsid.net/?vault=…&file=…`, making it easy for agents or scripts to construct.
- Using HTTPS avoids issues with logging, bookmarking, and corporate security filters that distrust custom protocols.
- Agents like Codex, Claude, or scheduled jobs can standardize on obsid.net when emitting references to notes, simplifying tooling.
- The article stresses that this keeps “every Obsidian link tappable” across chat frontends while users continue to live in their own vaults.
- The author encourages experimentation: converting old `obsidian://` links and wiring helper “skills” into agents.
## 📚 References
- Obsidian: https://obsidian.md/
- obsid.net redirect service: https://obsid.net/
- Original article: https://joost.blog/obsidian-agent-links/
## 🗣️ Paraphrase
- Paragraph A paraphrase: Obsidian is the author’s central hub, but chat apps can’t open its native `obsidian://` links, breaking workflows with OpenClaw.
- Paragraph B paraphrase: obsid.net wraps Obsidian links in standard HTTPS URLs so agents can safely share notes in WhatsApp, Telegram, Slack, and similar tools.
## 📰 Newsletter
If you’re deep into WordPress and also living out of Obsidian, you’ve probably hit the “dead link” wall when sharing `obsidian://` URLs in Slack or WhatsApp. Joost de Valk’s new obsid.net bridge turns those into regular HTTPS links that still open your local vault. It’s a neat pattern for agent-assisted workflows and documentation handoffs. Pair this with your favorite Obsidian-WordPress publishing plugin to keep private notes first while still making them easy to reference across your team’s chats.
## ✅ Action Items
#### DevRel
- Document how to generate obsid.net URLs from SDKs and sample bots.
- Create demos showing agents sending tappable Obsidian links in chat.
- Add quickstart snippets for popular languages to construct `vault`/`file` URLs.
- Publish a blog post and short video walking through an end-to-end agent + Obsidian workflow.
- Gather developer feedback on edge cases (multi-vault, mobile vs. desktop).
#### OSPO
- Assess licensing and governance model if obsid.net or similar tooling is open sourced.
- Define policies for storing note identifiers in corporate chat logs.
- Review security posture: data collected at redirect, logging retention, and jurisdictions.
- Align with SBOM and inventory practices if agents reference sensitive internal docs.
- Establish guidance for upstream contributions if the project opens up.
#### Community
- Host office hours for integrating Obsidian-based workflows in contributor onboarding.
- Encourage maintainers to use obsid.net-style links for personal notes referenced in public spaces.
- Provide contributor guides on safely referencing private docs from public issue trackers.
- Collect use cases from different teams and share patterns back with the community.
#### WordPress
- Core: Explore internal design-doc workflows that use Obsidian locally but share stable links in chats.
- Core Performance: Document performance investigation notes in Obsidian, share via safe redirect links on Trac/Slack.
- Core AI: Prototype WordPress-focused agents that return obsid.net-style links into contributor chats.
- **Core Program Team:** Standardize on link formats for private working notes vs. public artifacts.
- Mobile: Improve docs for using Obsidian notes as part of mobile dev runbooks.
- Playground: Ship examples where Playground environments are documented in Obsidian and referenced with safe URLs.
- Community: Include Obsidian workflows in organizer kits for meetups/WordCamps.
- Training: Build curricula for “local-first documentation with Obsidian,” including safe sharing patterns.
- Marketing: Highlight content workflows that start in Obsidian and surface into WordPress.
- Support: Let support teams keep internal playbooks in Obsidian while sharing stable links internally.
- Design: Encourage designers to keep exploratory work in Obsidian and cross-link from Figma/issue trackers.
- Documentation: Maintain working drafts in Obsidian; publish finalized docs to DevHub/HelpHub.
- Photos / TV / Polyglots / Accessibility / Meta / CLI / Hosting / Tide / Openverse / Themes / Plugins:
- Identify whether teams could benefit from local, Obsidian-based notes and document best practices for referencing them via HTTPS redirects without leaking private content.
#### The WPCC
- Programs: Offer fellowships that include training on local-first note systems like Obsidian.
- Projects: Use Obsidian + safe-linking patterns for governance clinics and sprint planning.
- Funding experiments: Support open tools that provide self-hostable obsid.net-style redirectors.
### FAIR
- Technical independence: Encourage local ownership of notes while using minimal external redirect metadata.
- Policies and covenants: Clarify expectations around logging and funding for shared infrastructure like redirect services.
- Productized governance artifacts: Provide templates (charters, agreements) stored in Obsidian and shareable via neutral links.
## 🧪 Hypotheses
- H1: Providing an HTTPS wrapper for `obsidian://` links will significantly increase how often users share Obsidian notes in chat apps.
- H2: Agents that output obsid.net-style URLs will see higher user engagement and follow-up actions than those that output plain text references.
- H3: Teams using Obsidian with safe redirect links will report fewer “lost context” issues in chat-based collaboration.
- H4: Reliance on a third-party redirector is acceptable to most users if no note content is stored server-side.
### 📊 Methodology
- Design A/B tests comparing workflows with raw `obsidian://` text vs. obsid.net URLs in Slack/WhatsApp.
- Collect telemetry (click-through rates, error reports) where users opt in.
- Survey Obsidian and agent users on perceived friction before and after adopting redirect-based links.
- Run small team pilots inside organizations and measure support tickets, onboarding time, and doc discovery issues.
### ❓ Questions
- Does obsid.net log full query parameters, and how long are logs retained?
- How will multi-device setups (desktop vs. mobile) behave with these redirects across platforms?
- Can users self-host an equivalent redirect to avoid third-party dependency?
- What happens if Obsidian is not installed on the device that opens the link?
### 🔮 Future Research
- Explore standardizing a generic “local knowledge link” pattern for tools beyond Obsidian.
- Investigate offline-resilient variants that queue openings until a vault is reachable.
- Study security models for mapping external URLs to sensitive local resources.
- Integrate with identity and permission layers for team-shared vaults.
### 💡 Implications
- Practice: Easier cross-device note access could deepen adoption of Obsidian in developer and contributor workflows.
- Policy: Organizations may need clearer policies on referencing private repositories of knowledge in public or semi-public channels.
- Security: Redirectors must minimize data retention and exposure, especially where vault names or file paths are sensitive.
- Education: Training on local-first knowledge management should include safe, interoperable linking patterns.
- Funding: Shared redirect infrastructure may require sustainable hosting or community funding.
### 🧠 Learning Styles Assessment
- Reading level estimate: Roughly B2–C1 (upper intermediate to advanced), by Flesch-style heuristics (technical terms, complex sentences).
#### 👀 Visual learners
- Present: Clear conceptual contrast between `obsidian://` and HTTPS links (described verbally).
- Improve: Add diagrams of the redirect flow from chat → obsid.net → Obsidian vault.
#### 🔊 Aural learners
- Present: No explicit audio support.
- Improve: Provide a short audio/video walkthrough demonstrating tapping a link in WhatsApp into Obsidian.
#### 🗣️ Verbal learners
- Present: Concise, concrete explanations and examples of URL formats.
- Improve: Add analogies to more familiar patterns (e.g., URL shorteners) in plain language.
#### 🧩 Kinesthetic learners
- Present: Implied hands-on step (“convert one of your old links”).
- Improve: Provide a step-by-step checklist with copy-paste examples and test scenarios.
#### 🧠 Logical learners
- Present: Clear problem/solution framing and causal explanation (blocked schemes → redirect → success).
- Improve: Add a simple decision table for when to use obsid.net vs. other approaches.
#### 🧑🤝🧑 Social learners
- Present: Focus on use in conversations (chats, agents).
- Improve: Offer prompts for teams to design shared workflows around Obsidian and chat tools.
#### 🧘♀️ Solitary learners
- Present: Article suits independent experimentation with one’s own vault.
- Improve: Include reflection prompts about personal note-linking pain points.
#### 🌿 Naturalistic learners
- Present: No direct environmental framing.
- Improve: Use ecosystem analogies (e.g., local vs. cloud habitats for data) if helpful.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: Likely standard article markup with headings and links.
- Improve: Ensure descriptive link text (not just raw URLs) and correct language attributes.
#### Keyboard navigation
- Present: Standard web page behavior should suffice.
- Improve: Confirm tab order clarity and visible focus styles.
#### Contrast and readability
- Present: Depends on joost.blog theme; text likely high contrast.
- Improve: Validate contrast ratios and line height; avoid overly dense paragraphs.
#### Text resizing and reflow
- Present: Modern responsive design likely adequate.
- Improve: Test up to 200% zoom and ensure no horizontal scrolling for body text.
#### Media and captions
- Present: Primarily text; minimal media.
- Improve: If adding screenshots or diagrams, include alt text and captions.
#### Forms and interactions
- Present: None critical for this article.
- Improve: N/A.
#### Standards reference
- Map any gaps (if identified) to WCAG 2.2 AA criteria on contrast, reflow, and link purpose.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: Tooling-focused, culturally neutral content.
- Improve: Include examples from diverse work environments (e.g., non-English teams).
#### Inclusive language
- Present: Neutral, technical language; minimal jargon beyond tool names.
- Improve: Add a brief glossary for tools and terms (Obsidian, URL handler, agents).
#### Neurodiversity support
- Present: Short, focused article with clear topic.
- Improve: Add more headings and bullet lists to break up text; minimize context switching.
#### Representation
- Present: No people imagery; neutral.
- Improve: If adding visuals, show diverse users and contexts.
#### Psychological safety
- Present: Non-controversial, practical topic.
- Improve: Provide clear statements about privacy assumptions and limitations.
### ✅ Logical Validity
#### Strong reasoning
- Causal chain: custom URI schemes are blocked → links fail in chat → HTTPS redirect preserves functionality; this is straightforward and supported by common platform behavior.
- Practical inference: If agents emit HTTPS links instead of custom schemes, they will work in more environments; aligns with browser and app security models.
#### Fallacies
- None obvious; the article is descriptive and low on strong, generalized claims.
#### Tone of voice
- Tone: Practical, mildly enthusiastic, and conversational.
- Example: Encouraging readers to “give obsid.net a try” and wire it into agents.
### 🛡️ DARVO Analysis
- Deny: No denial or minimization of harm; the article addresses a usability gap.
- Attack: No attacks on other tools or users.
- Reverse victim/offender: Not applicable; the piece describes a technical workaround, not a conflict.
## 🎯 Conclusion
The article proposes obsid.net as a simple HTTPS redirect layer that makes `obsidian://` links usable in everyday chats and agent-human interactions. For Obsidian-heavy workflows—especially those involving AI agents—standardizing on `https://obsid.net/?vault=…&file=…` keeps links tappable across platforms while still opening notes in your local vault. Next steps: test converting existing links, integrate the pattern into your agents or scripts, and evaluate whether you need additional privacy or self-hosted options.
## 🧱 Refactor Appendix (append after 🎯 Conclusion)
### 📚 Literature Split Pad
- Purpose: Stage Konik CEE units that become per-source Literature notes.
- Split level: **H3**.
- Include verbatim quotes under 25 words and a [view highlight] link.
### [H1] 5–10-word present-tense claim
> [!quote] [Share Obsidian links that actually work everywhere](https://joost.blog/obsidian-agent-links/) by [[Joost de Valk]] via [[joost.blog]]. Published 2026-02-25. Accessed 2026-02-25.
> “The whole point of obsid.net is to make those notes shareable in agent-human conversations.”
Two lines: context and use. Cite data if relevant.
[view highlight](https://joost.blog/obsidian-agent-links/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [Share Obsidian links that actually work everywhere](https://joost.blog/obsidian-agent-links/)
> “It’s just a simple https://obsid.net/?vault=…&file=… link you can paste into WhatsApp, Slack, email, or any chat that refuses to run custom schemes.”
Two lines: context and use.
[view highlight](https://joost.blog/obsidian-agent-links/#H2) #xref ID:rw_[MISSING]
---
### 🔖 Atomic Split Pad (Zettel Candidates)
- Purpose: Promote reusable claims into Atomic notes.
- Split level: **H4**.
- Each item: one idea, present tense, specific, testable.
#### [Z1] HTTPS wrappers keep Obsidian links tappable
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Local-First-Knowledge]] [[Agent-Chat-Workflows]]
#### [Z2] Agents can safely share local note links
- Scope/condition in one line.
- Pointer to page/time or dataset.
- Links: [[Developer-Agents]] [[Documentation-Workflows]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).”
- Keep each line short and self-contained.
- [F1] Try converting existing `obsidian://` links to obsid.net for daily chats — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
- [F2] Add obsid.net URL generation to my agent tooling — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
- [F3] Investigate privacy and self-hosted alternatives to obsid.net — context/https://joost.blog/obsidian-agent-links/ #fleeting #inbox
---
## 🧰 Template Library (paste into Note Refactor → Refactored Note Template)
<!-- Copy ONE template at a time into the plugin before running each batch. -->
### 📝 Fleeting — Refactored Note Template (Konik-ready)
---
type: fleeting
status: inbox
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
process_by: {{date:YYYY-MM-DD}} # review within 24–48 hrs
source_title: [MISSING]
source_link:
author: [MISSING]
source_type: article|paper|video|podcast|thread
reading_stage: inspectional|analytical|syntopical
project:
tags: #fleeting #inbox
---
# 📝 Fleeting Note — {{title}}
## 🧠 One-liner (my words)
- State the single idea in one short sentence.
## 🧭 Context & cue
- Where did this arise? Page/timecode/speaker.
- Trigger: quote, data point, claim, or question.
## 🧪 Adler checks (quick)
- What is this about as a whole?
- What is said in detail, and how?
- Is it true? Evidence for or against?
- So what? Impact or next move.
## 🔎 Bias & reliability snapshot
- Possible bias or framing?
- What evidence would change my view?
## 🧩 Konik bridge
- Draft a claim header for promotion.
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{source_link}}) by [[{{author}}]]. Accessed {{date:YYYY-MM-DD}}.
> “Short quote under ~25 words.”
One line on why this matters.
[view highlight]({{source_link}}) #xref ID:rw_[MISSING]
## 🧰 Next moves (pick 1–2)
- [ ] Promote to *Literature* with citation.
- [ ] Draft *Atomic* claim from [H1].
- [ ] Park as testable question.
## ✅ Processing checklist
- [ ] Rewrote in my words.
- [ ] Decided: trash | keep | convert.
- [ ] Linked to at least one related note.
- [ ] Tagged and moved out of inbox.
---
### 📚 Literature — Refactored Note Template (Konik-ready)
---
type: literature
status: draft
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
adler_level: inspectional|analytical|syntopical
reading_stage: inspectional|analytical|syntopical
source_title: [MISSING]
author: [MISSING]
year:
publisher_or_journal:
edition_or_volume:
doi:
url:
accessed: {{date:YYYY-MM-DD}}
citekey:
project:
tags: #literature #reading
---
# 📚 Literature Note — {{title}}
## 🧰 Action Inbox
- [H1] Short action — context/{{url}} #articleseed
- [H2] Short action — context/{{url}} #xref
- [H3] Short action — context/{{url}} #share
## 🧭 Bib Capsule
- Title, author, year, venue, and link.
- One-line scope: what the work attempts.
## 🧠 Author’s Thesis (their words)
- Core claim briefly. Include page/timecode.
## 🧩 Key Arguments
- Argument A — method/evidence — page/time.
- Argument B — method/evidence — page/time.
- Argument C — method/evidence — page/time.
## 🧪 Evaluation (Adler)
- What is this about as a whole?
- How is it argued? Fairly and clearly?
- Is it true or plausible? Why?
- So what? Practical or theoretical impact.
## 🗒️ Notes (Konik CEE units)
### [H1] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] 5–10-word present-tense claim
> [!quote] [{{source_title}}]({{url}}) by [[{{author}}]] via [[{{publisher_or_journal}}]]. Published {{year}}. Accessed {{accessed}}.
> “Verbatim highlight under ~25 words.”
Two lines: context and use. Link to data if relevant.
[view highlight]({{url}}#H2) #xref ID:rw_[MISSING]
## 🔖 Zettel Candidates
#### [Z1] 5–10-word present-tense claim
- One-line context and page/time.
#### [Z2] 5–10-word present-tense claim
- One-line context and page/time.
## 🏷️ Tag Coverage
#articleseed: 0 • #xref: 0 • #share: 0 • #bmf: 0 • #addendum: 0
## ✅ Processing Checklist
- [ ] Thesis captured in my words.
- [ ] 1–3 Zettel candidates drafted.
- [ ] Action Inbox pruned to high-signal items.
- [ ] Cross-links added and filed.
---
### 🔖 Atomic (Zettel) — Refactored Note Template (Konik-ready)
---
type: atomic
id: {{date:YYYYMMDDHHmm}}-{{title}}
status: evergreen
created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
origin: reading|thinking|experiment
proof_state: conjecture|working|supported|refuted
source_literature: [[Source-Literature-Note]]
citekey:
project:
tags: #zettel #idea
---
# 🔖 {{title}} <!-- 5–10 words, present tense, specific -->
## 🧠 Claim
- One idea only. Clear and testable.
## 🧾 Evidence & Pointers (Konik)
- [H#] from [[{{source_literature}}]] — page/time — brief rationale.
- ID:rw_[MISSING] — link to highlight or dataset.
> [!quote] Evidence snippet (≤25 words) if essential.
> Cite page/time. Keep it minimal.
## 🔍 Scope & Conditions
- When this holds. Boundaries and exceptions.
## 🔗 Links
- Broader: [[Parent-Concept]]
- Narrower: [[Specific-Case]]
- Related: [[Parallel-Idea]]
## 🧪 Tests / Falsifiers
- One check that could disconfirm the claim.
- Simple study or observation plan.
## 🧰 Implications
- Practice, policy, or design moves in one line each.
## 🔙 Backlinks
- From: [[{{source_literature}}]] • Context line.
## ✅ Maintenance
- [ ] Links in and out.
- [ ] Title still precise?
- [ ] Proof state updated.
## Highlights
- Why care? Because in human + agent chats, the agent often is the one sharing notes to you. Codex, Claude, or any cron job can now output safe obsid.net URLs instead of raw obsidian:// URIs, and you can open them anywhere. obsid.net links also look like (no, *are*) normal HTTPS URLs, so they survive log archives, bookmarking, and every chat frontend you already use. ([View Highlight](https://read.readwise.io/read/01kjbc9j2q8vabwmdmgj5frbap))
- Tags: 👻 ai highlighted