obsidian-api VS docs

I really like that you commit to keep this stable and open.

Do you plan to make the TypeScript definition part of this new site?

https://github.com/obsidianmd/obsidian-api/blob/master/canva...

For me it's easier to read TS format.

The Canvas feature is a custom file format, but they published the format here: https://github.com/obsidianmd/obsidian-api/blob/master/canva...

If Obsidian goes under or you want to migrate at least your data isn't lost.

Obsidian is closed source so you won't be infringing their copyright by incorrectly getting/copying their code within your code. I don't believe they have any software patents (too small a company), and the canvas data format is available under MIT license (https://github.com/obsidianmd/obsidian-api/blob/master/canvas.d.ts). Even if you decided to reproduce their plugin APIs (so that existing Obsidian plugins could be reused with your software), you'd be fine per https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc. (but their API definition is under MIT license anyway: https://github.com/obsidianmd/obsidian-api/tree/master)

I would start with with the obsidian api docs and the obsidian plugin docs then feed it into a gpt document loader and ask gpt the same thing you asked here. Obsidian offers a couple different “talk to your notes” plugins using gpt (all you need is an open ai api key) if you’re looking for a streamlined “ai document loader” you could just copy and paste the info into a new note once you have the plugin installed.

In any event, there are no CLI flags to do that at the moment. The canvas format is very new, and not part of the standard markdown format. There is a public specification for it, but it's up to developers to make applications supporting it.

Canvas has been an open standard since its release.

As far as I know, any API that can be used by end users and plugin developers (as described in the previous post) is considered public. You can find the API repo here and definitions in this file.

The .canvas format is a simple JSON-based format that is designed to be easy to parse. We've already seen several plugins leverage this and hope to see even more tools outside of Obsidian. You can see the spec here.

Looks cool! I couldn’t tell from the homepage, but it looks like they support cross-device syncing [1]. The big gap left is the rich plugin environment that Obsidian has.

1: https://docs.logseq.com/#/page/how%20to%20sync%20your%20logs...

I've become a big fan of LogSeq for these reasons. In LogSeq, you have pages and trees of data (aka blocks[1]. All can be cross-referenced or embeded between each context. It's quite nice.

1: https://docs.logseq.com/#/page/the%20basics%20of%20block%20r...

https://github.com/logseq/docs > Code > local > Download zip

You clearly didn't use it much or maybe you didn't take a look at the documentation: https://docs.logseq.com

Official Docs Official Plugin Dev Doc

Would you be so kind and give an example of such a tagged block? I had a look at the documentation and only found https://docs.logseq.com/#/page/how%20to%20create%20pages%20i... that does not addresses blocks.

Also another use for logseq is that you can deploy your notes or some of them as static HTML. the documentation website above is an example. Its hosted on GitHub pages: https://github.com/logseq/docs

Yep. There's a plugin API, https://docs.logseq.com/#/page/Plugins, used by 180+ plugins. Logseq can also be scripted from the commandline in node.js with https://github.com/logseq/nbb-logseq#projects-using-nbb-logs.... There are examples for creating a github action, a CLI or creating custom web apps

Cmd-K to find any line in your notes and Cmd-shift-K to find any line in your page. Starting with 0.8.3 there is also a native find-in-page feature, https://docs.logseq.com/#/page/Find%20in%20page, which can search anything that is visible including results of queries