This Week in Ruma

› published on 2016-07-03 by Jimmy Cuadra

Three major milestones happened for Ruma this week!

Support for events, the basic unit of data in Matrix, landed on the master branch. This is very important, because it's the foundation for almost all the core functionality of the homeserver. The initial implementation of events does not support federation, to keep the scope small, and because the details of federation are still not well specified.
Ruma's documentation website was launched, with its first guide, the Introduction to Matrix, which provides a great explanation of Matrix targeted at non-technical users.
Ruma reached the top of the Hacker News front page. Be sure to read the comment thread.

Notable changes to `ruma`

Add support for events.
Add partial support for additional parameters to the room creation endpoint: name, topic, preset, and invite.
Create some of the necessary events when a room is created: m.room.create, m.room.name, m.room.topic, m.room.history_visibility, m.room.join_rules, and m.room.member.

All event types were restructured to include two generic parameters, one for the primary "content" payload, and one for optional "extra content." This was done to support certain events in the specification that have non-standard key-value pairs at the top level of the data structure.
Remove the EventKind trait.
Add support for custom event types.

Add new documentation site and Introduction to Matrix guide. (Contributed in part by Leah Scampoli.)

SYN-720: Validation of event content from user input

Note that this is a bug filed against Synapse, not the spec itself. This was discovered while working on support for the room creation API endpoint's initial_state parameter. Ruma will do proper validation of state events created through this mechanism.