mindroom-nio
This fork publishes the Matrix nio changes needed by MindRoom on a release schedule independent of upstream matrix-nio. It follows active upstream development closely and carries a focused set of additions, primarily bot-oriented E2EE behavior, reliability fixes, and Simplified Sliding Sync support that are not yet available in an upstream release. Generally useful changes are kept suitable for upstream contribution, while fork-specific packaging and policy remain clearly separated.
mindroom-nio is a fork of nio, a multilayered Matrix
client library. The distribution name is mindroom-nio; the Python import name
remains nio. The underlying base layer doesn't do any network IO on its own,
but on top of that is a full-fledged batteries-included asyncio layer using
aiohttp. File IO is only done if you
enable end-to-end encryption (E2EE).
Documentation
The full API documentation for nio can be found at https://matrix-nio.readthedocs.io
Features
nio has most of the features you'd expect in a Matrix library, but it's still a work in progress.
- ✅ transparent end-to-end encryption (EE2E)
- ✅ encrypted file uploads & downloads
- ✅ space parents/children
- ✅ manual and emoji verification
- ✅ custom authentication types
- ✅ threading support
- ✅ well-integrated type system
- ✅ knocking, kick, ban and unban
- ✅ typing notifications
- ✅ message redaction
- ✅ token based login
- ✅ user registration
- ✅ read receipts
- ✅ live syncing
- ✅
m.reactions - ✅
m.tags - 🟡 cross-signing support (fork addition; bot-scoped producer side — self-signs the account's own device so it stays usable under MSC4153. The verifier side, Secret Storage, and key backup are not implemented. See doc/cross-signing.md.)
- ❌ server-side key backups (room key backup, "Secure Backup")
- ❌ user deactivation (#112)
- ❌ in-room emoji verification
Installation
To install mindroom-nio, simply use pip:
$ pip install mindroom-nio
Note that this installs mindroom-nio without end-to-end encryption support. The e2ee enabled version can be installed using pip:
$ pip install "mindroom-nio[e2e]"
Additionally, a docker image with the e2ee enabled version of nio is provided in
the docker/ directory.
Examples
For examples of how to use nio, and how others are using it, read the docs
1 maintainer
Release files for mindroom-nio 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mindroom_nio-1.0.6.tar.gz | 211.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mindroom_nio-1.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 459.0 kB
Release files / mindroom_nio-1.0.6.tar.gz
| Download URL | mindroom_nio-1.0.6.tar.gz |
|---|---|
| Size | 211.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2565b5765dd9a1b3aa08e2ccdbc5654e31ac98d592106fb3f06cee7907ff82b
|
|
BLAKE2b-256 checksum How to use checksums |
42769ccf4d27335e4e29571a1d4c87984b1bd923b8fe449e22345c9d742bbaa1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / mindroom_nio-1.0.6-py3-none-any.whl
| Download URL | mindroom_nio-1.0.6-py3-none-any.whl |
|---|---|
| Size | 247.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eebf6bd392b64ef252165ad5de5892ad21204103fdf01ee1953aac35ba25dd22
|
|
BLAKE2b-256 checksum How to use checksums |
b954e9c170ade42bc44bc23f09bb49ed252a373f604cbcdec4f78b764f188716
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log
