An open network for secure, decentralized communication
Showing 5 of 6 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Brooks Karlik
<p>Matrix-ircd is a work-in-progress bridge between matrix and IRC. The majority of the code was written in mid 2017 and does not use modern Rust asynchronous programming techniques, namely async/await. Instead, the project currently uses older asynchronous-styled code using manual combinators that have historically made maintaining (and writing) async code very difficult. This project will migrate the older futures code from 0.1.25 to std::future::Future and port all functions to using the newly introduced async/await syntax.</p>
Mentors: Student: Arnav Tiwari
<p>A reusable web component that a website author can download, style/theme, and embed into their website to make comments work with minimal integration difficulty. Could require user to log in with a matrix account to post (so your Matrix account would let you post comments on any website which used this), or support anonymous guest access. Current repository: <a href="https://github.com/arnav-t/riot-embedded" target="_blank">https://github.com/arnav-t/riot-embedded</a></p>
Mentors: Student: Tyagdit
<p>Transitioning the matrix connector in opsdroid to matrix-nio API to add support for E2EE and facilitate further development</p>
Mentors: Student: Nikolaos Filippakis
<p>This is a proposal concerning the addition of E2E encryption support for the Matrix bot in Go, go-neb. The project would touch upon other parts of the Matrix ecosystem for Go. Specifically the gomatrix library would need to be enhanced to support encryption-specific events (such as for the uploading and claiming of keys, handling of encrypted room events) and would potentially contain the bulk of the interactions with libolm, making it easier for future projects in Go to use the same functionality. Finally proper bindings for libolm need to be developed - some such projects exist but lack necessary operations for full E2E communications. The final result of this project would be go-neb working fully in encrypted rooms, as transparently as possible to its services.</p>
Mentors: Student: Devin Ragotzy
<p>Rust's procedural macros can be one of the more complicated and difficult to read sections of any codebase. A well-implemented and easy to use macro greatly improves a codebase by removing boilerplate code and user-facing complexity. My goal for the internship is to make the <code>ruma</code> macro crates readable and easy for newcomers to follow and add to. This will allow easier debugging and enable more people to review pull requests in the code-gen heavy crates. I plan to implement macro testing using <a href="https://github.com/dtolnay/trybuild" target="_blank">trybuild</a> or <a href="https://github.com/eupn/macrotest" target="_blank">macrotest</a> for both <code>ruma-events</code> and <code>ruma-api</code>. I will improve the error messages of the <code>proc_macro</code>s in <code>ruma-api</code> and <code>ruma-events</code> by using relevant spans and crafting helpful suggestions or examples to emit to the compiler, so the user knows exactly where and how to fix their code.</p> <p>The other goal of the project is to implement new code generation macros for the next breaking release version of <code>ruma-events</code>. The release will contain a major rewrite of how the event types are structured themselves and within collections. I will work on generating code for the new collection types and adapt existing code generation to the new API.</p>