Add more default plugins

[laurent22]

Here's a list of default plugins we could add:

• Favourite
• Note List Preview
• Note graph (to be confirmed - if one that's good enough exists)

[tomasz1986]

Is adding a large number of default plugins really desirable? What I mean is that each plugin a) increases Joplin's RAM usage (which is already high due to Electron), and b) can be detrimental to security. Of course, default plugins can be disabled (but not removed) by the user, but they still come enabled and running by default. The user may not even be aware of the fact that they have been added and are active in the background.

[accesswatch]

I think there should be a way of removing plugins that are not required by users that ship as a default. Is this on the roadmap? From: Laurent Cozic ***@***.***> Sent: Tuesday, February 11, 2025 9:00 AM To: laurent22/joplin ***@***.***> Cc: Subscribed ***@***.***> Subject: [EXT] [laurent22/joplin] Add more default plugins (Issue #11825) External Email

…

________________________________ Here's a list of default plugins we could add: * Favourite * Note List Preview * Note graph (to be confirmed - if one that's good enough exists) - Reply to this email directly, view it on GitHub<#11825>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQ3F4QWKJ2C4IOQXAUMLVT32PINAVAVCNFSM6AAAAABW5NDN5KVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA2DKOBQGUZDCOA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[laurent22]

All default plugins can be disabled. We are considering adding some more, those that seem important, because often users don't know about these plugins

[accesswatch]

I understand but if it isn't a feature that the plugin provides can we not allow it to be removed from the product by users? From: Laurent Cozic ***@***.***> Sent: Tuesday, February 11, 2025 10:38 AM To: laurent22/joplin ***@***.***> Cc: Bishop, Jeff - (jeffbis) ***@***.***>; Comment ***@***.***> Subject: [EXT] Re: [laurent22/joplin] Add more default plugins (Issue #11825) External Email

…

________________________________ All default plugins can be disabled. We are considering adding some more, those that seem important, because often users don't know about these plugins - Reply to this email directly, view it on GitHub<#11825 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQ3F4QTTDSO75BI2WVVNAK32PIYPTAVCNFSM6AAAAABW5NDN5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJRGU2TSNJUGA>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[laurent22]

No there won't be this option. Most plugins take 1 or 2MB on drive so there's not really a case for the extra complexity just to save 2 MB.

[tomasz1986]

Is there a possibility that they (or at least some of them) come disabled by default? For example, it makes perfect sense for the Backup plugin to come enabled for all users, but the rest of these are used on a more case-by-case basis, i.e. not essential enough to be running in the background and eating up resources for 100% of Joplin users.

[laurent22]

Probably not as the point of default plugins was always to add additional features via plugins, especially for those users who may not know that plugins exist.

If we disable them by default, we may as well not add them at all. So it's more a problem of selecting which plugins we add and ensuring we don't add something that most users don't need.