The thing I always wondered regarding obsidian plugins is how they are able to offer them on iOS, given that iOS has rules against downloading code that alters functionality of the software.
The Future of Obsidian Plugins
121–130 of 186 posts
Re: The Future of Obsidian Plugins
#122Review is done by LLMs? How you guys decided to deal with prompt injection attacks?
It isn't. Doesn't involve AI. Read the post :)
Re: The Future of Obsidian Plugins
#123Obsidian CEO here. We've been working for nearly a year to launch this new Community site and review system. I'm very excited about this first version but there are many more improvements to come. I've tried to be exhaustive with the blog post, FAQs, and next steps on our roadmap, but I am sure I forgot some things, so feel free to ask! This has been an incredibly challenging project for a number of reasons. We're on…
Do you plan to integrate the new web interface into the app? I would like to see which plugins I've already installed in the new interface.
Thanks for the greatness!
Re: The Future of Obsidian Plugins
#124What I would like is that they made it easier to install plugins locally. Should really just be copy pasting into a folder. I would change it myself, were it not for the fact that Obsidian is proprietary software. Time someone builds a compatible clone.
Needs more competition in the space for sure.
Re: The Future of Obsidian Plugins
#125I don't use Obsidian, and my assumption when I saw the title was I guess they're gonna be limiting it to a small set of corporate-blessed plugins . I've come to expect that "The Future Of XYZ" titles from software companies means severely limiting XYZ or preparing XYZ for a shut down!
I was wondering at which point the enshittification would be revealed.
> the enshittification
A strong reason to stick to using Obsidian as just a Markdown editor and not get sucked into the plugin ecosystem at all. If your Obsidian vault is just a folder of Markdown files, you're ready to leave at a moment's notice.
If I ever go in on some plugin ecosystem, it'll be FOSS, non-commercial, and have been around long enough to drink. (Emacs?) Haven't felt the need; a Markdown vault for reference resources + pen & paper for ephemera suffices for me.
Re: The Future of Obsidian Plugins
#126No permissions system, nothing resolved. Plugins still have access to everything - full disk, network, etc. How does one even speak of security vulnerabilities when the security model of Obsidian plugins is just straight up "click here for RCE".
All I see is a spanking new interface that will accelerate the pace of plugin turnover, bringing forward the next inevitable security incident.
Re: The Future of Obsidian Plugins
#127Earlier quoted context omitted.
That would not have been accurate though.
For those that aren't aware, this is all meant to distract/confuse you in light of this story: https://cyber.netsecops.io/articles/obsidian-plugin-abused-i...
We've been working on the project for nearly a year, so no.
Re: The Future of Obsidian Plugins
#128No permissions system, nothing resolved. Plugins still have access to everything - full disk, network, etc. How does one even speak of security vulnerabilities when the security model of Obsidian plugins is just straight up "click here for RCE". All I see is a spanking new interface that will accelerate the pace of plugin turnover, bringing forward the next inevitable security incident.
It seems like you have not read the blog post.
Re: The Future of Obsidian Plugins
#129Earlier quoted context omitted.
For those that aren't aware, this is all meant to distract/confuse you in light of this story: https://cyber.netsecops.io/articles/obsidian-plugin-abused-i...
We've been working on the project for nearly a year, so no. https://github.com/obsidianmd/eslint-plugin/commits/
Just say "I think my users are stupid" and be done with it. The timing of your announcement is obviously not a coincidence. You are genuinely terrible at this.
Re: The Future of Obsidian Plugins
#130No permissions system, nothing resolved. Plugins still have access to everything - full disk, network, etc. How does one even speak of security vulnerabilities when the security model of Obsidian plugins is just straight up "click here for RCE". All I see is a spanking new interface that will accelerate the pace of plugin turnover, bringing forward the next inevitable security incident.
It seems like you have not read the blog post.
Just wanted to say a huge thankyou for being so patient in the forum; it's quite annoying that the comment section is a more a function of the title + personal opinions than a function of the blog content.
I love using obsidian, and thanks so much for all the work that you and the team have put in :)