@PitaJ I was able to do it by giving the nav button a unique ID in the ID section and then just controlling the tooltip/button action in JS under the custom JS section. Surprisingly easy to do as it turns out.
@babaggeii The write API would contain support for API keys (and later on, access tokens), so there are plans to allow the write API to expose user-specific routes using the same user auth system as well.
@Joykiller Not sure if you're around anymore but I thought I'd respond anyway.
The problem with maintaining a plugin and theme directory is the maintenance aspect. We simply don't have the time to make sure everything is compatible, especially since every plugin created is a community contribution.
So we automate. We rely on plugin developers to report plugin compatibility, and serve only those plugins that are marked compatible. There is one downside, however, and that is plugins will quickly disappear in successive revisions of NodeBB unless the authors keep them up to date.
So there's definitely space for crowdsourcing as well. If a plugin is not marked compatible by the developer directly, multiple reports of compatibility by the plugin users should also count, and if enough votes come in, then the plugin should automatically be reintroduced.
that part isn't in yet, but it's on the wish list.