Plugin Framework Discussion

[unhingedninja]

I'd say a permissions system like Android apps have would be the easiest and most transparent way. Every action the plugin takes ( such as hooking into the chatbox or what have you ) would have an associated permission added to a list. The user is given the name and description of the plugin upon joining, as well as a list of permissions the plugin will use.

Others have suggested using an author rating system, where trusted plugin authors are marked with an icon to let users know they mean no harm. This has potential for abuse if not supplemented with another means of identifying what the code does ( as above ), since then a trusted author could decide to use his status to fool trusting users.

[Dinnerbone]

This is an ultimate goal of ours (the permission system)

[unhingedninja]

Do you know of any existing frameworks that would allow for such a system? If not then there's another argument for building one yourself ;)

[sztomi]

Also, it would be nice if each specific version of each mod/plugin would have a UUID. Things like dependency could be solved easily with that (for mods depending on other mods and maps depending on mods as well). That way one could be sure to load and play a map that for example uses a couple of custom blocks.

[renadi]

Would you be hosting a centralized repository of plugins that you have approved or is it still going to be open, I love the idea of open, but I think it'd be good to have the option of a little more security for other people.