Remix.run Logo
obsidianbases1 4 hours ago

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?

presbyterian 3 hours ago | parent | next [-]

"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

joemi an hour ago | parent [-]

Doesn't seem remotely fair to consider lock-in caused by plugins to be an Obsidian lock-in. If the plugin is storing data in such a way that it's not usable in a tool other than Obsidian, that's 100% the plugin's fault, not Obsidian's no matter which way you look at it.

Also, more generally, any software that has unique features will require "the annoying process of fixing them and getting it working in whatever new system I switch to when I leave", whether it's open source or not. So you're not actually looking for open source, you're just looking for something with perfect feature parity to another program.

sprinkly-dust 3 hours ago | parent | prev | next [-]

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.

kid64 19 minutes ago | parent | prev | next [-]

In what universe is it trusted? This blog post is an admission that they've been lying to their userbase about their review process for years, with updates receiving no review whatsoever. Enjoy your mass exfiltration.

doginasuit 3 hours ago | parent | prev [-]

I don't think it makes any sense given the history of tech companies to count any of them as a trusted source. Open source doesn't ask for your trust, and it is the only way to get off on the right foot.

kepano 2 hours ago | parent | next [-]

Speaking as someone who spends most of his time making open-source software, open source still requires trust. Almost all Obsidian plugins are open source, yet the reason for this new review system is that people don't have the time or ability to vet every line of code of every piece of software. Open source software is only as reliable as the maintenance infrastructure around it. It makes promises that can't be guaranteed about its dependencies, its maintainers, the formats it uses, etc.

See also: https://stephango.com/self-guarantee

joemi an hour ago | parent | prev [-]

> Open source doesn't ask for your trust

And yet, I'd wager my life savings that almost no one using open source software actually verifies that it's not malicious in a different way than one would closed source software (ie. reputation), and instead almost everyone just trusts it.