Live data from Hacker News

Ditching Obsidian and building my own

amberwilliams.io

311–320 of 570 posts

Re: Ditching Obsidian and building my own

#311

Wait. Sync is “free” if you want to use some other service other than Obsidian’s. I pay for Obsidian sync partially for slightly more convenience (fewer non-integrated points of failure) and also to support the app itself. I’d gladly pay $1000 over a decade for a crucial tool. If the concern is open source and true longevity, I get it, you don’t get that here. But cost for value? Holy shit. $1000 over a decade is abs…

That’s common thought process: “tool that I use more than 10 times a day to amplify my knowledge? $10 a month? Eye watering!”.

Oh well, time to grab that Uber eats for $20 third time this week.

Re: Ditching Obsidian and building my own

#312
post #47

Earlier quoted context omitted.

What about git makes you uncomfortable? I saw that you didn’t want to use a 3rd party provider, but why not stick a git repo on your VPS (which you are trusting with your data today) and use that to coordinate syncs between your client devices?

Made a comment in the thread explaining this https://news.ycombinator.com/item?id=44023090 I expect my PKMS to evolve and wouldn't rule out a self-hosted Git server if I find it's a better option long term.

Thanks for the reply. I do agree with sibling comment from tasuki that I think you’re missing the simpler solution of plain git repos to solve “owning your own data in a future-proof manner”.

If you’re not trying to coordinate work among multiple people, and aren’t trying to enforce a single source of truth with code, you don’t _need_ “git server” software. You just need a git repository (folder & file structure) in a location that you consider to be your source of truth.

I’m not trying to convince you to change it now, especially if you’re happy with what you have, but I would suggest reading some (or all) of https://git-scm.com/book/en/v2

I think the first ~4 subsections of chapter 4 cover what I & tasuki were suggesting could be sufficient for you. If you’re the type of engineer to read through the code of your data storage layer, I think you’d find Chapter 10 (Git Internals) interesting, because it can demystify git. I enjoyed the whole book.

As with any engineering project, I see lots of questions about your choices, and I applaud you for sticking around. I would make very different decisions than you, based on your stated priorities, but that’s okay.

Re: Ditching Obsidian and building my own

#313
post #3

Good article but as a heavy user of Obsidian (and previously Evernote), I would offer some counterpoints: > After some mental gymnastics weighing if I should continue with Obsidian, I found solace when asking myself "Can I see myself using this in 20 years?". I couldn't. The thought of cyclically migrating notes from one PKMS to another every 5 years, as I had done from Evernote to Notion to Obsidian, made me feel ti…

Again, a little bit odd considering that the author is technically savvy enough to write an entire PKMS but didn't seem to consider that you can just check your markdown notes into a git repository and sync with the native android/iOS Obsidian app on a mobile device.

Also, Obsidian supports free iCloud sync if you are a Mac and iOS user. I know that's only a subset of users, but a nice option to get Obsidian to sync on the phone if you are in the Apple ecosystem.

Also, they have a cheaper Sync plan now that is $4 per month.

I can't really be bothered that Sync would cost up to 1000 in ten years. If you use Obsidian daily, it had an immensive value and it's cheaper than most services out there.

Re: Ditching Obsidian and building my own

#314
post #301

Earlier quoted context omitted.

NAT busting, and no key management. What extra dependencies does Tailscale have?

Well, the dependency on Tailscale's servers, for one. You're getting that NAT-busting because Tailscale is running servers to handle that for you, and you're getting around key management by having them manage your keys and overlay their own auth layer for you.

You can always run Headscale: https://tailscale.com/opensource#encouraging-headscale

> Headscale is a re-implemented version of the Tailscale coordination server, developed independently and completely separate from Tailscale. Headscale is a project that complements Tailscale — with its own independent community of users and developers. Tailscale does not set Headscale’s product direction or manage the community, and neither prohibits nor requires employees from contributing to Headscale.

Re: Ditching Obsidian and building my own

#315
post #6

> Since my PKMS is hosted online to manage notes across devices, I have multiple layers of security to ensure my notes are kept private. {Screenshot of a login form} The biggest life hack I can recommend for a self hoster is to set up a VPN on your local network and then just never expose your services on the public internet unless you're specifically trying to serve people outside your own household. Before I did th…

Even better, set up Tailscale. It's far easier to set up, is much more reliable (e.g. when devices are behind firewalls), and uses direct (encrypted) connections when possible. You can get it to do what you want with just a few clicks. Things like exposing a IoT VLAN on your Tailnet or setting up an exit node to tunnel all internet traffic through your home are super easy. You can even share specific devices with fri…

Unraid added native Tailscale support in 7.0, now you can just add an "app" (a docker container) and tick a checkbox and it'll appear in your tailnet directly.

Re: Ditching Obsidian and building my own

#316
post #205
post #183

Earlier quoted context omitted.

True, but the format is still text. In a "catastrophe", you can always just a) ignore these, or b) write custom code to process them (e.g. port the plugin to VSCode or whatever). Still far better than a proprietary format.

A proprietary format with an export function allows you the same inconvenience of having to write code for processing.

Not true for a variety of reasons:

1. You're relying on the external service to continue providing the export functionality, or else doing regular backups.

2. The format of the exports might be proprietary, so it might be orders of magnitude more difficult to parse.

3. The export might not contain all the data.

4. Even if the export isn't to a proprietary format, it might be to a format that's much harder to parse than Markdown. Markdown is not only a standard, it's fairly readable even without any parsing, as opposed to, say, exporting in HTML. Losing some functionality (often minor, depending on what you use Obsidian for) is better than losing more or all functionality.

Re: Ditching Obsidian and building my own

#317
post #231
post #3

Good article but as a heavy user of Obsidian (and previously Evernote), I would offer some counterpoints: > After some mental gymnastics weighing if I should continue with Obsidian, I found solace when asking myself "Can I see myself using this in 20 years?". I couldn't. The thought of cyclically migrating notes from one PKMS to another every 5 years, as I had done from Evernote to Notion to Obsidian, made me feel ti…

> Again, a little bit odd considering that the author is technically savvy enough to write an entire PKMS but didn't seem to consider that you can just check your markdown notes into a git repository and sync with the native android/iOS Obsidian app on a mobile device. Even simpler, I have mine in a Dropbox folder. Felt very strange for _this_ to be the straw that broke the camel's back for the author. Nonetheless, v…

Fun fact: Dropbox doesn’t support emoji in file names ( or at least, didn’t last time I checked. )

Deal breaker for me - adding iconography to file and folder names can be a natural, zesty enterprise.

Re: Ditching Obsidian and building my own

#318
post #3

Good article but as a heavy user of Obsidian (and previously Evernote), I would offer some counterpoints: > After some mental gymnastics weighing if I should continue with Obsidian, I found solace when asking myself "Can I see myself using this in 20 years?". I couldn't. The thought of cyclically migrating notes from one PKMS to another every 5 years, as I had done from Evernote to Notion to Obsidian, made me feel ti…

Big obsidian fan, but I will say: notes being “just markdown” is not entirely true depending on how you use obsidian. If you are a plug-in heavy user, and those plugins introduce new syntax and lots of JavaScript functionality, you are accumulating a bespoke custom syntax that only works on your copy of obsidian with your set of plugins. Obsidian and those plugins are still free and are a huge benefit, but just somet…

I've thought about this and I think Templater and Dataview are the two plugins I'd miss if Obsidian was sold to a VC tomorrow and enshittified.

And I'm pretty sure both will be forked and modified to run independently of Obsidian within a week of the theoretical enshittification.

Re: Ditching Obsidian and building my own

#319
post #3

Good article but as a heavy user of Obsidian (and previously Evernote), I would offer some counterpoints: > After some mental gymnastics weighing if I should continue with Obsidian, I found solace when asking myself "Can I see myself using this in 20 years?". I couldn't. The thought of cyclically migrating notes from one PKMS to another every 5 years, as I had done from Evernote to Notion to Obsidian, made me feel ti…

Again, a little bit odd considering that the author is technically savvy enough to write an entire PKMS but didn't seem to consider that you can just check your markdown notes into a git repository and sync with the native android/iOS Obsidian app on a mobile device. Also, Obsidian supports free iCloud sync if you are a Mac and iOS user. I know that's only a subset of users, but a nice option to get Obsidian to sync…

To add to your last point - 10 years is a very long time frame. Any recurring cost grows to eye-watering levels if the time interval is huge enough. In 10 years, a lot can happen in the space and you are not locked in with obsidian - if the next better thing comes along in 3 years, you can easily migrate.

Re: Ditching Obsidian and building my own

#320
post #5

I really don't want to critisize OP since building stuff for yourself is always a good mentality. But lets be realistic, 1000$ over 10 years is nothing. It will always cost more if you consider your own time for maintenance long term. Obsidian is one of the most consumer friendly business for note taking out of there, they are not VC so the Evernote comparison is unwarranted IMO.

> But lets be realistic, 1000$ over 10 years is nothing Where is the limit ? While $100/year maybe doesn't sound like much, it's hardly the only subscription service you have, and they all add up, from your mail provider, office suite, cloud storage, streaming services, phone bills, internet service, etc. Personally I find $100/year to edit notes on my phone to be a bit much, but then again, I just use iOS Notes. I a…

Yeah I just wanted to chime in here on what i see as a world view problem that might need to be updated with the times. I see your point about everything being subscription based.

There are definitely software out there that do not deserve to be subscription based. But there are some developers that I think should be supported on a regular basis. Especially obsidian because they develop one product and continually work on it to make it better. IMHO they deserve the money.

On side note I wish there was a way for it to be open source, and the team's reasons for not supporting open source seems a little iffy. They could still make money of of Obsidain Sync or other features that does not need to be part of a Open Source Release. Commercialism of a project this important worries me because people that depend on it can be easy side-lined if the team decides to sell out. Look what happened to the Atom editor. Microsoft brought it then killed it. I know with Obsidian you can walk away from it and thats good, but I always worry about commercial domination of a market causing limited choice.

I know your point was about subscriptions, and I guess I am saying im more supportive of that model, based on the times we are in, for developers that have genuine passion for a project that they want to continue developing.

Heck I know am realizing I need to support open source projects with regular donations because I want them to thrive long term

Post reply on HN