Vommet on the web
Vommet also runs in a web browser, with nothing to install. Use ours at web.vommet.app, or run your own copy next to your homeserver.
It's an app, not an account
Vommet on the web is the same Matrix app as the desktop version, just delivered by a website. It doesn't hold accounts. You sign in to your own homeserver, and your rooms, messages and contacts live there, exactly as with the desktop or phone app.
web.vommet.app suggests nether.im on the sign-in page because that's where the Vommet community
lives, but you can type any homeserver. A copy you host yourself can suggest yours.
Keep your recovery key handy
Your encryption keys are kept in this browser's storage. Clearing site data, using a private window, or a browser that throws storage away will sign this browser out and forget its keys, just like uninstalling the app would. Set up secure backup so you can unlock your old messages again.
What works compared with the desktop app
We test the web version in Chrome and Firefox.
Works
- Signing in with a password, unlocking with your recovery key
- Encrypted rooms, including older messages from your key backup
- Sending, replying, editing and reactions
- Files, images, stickers and custom emoji
- Staying signed in when you reload
Different
- Calls need your homeserver to support them, as in the desktop app
- No noise suppression from Vommet itself (your browser's own is used)
- Choosing an output device needs a browser that supports it (Chrome, Edge)
Not on the web yet
- Notifications
- Widgets
- Push-to-talk while another app has focus
- New-version notice (the website always serves the latest build)
Which browsers
The page picks the right version for your browser. There's nothing to choose.
| Browser | Version you get |
|---|---|
| Chrome, Edge and other Chromium browsers (119 or newer) | WebAssembly: starts faster, feels smoother |
| Firefox, Safari, and older Chromium browsers | JavaScript: does the same things, a bit slower |
Both versions draw with WebGL. If the page says Vommet needs WebGL, turn on hardware acceleration in your
browser's settings. Some privacy-focused browsers, LibreWolf among them, switch WebGL off by default: set
webgl.disabled to false in about:config, then reload.
The first visit downloads about 22 MB. After that, your browser keeps the app and only fetches what changed in a new release.
Hosting your own copy
Each Vommet release is published as a small container image: a web server with the app inside, listening on port 8080 and running as an unprivileged user.
| Tag | What it is |
|---|---|
testing-YYYY-MM-DDx | One tester release, never changes. Pin this if you want to choose when to update. |
testing | Always the newest tester release. |
latest | The newest stable release, once there is one. |
docker run
docker run -d --name vommet-web -p 8080:8080 \
-e VOMMET_DEFAULT_HOMESERVER=example.org \
ghcr.io/dark-collective/vommet-web:testing
Then open http://localhost:8080, or put it behind your reverse proxy with HTTPS (browsers only
allow calls, the microphone and encrypted storage on secure pages).
Docker Compose
services:
vommet-web:
image: ghcr.io/dark-collective/vommet-web:testing
restart: unless-stopped
ports:
- "127.0.0.1:8080:8080"
environment:
# Pre-filled on the sign-in page. Only a server name, no https://.
VOMMET_DEFAULT_HOMESERVER: example.org
Settings
VOMMET_DEFAULT_HOMESERVER: the homeserver suggested on the sign-in page, for exampleexample.org. People can still type another one. Without it, the image suggestsnether.im.VOMMET_CROSS_ORIGIN_ISOLATION=off: drops the two Cross-Origin headers below, for setups that embed pages which don't allow it. The WebAssembly version then runs single-threaded.
If you serve the files yourself
The image already does all of this. If you copy the files out of it, or put a proxy in front that rewrites headers, make sure that:
.wasmfiles are sent asContent-Type: application/wasm. Otherwise browsers refuse to start the fast version.- Every page is sent with
Cross-Origin-Opener-Policy: same-originandCross-Origin-Embedder-Policy: credentialless. The WebAssembly version needs them to run multi-threaded. - Paths that aren't files fall back to
index.html. index.html,flutter_bootstrap.js,flutter_service_worker.js,version.jsonandassets/assets/config/are sent withCache-Control: no-cache, so a new release shows up on the next reload.
Privacy
Vommet on the web sends the same things as the desktop app, and nothing more. Diagnostics are off unless you say yes, exactly as in the other versions. See the privacy page for what the website itself sees.