Hacker News Reader

Comment by not_your_mentat | Hacker News Reader

This looks really neat!

I'd be interested in giving it a try, but doing so would replace existing tools and workflow. As a user, I'm unwilling to do this is I can't both own my data and application hosting.

If Nino doesn't pan out and the product gets shut down, how do I continue to access my now (trigger warning, words used to describe as I understand, not critique) tightly coupled proprietary data? Can I self host? Is source code available? Are document formats open? How do I not get screwed as an enthusiastic adopter in the unhappy case that things don't work out? If I put my data in and the product isn't working for me, how do I get my data out?

View on HN

One great solution for that would be the approach many advanced Markdown editors like Obsidian have: the documents remain usable. You might lose some benefits (the integration between documents in a graph-like structure) that are specific to the tool. Still, your work is preserved in a universal format that anyone can leverage.

Most elements of Nano have widely accepted standards, presumably easy to integrate, so that guarantee should be doable.

It's not a universal format since a lot of data is for only for Obsidian plugins that can work work it, and it isn't universally extensible, so not suitable for proper tools this aims to be

Thanks. I think the concern about software provider shutting down is valid. Heck, I still remember being pissed when Google deprecated two products I used within a month (a few months back).

Self-hosting might be too complex to setup, but do you think single tenant offering helps? I don't know if it makes sense for individuals tho.

In addition to HTML & CSV, there is an option to export JSON, which supports more formats. In a way, it is an open format (.json) but I'll have to add relevant documentation. PDF support will also come at one point.

Self-hosting is key for us as well. Companies working with sensitive data really value "on-device" / "on-premises" architecture, which it looks like you're close to nailing.

Check out Bitwarden and Gitlab's self-hosting approaches, and congrats on the launch. I'm excited to try it.

And regarding self-hosting complexity, start with a "docker-compose up" example and iterate from there.

Reply on news.ycombinator.com