From the editor
I'm back from my vacation to Montreal and Quebec City (which are lovely and you should visit) and working on Ruma again!
Although development this past week was hindered a bit by another round of breaking changes to the Rust compiler's
libsyntax crate, which affects Ruma's use of
diesel, there have been a few changes to Ruma and some movement on the Matrix specification.
For anyone interested in following This Week in Ruma regularly, it is now available via an Atom feed.
Notable changes to
New CLI subcommand,
This new subcommand generates and prints a secure random value suitable as the
macaroon_secret_keyin the Ruma config file. This value is used as the secret key for creating user access tokens using Macaroons.
Interactive authentication removed from
At least for now, user registration will not require any sort of external credential verification. This area of the spec is currently less stable, so implementing it will wait until it makes more sense.
Simplified structure for crates, modules, and tests
The integration tests have been moved into the
srcdirectory so that it's not necessary to split
rumainto a binary and a library just so the integration tests can link to the library. This makes Cargo.toml and various
Swagger data source
rumanow serves a JSON structure at
/ruma/swagger.jsonthat can be loaded by Swagger UI to display the full Matrix client-server specification that will eventually be implemented by Ruma.
Matrix at large
There has been a bunch of activity on the spec recently. It appears that the Matrix team is preparing for a stable 1.0 release of the client-server API spec. A branch I worked on for the spec landing page of the specification was also merged. Those changes improve the organization of the information to make several things clearer to first-time readers.