Live data from Hacker News

The Future of Obsidian Plugins

obsidian.md

41–50 of 186 posts

Re: The Future of Obsidian Plugins

#41
post #13

For those not aware, it has basically been impossible to submit new plugins due to the manual review (and how easy/fun it is to write a plugin with AI). The developer community was becoming increasingly frustrated, and the team was burning out under the load. So congrats to the team! This relieves a huge scaling bottleneck. It has been really cool to see how y'all build and scale.

Got any cool plugins you recommend? I'm finally getting comfortable after switching from OneNote and getting sync set up.

"Ink" for drawing (big miss in the standard feature set IMO, the only one thing I missed coming from OneNote which is horrible in every other way compared to Obsidian).

"Self-Hosted Livesync" for syncing on your own server (I don't want my stuff on other people's computers even when encrypted)

"Copilot" for AI integration (I use two local ollama servers as you might have guessed from the above :) )

"Whisper" for text to speech/dictation (Yes I host that locally too)

"ReadItLater" for easy web clipping/archiving

Re: The Future of Obsidian Plugins

#42
post #32

I want to use Obsidian... but I won't as long as it's not open source. I know I can keep all my files as plain text, but that's not enough for me. Using a KB on a daily basis shapes my workflows and having to change that from one day to another (e.g., because maybe Obsidian changes in a way I don't like) is too much for me. I could already handle all my plain txt files using simply the file system, but of course I wo…

I know that most people aren’t into nvim, but I really love obsidian.nvim for this.

Beautiful searching and editing experience and all the KM features that I need, all on plain Markdown. I’ve been extremely happy since I set it up.

Re: The Future of Obsidian Plugins

#43
post #32

I want to use Obsidian... but I won't as long as it's not open source. I know I can keep all my files as plain text, but that's not enough for me. Using a KB on a daily basis shapes my workflows and having to change that from one day to another (e.g., because maybe Obsidian changes in a way I don't like) is too much for me. I could already handle all my plain txt files using simply the file system, but of course I wo…

> I want to use Obsidian... but I won't as long as it's not open source.

Sooo... don't use it?

There are plenty of open source alternatives, and I'm sure someone's going to mention org-mode.

Re: The Future of Obsidian Plugins

#45
post #32

I want to use Obsidian... but I won't as long as it's not open source. I know I can keep all my files as plain text, but that's not enough for me. Using a KB on a daily basis shapes my workflows and having to change that from one day to another (e.g., because maybe Obsidian changes in a way I don't like) is too much for me. I could already handle all my plain txt files using simply the file system, but of course I wo…

Trusted source > open-source As long as it's trusted, there is no lock-in, and the model supports maintaining the software, what do you have to lose?

"there is no lock-in" is a thing that's said a lot about Obsidian and, as an Obsidian fan, I feel like isn't totally true. Yes, Obsidian just stores markdown files, but it has unique syntaxes, especially if you're using plugins, that aren't transferable. So while I can get my files out, I still have to go through the annoying process of fixing them and getting it working in whatever new system I switch to when I leave. It's still far better than a lot of other proprietary tools, absolutely, but it's also not trivial to drop Obsidian if/when you stop using it

Re: The Future of Obsidian Plugins

#46
post #28

Very cool. Shame the website is dark mode only which only makes it harder to read for people with astigmatism.

But a very rare form of astigmatism I guess? Because I've had it for 30+ years and I can read it perfectly without any effort?

halation (bleeding of the text into the background) happens for all people with astigmatism with white text on dark background but severity will obviously differ depending on your personal environment.

But given that about 50% of people have some form of astigmatism dark mode default has been a horrid trend.

Re: The Future of Obsidian Plugins

#47
post #32

I want to use Obsidian... but I won't as long as it's not open source. I know I can keep all my files as plain text, but that's not enough for me. Using a KB on a daily basis shapes my workflows and having to change that from one day to another (e.g., because maybe Obsidian changes in a way I don't like) is too much for me. I could already handle all my plain txt files using simply the file system, but of course I wo…

Unless you have crazy custom files I feel like this is a non issue Obsidian is just rending markdown so any potential future app (or the influx of slop AI markdown editors/renderers) out there could do the job albeit worse than Obsidian.

Re: The Future of Obsidian Plugins

#49

Earlier quoted context omitted.

But a very rare form of astigmatism I guess? Because I've had it for 30+ years and I can read it perfectly without any effort?

halation (bleeding of the text into the background) happens for all people with astigmatism with white text on dark background but severity will obviously differ depending on your personal environment. But given that about 50% of people have some form of astigmatism dark mode default has been a horrid trend.

Ah maybe because I have always lights off, so it's dark surrounded by dark ^^

Re: The Future of Obsidian Plugins

#50
post #32

I want to use Obsidian... but I won't as long as it's not open source. I know I can keep all my files as plain text, but that's not enough for me. Using a KB on a daily basis shapes my workflows and having to change that from one day to another (e.g., because maybe Obsidian changes in a way I don't like) is too much for me. I could already handle all my plain txt files using simply the file system, but of course I wo…

Trusted source > open-source As long as it's trusted, there is no lock-in, and the model supports maintaining the software, what do you have to lose?

There are still free as in freedom software hardliner folks out there. The idea that every piece of revoked source code is an affront to computing rights might be less applicable in Obsidian's case since the files are still portable, and the system may be sufficiently extensible through custom plugins (you can load anything you want through the developer plugins option) that source code itself is not necessary. Though perhaps one might want to re-assure themselves that there is nothing 'malicious' happening in the software, that's only achievable with auditing it oneself and using reproducible builds. Perhaps the freedom to fork is also not as thoroughly infringed since the files are portable and reverse engineering is not impeded.
Post reply on HN