Install from a ZIP
Choose Add plugin and pick a ZIP with plugin.json and its entry script, at the root or inside one folder. Every part is validated before anything is stored.
Features
This is the feature set of Venora 0.1.0. If something isn't on this page, it isn't in Venora yet. The roadmap says what's planned.
01 Plugin manager
Each plugin has a card with its name, version, author and description. Imported plugins are marked as imported.
Choose Add plugin and pick a ZIP with plugin.json and its entry script, at the root or inside one folder. Every part is validated before anything is stored.
Switch optional plugins on and off. A greyed-out, checked box marks a required bundled plugin. Imported plugins can never make themselves required.
See what each plugin declared, with a description of every permission. Sensitive ones need your confirmation at install and at every update that declares them.
Plugins declare settings, and Venora draws the dialog: on/off switches, text, numbers with limits, and choices from a list. Only you can change them, and a running plugin can subscribe to hear when you do.
Add a newer ZIP of an installed plugin. Venora compares versions using semantic versioning, shows the release notes, and keeps the plugin's settings and data.
Uninstalling an imported plugin stops it and deletes its files, enabled state, settings and stored data. Nothing of it remains.
Plugins can ship a changelog of breaking changes, new features, improvements and bug fixes. Update prompts show the new version's notes, and the info dialog shows the whole history.
A plugin can require a Plugin API version and a minimum Venora version. Incompatible plugins are refused at install, and skipped at load with the reason on their card.
A plugin's author, or list of maintainers, is shown as “By …” on its card. Like every plugin-provided string, it is shown as text, never as HTML.
02 At a glance
Plugins start when you open a channel and stop when you leave. If one fails, its card says why, and the others keep running.
03 Safe mode & recovery
Plugin CSS can restyle Fermo's page, including its settings. So Venora keeps its controls somewhere plugins can't reach.
04 Runtime
The same runtime applies to bundled and imported plugins alike. The security page covers each part in depth.
A dedicated worker in a sandboxed frame: no DOM, no network, no extension APIs.
Privileged work happens only through a fixed set of permission-checked capabilities.
Plugins are never sent your Fermo session token. A guard checks every message.
Each plugin gets its own key–value store of up to 1 MiB, kept across reloads and updates.
Plugins can subscribe to setting changes and to mentions appearing on the page.
A plugin with ui can restyle Fermo. CSS that loads resources or writes text isn't applied.
Per-plugin request, event and message limits, timeouts, and caps on storage and install size.
Stops plugins that stop responding. A plugin that keeps misbehaving stays off until you reload.
05 Bundled plugins
| Plugin | What it does | Permissions | Can disable |
|---|---|---|---|
| Mention avatars | Shows the mentioned user's avatar beside their name. Setting: avatar size, 12–32 px. | ui storage account network | Yes |
| UI fixes | CSS refinements for Fermo's account controls, search field and related layout. | ui | No, required |
| Venora status | Briefly confirms that Venora is running when Fermo loads. | ui | No, required |
Not in Venora yet