On a side note, I find it interesting that a few recent projects are going for the Open Knowledge name. The Open Knowledge Foundation (https://okfn.org) is one of the first/largest proponents of the open data movement (think of it as a Free Software Foundation but for data, not software). They started in 2004 and developed many of the open data licenses and widely used infrastructure tools like CKAN (an open data portal platform).
1. Name collison happenstance. We'd locked in the npm package and domains prior to their announcement.
2. Our templates are Open Knowledge Format compliant and we have an explicit quickstart around making an OKF knowledge base. You can think of OKF as a format/standard for the content, and OpenKnowledge (our app) as an IDE/editor for any type of markdown based content.
Sweet, let me know the experience, we're actively thinking about how to make OKF KBs editing a good experience. E.g. a linter or other conformant mode.
Fully local, but can't integrate with any local LLM?
I do think a fully OSS Obsidian-like that syncs natively is an impressive accomplishment, though the usefulness of this is limited with OSX being the only supported platform. If an Android app is in the works I'll definitely follow the project!
Personally I just want to see more support for local LLMs. I haven't been doing much coding lately but am interested in setting up Qwen 3.6 if I can obtain the hardware
Sounds cool. How do agents know what else is going on in the doc? They have an embedded browser and they do like mutation observer type stuff? Or does the integration do polling?
Looking into Slite now to check. With OpenKnowledge, the content is just markdown files on-disk, so there shouldn't be anything exclusionary about it. Not sure how/if Slite handles markdown files. Will take a look.
Since Obsidian is just markdown, you can just open an Obsidian vault with OpenKnowledge. We made it so that most Obsidian syntax is supported, like wikilinks.
For Notion, we don't have a migration tool, but you can try the export to markdown approach.
Recommend trying it to get a feel, and if are looking to migrate and facing friction let me know details.
Congratulations on the launch. It looks neat!
On a side note, I find it interesting that a few recent projects are going for the Open Knowledge name. The Open Knowledge Foundation (https://okfn.org) is one of the first/largest proponents of the open data movement (think of it as a Free Software Foundation but for data, not software). They started in 2004 and developed many of the open data licenses and widely used infrastructure tools like CKAN (an open data portal platform).
Nothing to add, just found it interesting.
Disclaimer: I worked there for a few years.
Is this following the Open Knowledge Format proposed by Google earlier this month or just a name collision?
https://cloud.google.com/blog/products/data-analytics/how-th...
Two bits:
1. Name collison happenstance. We'd locked in the npm package and domains prior to their announcement.
2. Our templates are Open Knowledge Format compliant and we have an explicit quickstart around making an OKF knowledge base. You can think of OKF as a format/standard for the content, and OpenKnowledge (our app) as an IDE/editor for any type of markdown based content.
Neat, I’ve created a couple OKF based knowledge bases, this looks like a nice way to work with them.
https://github.com/jacquescorbytuech/crm-open-knowledge-wiki
https://github.com/jacquescorbytuech/running-knowledge-base
Sweet, let me know the experience, we're actively thinking about how to make OKF KBs editing a good experience. E.g. a linter or other conformant mode.
Fully local, but can't integrate with any local LLM?
I do think a fully OSS Obsidian-like that syncs natively is an impressive accomplishment, though the usefulness of this is limited with OSX being the only supported platform. If an Android app is in the works I'll definitely follow the project!
Got it. MCP Server and CLI is agent-agnostic, so should work with local models/harnesses, but we'll look into more explicit docs around this.
What IDE or harness do you use? We'll take a look.
Personally I just want to see more support for local LLMs. I haven't been doing much coding lately but am interested in setting up Qwen 3.6 if I can obtain the hardware
Sounds cool. How do agents know what else is going on in the doc? They have an embedded browser and they do like mutation observer type stuff? Or does the integration do polling?
Right now you'd simply prompt it. Working on more direct integration. Turns out they don't make event based back and forth easy.
I'm a sucker for pretty UIs. I already have a company-mandated knowledge base tool, Slite, can they be used together?
Looking into Slite now to check. With OpenKnowledge, the content is just markdown files on-disk, so there shouldn't be anything exclusionary about it. Not sure how/if Slite handles markdown files. Will take a look.
tl;dr: Slite supports import/export Markdown files, so not a native "interop".
Links: https://slite.slite.page/p/5XOO7_tII0D87T/Importing-Files, https://slite.slite.page/p/PxKfPvLrLHj07O/Exporting-Your-Doc...
Recommend trying it for some personal notes/specs/etc. -- can be used independently.
macos only? shame.
CLI + Web viewer are available for Linux and Windows. We tested it and works pretty well.
yea pass..
Is there a migration path from Obsidian or Notion? Switching costs are usually what keeps people locked in.
Since Obsidian is just markdown, you can just open an Obsidian vault with OpenKnowledge. We made it so that most Obsidian syntax is supported, like wikilinks.
For Notion, we don't have a migration tool, but you can try the export to markdown approach.
Recommend trying it to get a feel, and if are looking to migrate and facing friction let me know details.