Live data from Hacker News

Obsidian – A knowledge base from a local folder of plain text Markdown files

obsidian.md

131–140 of 373 posts

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#131

Quoted post unavailable.

I’m slightly relieved reading this. I see markdown everywhere, I can’t stand it, and I wonder why people are so crazy about it. It’s nice to know I’m not alone.

Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#132

Quoted post unavailable.

I’m slightly relieved reading this. I see markdown everywhere, I can’t stand it, and I wonder why people are so crazy about it. It’s nice to know I’m not alone. Unfortunately I don’t think markdown is going anywhere. I think I see it far more than ever and there’s no sign of it slowing down.

Textile and LaTeX are better, anyway. At least it's not HTML or BBCode.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#133

Quoted post unavailable.

I could not disagree more. I'm very pleased that things such as markdown exist and are being widely used. All of the tools used by 'other professions' as you say, are in some nonsense proprietary format that works in their application and theirs alone. Even something as widespread as .docx is still a third-class citizen on other applications, due to Microsoft's monopoly on it.

Is Markdown perfect? No. I find it rather frustrating that there isn't a single definitive flavor, but it's easy to learn, easy to read and render, and can be used as a tool in just about anything. You can keep your 'real programs'.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#134

Quoted post unavailable.

Wow, I couldn't feel more differently about markdown. I'm not a programmer, but I welcome this useful non-proprietary format. I just wish I could get my entire small business to use a Wiki full of markdown files (which present very nicely with wikijs and other such software) instead of a bunch of folders full of MS Word files.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#136

Earlier quoted context omitted.

I just run the wiki in docker and take regular snapshots? I also find the requirement "have internet" is a good trade-off against the requirement "install client on every device".

How is docker easier for most people? How does docker even work with multiple devices? Mobiles? and how much storage does a docker-snapshot wastes?

snapshots aren't that big. A wiki server just runs on a single server? I thought it was pretty common among the HN population to have a cloud note solution. Syncing files seems more hassle than a one-time docker setup.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#138

Last I checked there was no good way to do quick capture of articles from mobile iOS to obsidian. Scenario — I come across an article on my iPhone, and I just want to dump title + URL (maybe even the text content) into obsidian. This is a must have for any note taking tool. Anyone have a good workflow for this, please share. Ideally an iOS shortcut.

I made a web clipper bookmarklet for Obsidian that works on mobile https://gist.github.com/kepano/90c05f162c37cf730abb8ff027987...

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#139

Quoted post unavailable.

There are a couple of key advantages to textual formats:

* They work easily with Gi

* They are understandable without a specialized program

I'm curious to what you'd suggest as an alternative to text (yaml, json, ini) configuration files.

Re: Obsidian – A knowledge base from a local folder of plain text Markdown files

#140

Quoted post unavailable.

Agreed on Markdown's limited expressiveness.

I think the reason for programmers' attachment to Markdown isn't just about being able to operate on it in a terminal. It's about the general interoperability of plaintext.

Terminal editing is one example, but even IDEs and non-terminal text editors also use plaintext. There's also the fact that version control tools are designed for line-based plaintext. Markdown is especially often used for documentation that gets checked in alongside code, so this is an important consideration.

I would be very interested to hear thoughts on good alternatives to Markdown for technical documentation, even if not plaintext-based.

Post reply on HN