Recently went through my plug-ins list and found out one of them was de-listed and no longer functional. I had it running this entire time, even though Obsidian took over its functionality as a native feature. Having deprecated plug-ins like this is an unnecessary use of resources and can lead to an unnecessary degradation in performance within obsidian. Being able to tell if a plug-in has been de-listed from within the community plug-ins list would be beneficial during re-factoring of my vault.
2 Likes
not informed about obsidian-gallery plugin being removed through dev account deletion. this led to me having problems to find the new version (which is not in the plugin gallery), but i remembered it existed.
i dont know why such plugins even get removed from the “installed only” gallery since for themes it doesn’t do that, they keep an empty field with no image and just the base text data, and no readme file. it should be the same way with plugins.
example with a deleted theme. for plugins it just removes that entirely.
That theme removal experience could be improved too. I’ll add it to the post.
How should I use these lists?
Consider this:
community-plugins-removed.jsoncontains a reference to a plugin with the ID"duplicate-line", with the reason: “Developer banned from GitHub.”community-plugins.jsonalso contains a plugin with the ID"duplicate-line", which looks fine (msztolcman/obsidian-duplicate-line).
Maybe the ID in community-plugins-removed.json refers to a previously removed plugin with the same name, and a new plugin reused the ID without knowing it had been removed before.
This causes confusion.
Oh, that’s unfortunate.
The reason why that file exists in the first place is to make sure that there are no duplicates (checked automatically), but that new plugin was added before that file was added, so it slipped by.
Not sure of a good way to fix this, since id can only be changed with side effects (no further updates for prior users)