deepbluev7
Developer of Nheko for fun and because its bugs annoyed me.
Employed by Famedly to work on Matrix stuff, because I am annoyed at communication getting lost in healthcare and to support a multi-vendor ecosystem around Matrix.
Involved too deeply in moderation stuff because I got offered some noodles.
Very noisy when I feel something needs a voice, often that just ends up being my own opinion though.
Recently elected as a member of the Matrix Foundation Board as an ecosystem representative and honestly somewhat scared of the responsibility.
If you have something to talk with me about, please do! I don't always have the time and energy for that, but I often do things wrong and need to be told why!
This biography stuff is getting longer each year and that is somewhat concerning... Congrats to anyone who made it to the end!
Session
Matrix is a decentralized and federated system with many different "vendors" or rather many independent developers, projects, instances and users. The protocol is also developed as an open specification with public proposals for any changes.
How do you even begin to fix a security issue in the specification that affects possibly every participant in the ecosystem? Let us dive into how this currently works, what challenges result from the way Matrix is used and developed and discuss some possible improvements. After all every system has a hole eventually and its strength is measured in how it deals with them. I am looking forward to hearing your ideas and suggestions!