📡 Unofficial Micro Plugin Channel

[Neko-Box-Coder]

Hi guys 👋, due to the lack of updates and accepted PRs for both the official plugin-channel and updated-plugins, I have decided to continue the work from @taconi with his discontinued (but awesome) plugin-channel.

https://github.com/Neko-Box-Coder/unofficial-plugin-channel

There is still some work to do but here are the major things I added to this plugin channel:

• Added requirements needed (and links to them) to use the plugin
• Added OS indicators to show which OS is supported
• Have both main (reference external repo) and stable (reference json and binaries stored in repo) channels
• Indicator for malicious code check

Here are the things that remain to be done:

• Indicator of it still being maintained or not
• Prefixing unofficial to plugins that are already in the official channel
• Maintaining/Replacing abandoned plugins in the official channel

Feel free to give any feedback, add your own plugin or use it as a plugin channel.

Thanks :)

[Neko-Box-Coder]

@dmaluka @JoeKar

This post is quite outdated but I guess this is the right place to ask for you guys' opinions.

I know we now have rights/access to the official plugin channel but it is pretty much not the main focus at all and a few problems:

1. The official repo itself is not mentioned, or at least hard to find unless you REALLY look for it.
2. Only minimum maintaince atm, got plenty of open PR and issues. (Which I understand, maintaining micro repo itself is already quite a bit)
   a. I regularly maintain the unofficial one quite frequently atm.
3. Mixture of plugin download sources from the repo release and external plugin repo release.
   a. The unofficial one currently provides 2 channels, main which links to external repo release and stable which links to unofficial repo release together with all the hashes of zips inside the stable branch itself.
4. Official repo README just provides minimum information, which I guess the micro website plugin page makes up with additional info.
   a. The unofficial one provides all the requirements the user need in order to use a plugin, together with code check (stable) and the plugin repo status itself.

I am wondering if you guys would agree to redirecting or move the default plugin channel to the unofficial one instead, given that I am actively updating and maintaining it atm.

One of the problems I have is security where the external repo upstream can change the code to anything (for the release zip) and this is pretty much RCE in a sense.

The unofficial channel doesn't really solve it per se but it has hashes which the user can quickly check against for the stable branch, we probably should introduce some sort of sha checksum to the plugin ecosystem.

Anyway, got sidetracked. The main point of me asking this is to make introducing plugins to the channel much easier, lessen the burden you guys have and make adding plugins that can be accessible (via channel) much quicker.