The case for incorporating key plugins into the core program so they are present by default

[ariehen]

See this topic:

Regularly incorporate the next most popular community plugins

Use case or problem The community has been very proactive in meeting the needs of Obsidian users with the community plugins. However, because community plugins are not as rigorously tested and certified by Obsidian to be functional and secure, many users constrain themselves to just the core plugins. Proposed solution The Obsidian development team would regularly pull the most popular community plugins into their own backlog, to reimplement as core plugins. Current workaround (optional) For us…

Regularly incorporate the next most popular community plugins

This has a lot of overlap with the discussion in this thread. Security of the plugins - #115 by obsequious I’d suggest reading through that thread to understand why this is likely not a feasible feature request. In that thread there are a lot of people coming up with different ways of asking the developers to take on the responsibility of the community plugin security. And the short answer is that isn’t going to happen. Plus the developers have their own priorities and roadmap. This is also ba…