Earlier quoted context omitted.
> Free Not really. The license says you are not allowed to take notes about work you get compensated for. So free only for 100% hobby projects. Working in a start-up I don't have big 100% hobby projects that would require a lot of note keeping. YMMV
It's not like there's a realistic way to enforce that license, so it's essentially free. Edit: typo
Show HN: Obsidian – A knowledge base that works on local Markdown files
361–370 of 501 posts
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#362Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#363Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#364Exactly what I’ve been looking for. Will there be extension support?
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#365Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#366Would be nice to see a live example, I can't tell from the website what this actually does or how it would be useful to me
Sorry but because it works on a local folder, online demo is unrealistic. I would recommend installing, opening an empty folder, and going to Settings - Help to grab our hel & demo folder to play around with it and get a feel.
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#367Closed source cryptography is dangerous, and should be avoided whenever possible.
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#368I will never again build any kind of workflow for my knowledge on top of anything that isn’t open source. 5y is a long time and 10y is an eternity for these sorts of products but its just a fraction of my working life. My own personal setup is a bunch of markdown files and it’s great, so I like that approach, but I’m very cautious about investing time for something so important in a product i don’t control.
We'll likely make a formal guarantee to open source in the case of us shutting down. Didn't realize that was a possibility, thanks for the suggestion!
It also allows people to read, audit, and trust the crypto code, which your model does not. For people like me, that’s a hard pass.
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#369Earlier quoted context omitted.
I disagree. $50 for note taking app only is expensive compared to something like Google Docs which does much more functionality and includes cloud storage. The product is applicable to anyone who needs a knowledge base so it’s $50/employee and that adds up quickly. While the developer is free to charge whatever they like, I don’t like the trend of these products priced based on people thinking $50 isn’t that much and…
Yeah. Photoshop is only $10/mo. Many IntelliJ IDEs are $12.50/mo and you get to keep them if you stop paying. Both of those are core revenue drivers for many of the employees who use them. $4/mo is quite expensive for a markdown editor IMO.
Imagine if the author of grep charged $5/month for the utility.
Re: Show HN: Obsidian – A knowledge base that works on local Markdown files
#370Maker here, excited to be on Hacker News. Obsidian is going into public beta today! (We're also on Product Hunt, come check us out!) We made Obsidian to be your long-term second brain and personal knowledge base. As you put in more notes and make more connections, the knowledge base gets more valuable, so we think it's important that you can 100% own your data and not rely on any cloud services. We believe you second…
I've been using various personal wikis for years, and this hits most of what I am looking for.
But, I'd like to offer some suggestions.
- It would be cool if you would consider some tweaks for how the text is rendered. It can still be Markdown compatible, but for example allow linebreaks to be interpreted as linebreaks. Text used for reference often has different needs than what is being exported to HTML.
- Git integration. I just use git for syncing my knowledge bases. It makes the most sense for my multiple devices, and it is very rare that I even have conflicts and can't automatically merge differences.
I actually have a script that lets me use Dropbox or another syncing provider to sync my working tree, separate from the repo itself, so that my history isn't polluted with excessive automated commits, but it is still tracked relative to where it was checked out, and resolved automatically. That way you can have the strengths of git without the drawbacks.
You may also want to check out git-annex/datalad. I combine it with my home grown Markdown wikis for embedding references to files in my wikis, keeping my git history just pure text. One of my goals is to bridge file management with text management.
I'd be happy to share any of this if you're interested. I've had plenty of free time recently to further develop it.