Hi guys,
just read the changelog for the newly released Obsidian version 1.9.12.
And I’m a little bit surprised.
If I read the changelog correctly, the Obsidian team disables two community plugins because they’re causing troubles with core components (presumably Bases).
Fair enough. I understand that some unnecessary bug reports have been filed. And that the user experience could be harmed.
Yet, does this really justify interacting with a users personal plugin config? For me this seems to be going a step too far.
Do I read this the wrong way?
What’s your take on this?
As I see it’s common practice to delist plugins from the main JSON list.
This is fine in my opinion.
Yet, it seems weird to me to built a new function just to disable two concrete plugin (versions).
Seems overly specific.
We normally only deprecate plugins that cause significant data loss, but in this case we have received an overwhelming amount of bug reports that we decided to deprecate these two specific plugin versions.
For Commander there is already an update available, and once you update the plugin will work again.
For the Image Toolkit plugin the update is still outstanding.
We are working on a new mechanism that should hopefully solve this problem in the long term, so that we don’t have to delist more plugins for UX issues.
2 Likes
Thanks @joethei for the explanation! I understand your points.
Best of luck to you and the team for solving the current plugin situation.
AI is really backfiring hard in this regard. I hope you’ll find a good mechanism to deal with the submission of new plugins and quality control of current ones.