2,486 karma · joined May 9, 2012
https://obsidian.md
After much internal debate we chose the JSON format. We stay committed to keep it as open and easy to work with as possible. Plugin developers are already parsing and modifying the JSON file to programmatically change a Canvas view, and I think that's a fantastic start!
We used to use d3-force for force simulation, but then we rewrote it in wasm ourselves for performance.
The new editor in Obsidian was made possible by CodeMirror 6, and it has been powering both the Live Preview mode (like Typora) and the source mode in Obsidian ever since.
It can be a bit overwhelming to get into first, but as we experimented more with it, we found it to be extremely extensible and powerful. It's also highly performant for large documents. Another major reason we chose CM 6 is that it's also one of the only code editors that work decently on mobile.
While developing the new editor, Marijn was also amazingly responsive in investigating and fixing all the big and little things we ran into, even relatively niche issues like IME input bugs.
If you find CM 6 useful, consider what you can to support the project! Funding link is here: https://marijnhaverbeke.nl/fund/
File Provider is something we'll attempt to implement sometimes in the future to support other sync providers.
More info available at https://help.obsidian.md/Obsidian/iOS+app#Sync
Obsidian is a personal knowledge management app that works on top of a local folder of Markdown files [0]. Because "local" often means your computer, for the longest time, it has been a pain to access these notes on the go.
Our original plan was to build fully native mobile apps. Instead, we decided to build hybrid web apps. Hybrid web apps gets a lot of hate, and for good reason. There's heavy performance penalty for running JavaScript. Animations are often janky. A lot of native capabilities are restricted.
We know everyone's favorite argument for using the web stack. "We're a small team, and it's just not possible to....". Sure, we're also just two developers, but that excuse gets old.
We see it in a different way. We leverage hybrid web apps not as a shortcut, rather, we use it to put power in the hands of our users. This has always been a key principle driving Obsidian's development.
Obsidian is one of the few apps out there that lets users customize every aspect of the app. Themes and CSS snippets let users completely change the interface. Plugins [1] let users augment the GUI [2], run macros [3], build databases [4], synchronize with other apps [5], and much more.
It's unprecedented for users to have access to this kind of power on their mobile devices.
Now, it's reality, thanks to the web stack. Get it at https://obsidian.md/mobile
[0]: https://obsidian.md [1]: https://obsidian.md/plugins [2]: https://github.com/liamcain/obsidian-calendar-plugin [3]: https://github.com/SilentVoid13/Templater [4]: https://github.com/blacksmithgu/obsidian-dataview [5]: https://github.com/renehernandez/obsidian-readwise
---------
We have a vibrant community of passionate users: lawyers, database engineers, dungeon masters, medical students, CEOs and CTOs under their alternate identity. You can find them on Discord and our forum at https://obsidian.md/community
We're also launching on Product Hunt: https://www.producthunt.com/posts/obsidian-for-mobile
I think you would really enjoy our active discord community where a lot of people share and discuss their use cases and specific workflows. https://obsidian.md/community
Is it not working for you?
Ideally the help docs can be opened as its own vault and can be a nice testing ground for a new user to play around with the functionality.
If you don't trust us, technically you can also use firewall rules to block internet access (or monitor network and see what Obsidian is doing).
Would you join our community to give us a chance to debug the issue? https://obsidian.md/community
We're still currently in beta so we'd really appreciate all the help we can get to polish any hiccups in the app.
As for the editing experience, we're only about 3 months in so there's a lot of catching up to do, and Typora-level editing experience is something we're shooting for.
Markdown has definition lists that can serve as front and back of the cards (https://www.markdownguide.org/extended-syntax/#definition-li...), not as advanced as Anki but should suffice in most cases.
If I understand correctly, licenses are usually written more strictly for legal purposes, but in my opinion your use case sounds like it should belong to personal use.
If anyone has pointers for us to make the license text more clear, please let me know!
Our community made this: https://github.com/deathau/markdown-clipper