Our great sponsors
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
siyuan
A privacy-first, self-hosted, fully open source personal knowledge management software, written in typescript and golang.
-
-
markdownload
A Firefox and Google Chrome extension to clip websites and download them into a readable markdown file.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Apparently that's for development, the deployed production version is using a separate database: https://github.com/penxio/penx/issues/20#issuecomment-186770...
> Not really. Obsidian has its shares of problems too, and most of them originate from using Markdown.
Aha. Which problems do you mean?
> Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content.
Joplin is using md to. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo.
This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me, and it never breaks anything in my simple md files.
> Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.
Aha. I don't think so. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!
> And gosh, Obsidian has really a huge amount of plugins for data-handling.
And gosh, this is a good thing!
> At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates.
Installing multiple task plugins shows that something is "broke" on the user side. It's not the fault of Markdown or Obsidian.
Just have a look on: https://github.com/ivan-lednev/obsidian-day-planner but you dont need a fancy task plugin like this, if you know your way around https://github.com/blacksmithgu/obsidian-dataview or https://github.com/obsidian-tasks-group/obsidian-tasks
Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser https://github.com/deathau/markdownload and nvim https://github.com/epwalsh/obsidian.nvim
> Not really. Obsidian has its shares of problems too, and most of them originate from using Markdown.
Aha. Which problems do you mean?
> Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content.
Joplin is using md to. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo.
This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me, and it never breaks anything in my simple md files.
> Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.
Aha. I don't think so. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!
> And gosh, Obsidian has really a huge amount of plugins for data-handling.
And gosh, this is a good thing!
> At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates.
Installing multiple task plugins shows that something is "broke" on the user side. It's not the fault of Markdown or Obsidian.
Just have a look on: https://github.com/ivan-lednev/obsidian-day-planner but you dont need a fancy task plugin like this, if you know your way around https://github.com/blacksmithgu/obsidian-dataview or https://github.com/obsidian-tasks-group/obsidian-tasks
Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser https://github.com/deathau/markdownload and nvim https://github.com/epwalsh/obsidian.nvim
Fyi, if you are ever looking for a fun project you might be able to implement this. The vscode editor source is available as a library https://microsoft.github.io/monaco-editor/
FWIW, I exported all my Evernote notebooks just recently from my old free account. Used https://github.com/akosbalasko/yarle to convert them to Markdown. It also has support for various PKB formats, like Obsidian. Hope that helps!
+1 and curious, too
I would go further than that also. It directly mirrors https://anytype.io/ but without the desktop or mobile clients to actually store the workspace on your device.
Thanks for the pointer!
https://github.com/vrtmrz/obsidian-livesync: self-hostable sync via CouchDB, MIT license, supports the visual conflict resolver and end-to-end encryption.
You should have a look at Foam: https://github.com/foambubble/foam
Try SiYuan Note. It's free and open source local-first mix of Notion and Obsidian.
https://github.com/siyuan-note/siyuan
> Not really. Obsidian has its shares of problems too, and most of them originate from using Markdown.
Aha. Which problems do you mean?
> Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content.
Joplin is using md to. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo.
This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me, and it never breaks anything in my simple md files.
> Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.
Aha. I don't think so. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!
> And gosh, Obsidian has really a huge amount of plugins for data-handling.
And gosh, this is a good thing!
> At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates.
Installing multiple task plugins shows that something is "broke" on the user side. It's not the fault of Markdown or Obsidian.
Just have a look on: https://github.com/ivan-lednev/obsidian-day-planner but you dont need a fancy task plugin like this, if you know your way around https://github.com/blacksmithgu/obsidian-dataview or https://github.com/obsidian-tasks-group/obsidian-tasks
Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser https://github.com/deathau/markdownload and nvim https://github.com/epwalsh/obsidian.nvim
> Not really. Obsidian has its shares of problems too, and most of them originate from using Markdown.
Aha. Which problems do you mean?
> Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content.
Joplin is using md to. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo.
This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me, and it never breaks anything in my simple md files.
> Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.
Aha. I don't think so. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!
> And gosh, Obsidian has really a huge amount of plugins for data-handling.
And gosh, this is a good thing!
> At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates.
Installing multiple task plugins shows that something is "broke" on the user side. It's not the fault of Markdown or Obsidian.
Just have a look on: https://github.com/ivan-lednev/obsidian-day-planner but you dont need a fancy task plugin like this, if you know your way around https://github.com/blacksmithgu/obsidian-dataview or https://github.com/obsidian-tasks-group/obsidian-tasks
Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser https://github.com/deathau/markdownload and nvim https://github.com/epwalsh/obsidian.nvim
> Not really. Obsidian has its shares of problems too, and most of them originate from using Markdown.
Aha. Which problems do you mean?
> Markdown is a freeform text-format, and works very well for writing text, but it really sucks for data and structured content.
Joplin is using md to. And if Joplin does a good job on "data" and "structured content" (whatever you mean by that) by separating that in their DB, it's a big NO for me since it's a closed silo.
This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me, and it never breaks anything in my simple md files.
> Most plugins and features in that area are very brittle and overspecialized, working only well enough in their specific use case.
Aha. I don't think so. Which authority says that? And even if It's like that, my markdown files would survive everything, since they are a) in git. https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!
> And gosh, Obsidian has really a huge amount of plugins for data-handling.
And gosh, this is a good thing!
> At some point, it was so bad that there were multiple competing task-plugins which broke each other just because they had different formatting for dates.
Installing multiple task plugins shows that something is "broke" on the user side. It's not the fault of Markdown or Obsidian.
Just have a look on: https://github.com/ivan-lednev/obsidian-day-planner but you dont need a fancy task plugin like this, if you know your way around https://github.com/blacksmithgu/obsidian-dataview or https://github.com/obsidian-tasks-group/obsidian-tasks
Since the Ecosystem around Obsidian and pure Markdown, most of the time I stay in my browser https://github.com/deathau/markdownload and nvim https://github.com/epwalsh/obsidian.nvim
Just curious, any reason you're using TMarkor instead of Markor? (https://github.com/gsantner/markor/ , https://play.google.com/store/apps/details?id=net.gsantner.m...)
Only asking since this was also the editor I ended up settling on in Android, but it seems like TMarkor is just a repackaging of Markor without any references to its forked(?) source.
My requirement was that the repo had to be open source so that I could audit the repo and compile the APK from source, as well as potentially fork it for personal modifications if needed.