307 lines
18 KiB
Markdown
307 lines
18 KiB
Markdown
+++
|
||
title = "This Week in Matrix 2023-05-19"
|
||
path = "/blog/2023/05/19/this-week-in-matrix-2023-05-19"
|
||
|
||
[taxonomies]
|
||
author = ["Andrew Morgan"]
|
||
category = ["This Week in Matrix"]
|
||
+++
|
||
|
||
## Matrix Live
|
||
|
||
No Matrix Live this week as Thib's away. Tune in next week though - maybe he'll do two!
|
||
|
||
## Dept of Spec 📜
|
||
|
||
[Andrew Morgan (anoa)](https://matrix.to/#/@andrewm:element.io) announces
|
||
|
||
> Here's your weekly spec update! The heart of Matrix is the specification - and this is modified by Matrix Spec Change (MSC) proposals. Learn more about how the process works at https://spec.matrix.org/proposals.
|
||
>
|
||
>
|
||
> ## MSC Status
|
||
>
|
||
> **New MSCs:**
|
||
> * [[WIP] MSC4016: Streaming E2EE file transfers with random access](https://github.com/matrix-org/matrix-spec-proposals/pull/4016)
|
||
> * [MSC4015: Voluntary Bot indicators](https://github.com/matrix-org/matrix-spec-proposals/pull/4015)
|
||
>
|
||
> **MSCs in Final Comment Period:**
|
||
> * *No MSCs are in FCP.*
|
||
>
|
||
> **Accepted MSCs:**
|
||
> * *No MSCs were accepted this week.*
|
||
>
|
||
> **Closed MSCs:**
|
||
> * *No MSCs were closed/rejected this week.*
|
||
>
|
||
> ## Spec Updates
|
||
>
|
||
> Matrix v1.7 has been given a release date of **May 25th**, right before the next TWIM! Expect a matrix.org blog post with all the details on the day.
|
||
>
|
||
> Leading up to the release we've seen a number of great spec PRs [appearing and being merged](https://github.com/matrix-org/matrix-spec/pulls?q=is%3Apr+sort%3Aupdated-desc+)! Thank you to everyone for writing them (saving the SCT some time!) and to other reviewing on commenting. It's a huge help and the spec feels like it's chugging along at a blistering pace!
|
||
>
|
||
> ## Random MSC of the Week
|
||
>
|
||
> The random MSC of the week is... [MSC2213: Rejoinability of private/invite-only rooms](https://github.com/matrix-org/matrix-spec-proposals/pull/2213)!
|
||
>
|
||
> This MSC adds the ability for users who have previously joined a room to rejoin again. Typically this isn't desired in a public room setting, but it does specifically make sense in the case of a DM that you've left and want to return to without the other user needing to invite you. This case has specific implications for cases where there could be only ever one room between two users. Being able to rejoin it if the other user has disappeared is key!
|
||
>
|
||
> Outside of the DM use case, this functionality can mostly already be achieved by using [restricted rooms](https://spec.matrix.org/v1.6/client-server-api/#restricted-rooms), where users of a given space/another room can always join your room. However, it would be nice to have the flexibility of allowing certain users to rejoin a room without needing another room to serve as proof of membership.
|
||
>
|
||
> Is this something you're interested in? Do you have additional use cases? Feel free to check out the MSC and comment with your thoughts!
|
||
|
||
<!-- more -->
|
||
|
||
## Dept of Clients 📱
|
||
|
||
### Fractal ([website](https://gitlab.gnome.org/GNOME/fractal))
|
||
|
||
Matrix messaging app for GNOME written in Rust.
|
||
|
||
[Kévin Commaille](https://matrix.to/#/@zecakeh:tedomum.net) says
|
||
|
||
> Fractal 5.beta1 is out!
|
||
>
|
||
> Fractal 5.beta1 is the first beta release since the rewrite of Fractal to take advantage of GTK 4 and the Matrix Rust SDK. It is the result of over two years of work.
|
||
>
|
||
> New features since Fractal 5.alpha1:
|
||
>
|
||
> * Joining room by ID, by alias or with a Matrix URI
|
||
> * Creation of direct chats
|
||
> * Sending and displaying read receipts, read markers and typing notifications
|
||
> * Notifications on new messages
|
||
> * Highlight messages with mentions
|
||
> * Added media file history viewers in the room details, thanks to our GSoC intern Marco Melorio
|
||
> * Displaying the other user's avatar as a room avatar for direct chats
|
||
>
|
||
> Of course, there are a also a lot of less visible changes, fixes and translations thanks to all our contributors, and our upstream projects.
|
||
>
|
||
> As the version implies, this is still considered beta stage and might trigger crashes or other bugs but overall should be pretty stable. It is available to install via Flathub Beta, see the [instructions in our README](https://gitlab.gnome.org/GNOME/fractal#beta-version).
|
||
>
|
||
> _The GNOME 44 runtime used by the beta version Flatpak was shipped with a GTK version that has a regression which messes with room order in the sidebar: some rooms can appear twice and some rooms are missing. This is a known issue so there is no need to report it, there is nothing for us to do but wait until the fix is backported and shipped in an update of the GNOME runtime. In the meantime, the nightly version is unaffected by that._
|
||
>
|
||
> A list of blocking issues for the release of version 5 can be found in the [Fractal 5 milestone](https://gitlab.gnome.org/GNOME/fractal/-/milestones/18) on GitLab. All contributions are welcome !
|
||
> 
|
||
> 
|
||
|
||
### FluffyChat ([website](https://fluffychat.im))
|
||
|
||
|
||
|
||
[Krille](https://matrix.to/#/@krille:janian.de) announces
|
||
|
||
> Here's a quick rundown of what's been happening in the Fluffy world over the past week:
|
||
>
|
||
>
|
||
>
|
||
> 📱 Android:
|
||
>
|
||
> * Updated minimum SDK version from 16 to 19. With the latest Flutter upgrade this was necessary. So FluffyChat will no longer be installable on Android 4.3 and below.
|
||
>
|
||
> 🔧 Miscellaneous:
|
||
>
|
||
> * Added missing blockquote style.
|
||
> * Cleaned up unused translations.
|
||
> * Various code clean-ups and maintenance tasks.
|
||
>
|
||
> 🔄 Refactoring and Updates:
|
||
>
|
||
> * Refactored Flutter Matrix HTML
|
||
> * Updated fonts for improved visuals.
|
||
> * Leveraged DateTime for accurate weekday localization.
|
||
>
|
||
>
|
||
>
|
||
> 🐞 Bug Fixes:
|
||
>
|
||
> * Fixed render overflow caused by long file names.- Improved error reporting for critical issues.
|
||
>
|
||
> 💡 Exciting New Features:
|
||
>
|
||
> * Mute notifications from chat groups with a simple toggle.
|
||
>
|
||
> 🔧 Maintenance and Dependency Updates:
|
||
>
|
||
> * Streamlined codebase by removing unnecessary dependencies.
|
||
> * Updated dependencies for enhanced performance and security.
|
||
> * Enhanced release curl calls for better error handling.
|
||
> * Updated translations (thanks to all translators)
|
||
>
|
||
> We are working hard to make the next release possible to bring these changes to all users soon. Stay tuned <3
|
||
|
||
### Ement.el ([website](https://github.com/alphapapa/ement.el))
|
||
|
||
Matrix client for Emacs
|
||
|
||
[alphapapa](https://matrix.to/#/@alphapapa:matrix.org) says
|
||
|
||
> [Ement.el](https://github.com/alphapapa/ement.el), a Matrix client for the [GNU Emacs](https://www.gnu.org/software/emacs/) Lisp machine and text editor, has been released at [version 0.9](https://github.com/alphapapa/ement.el/releases/tag/v0.9). Changes since the last release include:
|
||
>
|
||
> *Additions*
|
||
>
|
||
> + Option `ement-room-timestamp-header-align` controls how timestamp headers are aligned in room buffers.
|
||
> + Option `ement-room-view-hook` runs functions when `ement-room-view` is called. (By default, it refreshes the room list buffer.)
|
||
> + In the room list, middle-clicking a room which has a buffer closes its buffer.
|
||
> + Basic support for video events. (Thanks to [Arto Jantunen](https://github.com/viiru-).)
|
||
>
|
||
> *Changes*
|
||
>
|
||
> + Using new option `ement-room-timestamp-header-align`, timestamp headers default to right-aligned. (With default settings, this keeps them near message timestamps and makes for a cleaner appearance.)
|
||
>
|
||
> *Fixes*
|
||
>
|
||
> + Recognition of certain MXID or displayname forms in outgoing messages when linkifying (aka "pilling") them.
|
||
> + Unreadable room avatar images no longer cause errors. (Fixes [#147](https://github.com/alphapapa/ement.el/issues/147). Thanks to [@jgarte](https://github.com/jgarte) for reporting.)
|
||
> + Don't error in ~ement-room-list~ when no rooms are joined. (Fixes [#123](https://github.com/alphapapa/ement.el/issues/123). Thanks to [@Kabouik](https://github.com/Kabouik) and [Omar Antolín Camarena](https://github.com/oantolin) for reporting.)
|
||
> + Enable member/room completion in compose buffers. (Fixes [#115](https://github.com/alphapapa/ement.el/issues/115). Thanks to Thanks to [Justus Piater](https://github.com/piater) and [Caleb Chase](https://github.com/chasecaleb) for reporting.)
|
||
>
|
||
> Feel free to join us in the chat room: [#ement.el:matrix.org](https://matrix.to/#/#ement.el:matrix.org).
|
||
|
||
### Element Android ([website](https://github.com/vector-im/element-android))
|
||
|
||
Secure and independent communication for Android, connected via Matrix. Come talk with us in [#element-android:matrix.org](https://matrix.to/#/#element-android:matrix.org)!
|
||
|
||
[kittykat](https://matrix.to/#/@kittykat:matrix.org) reports
|
||
|
||
> * Element Android 1.6.0 has been released in the beta channel, it is now using the Crypto Rust SDK. It will be rolled out slowly (currently 5%). We are monitoring the deployment and gathering feedback. The production release will only happen after the rollout and might contain any needed fixes
|
||
> * We’ve also had some improvements to the Rich Text Editor, especially to mention slash commands.
|
||
|
||
### Element X Android ([website](https://github.com/vector-im/element-android))
|
||
|
||
The next generation of Element on Android! Come talk with us in [#element-android:matrix.org](https://matrix.to/#/#element-android:matrix.org)!
|
||
|
||
[kittykat](https://matrix.to/#/@kittykat:matrix.org) reports
|
||
|
||
> * The team is working on:
|
||
> * Adding invite users to room
|
||
> * Roomlist context menu (which will include settings and leaving the room)
|
||
|
||
### Element X iOS
|
||
|
||
[Ștefan](https://matrix.to/#/@stefan.ceriu:matrix.org) says
|
||
|
||
> This has been a very exciting week for Element X iOS with our second ever public release seeing the light of day. The change log is huge and the app is better than ever so do please join our [public testflight](https://testflight.apple.com/join/uZbeZCOi) if you haven't already.
|
||
> We now have room and member details, media uploading, animated gif support, user blocking, system notifications, room leaving and many many more. Feel free to also join our [public room](https://matrix.to/#/#element-x-ios:matrix.org)
|
||
>
|
||
> Otherwise this week we have been focusing on:
|
||
> * custom rendering for different reply room message types in the timeline
|
||
> * background app refresh support
|
||
> * read receipts
|
||
> * inviting people to rooms
|
||
> * creating new rooms
|
||
> * and last but not least: bug fixes, general stack cleanup and architectural improvements
|
||
|
||
## Dept of SDKs and Frameworks 🧰
|
||
|
||
### Elm SDK ([website](https://github.com/noordstar/elm-matrix-sdk/tree/main))
|
||
|
||
[Bram](https://matrix.to/#/@bram:noordstar.me) reports
|
||
|
||
> Sometimes, development isn't about writing code, it's about looking ahead and planning!
|
||
> In the past three weeks, I've tried to figure out how filters work combined with endpoints like [`/sync`](https://spec.matrix.org/v1.6/client-server-api/#get_matrixclientv3sync), [`/messages`](https://spec.matrix.org/v1.6/client-server-api/#get_matrixclientv3roomsroomidmessages) and [`/context`](https://spec.matrix.org/v1.6/client-server-api/#get_matrixclientv3roomsroomidcontexteventid) - and it turns out I couldn't find any straight answers!
|
||
>
|
||
> So I wrote [a whitepaper](https://github.com/noordstar/elm-matrix-sdk/blob/main/development/issues/Filters.md) in the [Elm SDK repository](https://github.com/noordstar/elm-matrix-sdk/tree/main) on the inconsistencies and where the spec is unclear (to me, at least). I hope you're willing to look into it as I might open up an MSC soon where I request to be more specific about filters and the endpoints.
|
||
>
|
||
> [Read the whitepaper here,](https://github.com/noordstar/elm-matrix-sdk/blob/main/development/issues/Filters.md) and please give me your feedback and/or corrections!
|
||
|
||
### matrix-scala ([website](https://github.com/UMEssen/matrix-scala/tree/main))
|
||
|
||
[cheb](https://matrix.to/#/@chebureki:matrix.org) reports
|
||
|
||
> I've developed a rudimentary Matrix-Library for Scala for akka, for distributed async systems.
|
||
> The underlying code is actually automatically generated from the specification, with strong typing, automatic JSON (de-) serializiation and a rudimentary client provided.
|
||
> It features the entirety of the client-server API. This is achieved via a custom code-generator.
|
||
> This library provides _just enough_ stuff to easily build a fully fletched client.
|
||
> A more high-level client is in development right now. Encryption will be hard, but will hopefully be implemented via JNI in the foreseeable future.
|
||
>
|
||
> This is part of Germany's effort to move hospitals messaging systems to the Matrix protocol.
|
||
>
|
||
> In case you want to check it out:
|
||
> A prebuilt is also provided
|
||
> https://github.com/UMEssen/matrix-scala/tree/main
|
||
|
||
### Trixnity ([website](https://gitlab.com/trixnity/trixnity))
|
||
|
||
Multiplatform Kotlin SDK for Matrix
|
||
|
||
[Benedict](https://matrix.to/#/@benedict:imbitbu.de) announces
|
||
|
||
> Trixnity got its first big external contribution in version v3.6.2!
|
||
>
|
||
> features:
|
||
>
|
||
> * added support for Android [room](https://developer.android.com/jetpack/androidx/releases/room) database. Thanks to Jon Poulton!
|
||
>
|
||
> bugfixes:
|
||
>
|
||
> * allow parallel use of Okio media store
|
||
|
||
## Dept of Bots 🤖
|
||
|
||
### Trinity ([website](https://github.com/bnjbvr/trinity))
|
||
|
||
[bnjbvr](https://matrix.to/#/@bnjbvr:delire.party) reports
|
||
|
||
> Matrix bots in Rust and WebAssembly. If you're interested to follow the project, feel free to join [#trinity:delire.party](https://matrix.to/#/#trinity:delire.party) or get the code on [Github](https://github.com/bnjbvr/trinity).
|
||
>
|
||
> Since last time, we've upgraded to the latest version of wasmtime, wit-bindgen and cargo-component, and even found [a bug in the toolchain](https://github.com/bytecodealliance/cargo-component/issues/80)! Thanks to the Bytecode Alliance folks for helping with a workaround.
|
||
>
|
||
> We've also converted all the bot commands so they make use of the simpler `libcommand` API, and thanks to that, we could add support for emoji reactions easily. Now the bot will report success by adding 👌 annotation to the (human) request.
|
||
>
|
||
> The bot will also report its presence as disconnected as soon as the program exits (and automatically mark itself connected when it gets back, but that part is thanks to the Rust SDK 💜).
|
||
|
||
## Dept of Events and Talks 🗣️
|
||
|
||
### Matrix Community Summit 2023 ([website](https://matrix.to/#/#matrix-community-summit:c-base.org))
|
||
|
||
[Christian Paul (jaller94)](https://matrix.to/#/@jaller94:matrix.org) reports
|
||
|
||
> To follow up on the overwhelmingly successful conference last year, we're planning a second Matrix Community Summit in Berlin. We expect this to have 3 days of activities.
|
||
>
|
||
> * Thu, 21st Sep: BarCamp day (attendees pitch topics and vote for which to discuss)
|
||
> * Fri, 22nd Sep: Conference day
|
||
> * Sat, 23rd Sep: Conference day
|
||
>
|
||
> The website and Call for Presentations is being worked on. Expect both to be announced here in the following weeks.
|
||
>
|
||
> This event will take place in Berlin, with the most likely location being the one from last year: The famous hacker space c-base. If you know any place more suited for a conference, please contact us. https://matrix.to/#/#matrix-community-summit:c-base.org
|
||
>
|
||
> Your Matrix Salon Berlin
|
||
|
||
## Dept of Interesting Projects 🛰️
|
||
|
||
### Beepberry ([website](https://beepberry.sqfmi.com))
|
||
|
||
[Eric Migicovsky](https://matrix.to/#/@eric:beeper.com) announces
|
||
|
||
> I announced a little side project yesterday: Beepberry - a portable e-paper computer for hackers, designed for chatting on Beeper (universal messaging app built on top of Matrix). My day job is running [Beeper](https://beeper.com/), but I will always have a soft spot for building hardware (I was the founder of Pebble).
|
||
>
|
||
> I wanted to create a ‘weekend’ device that would let me stay in touch with friends and family, without the distractions of a full smartphone. I imagined a tiny, hackable e-paper screen with a physical keyboard, powered by a Raspberry Pi, that I could use to chat around my home…and do pretty much nothing else.
|
||
>
|
||
> Before Matrix, the idea probably would not have gone anywhere. Most chat apps do not have an API, making it practically impossible to hack something like this together.
|
||
>
|
||
> I partnered with [sqmfi](https://twitter.com/sqfmi) and they’re starting to take pre-orders at https://beepberry.sqfmi.com for the first batch. It’s $79 (or $99 including a Pi Zero). Specs: Sharp Memory LCD (same display tech as in Pebble!), Pi Zero (BT/WIFI), physical keyboard, 2000mAh lipo.
|
||
>
|
||
> On top of being an amazing chat device, it’s basically an e-paper Cyberdeck that fits in your pocket. It’s a ton of fun to hack on. Keep in mind - THIS IS NOT A REAL FINISHED PRODUCT. It’s basically a devkit.
|
||
>
|
||
> More info in the blog post: https://blog.beeper.com/p/beeper-x-sqmfi-beepberry, or join `#beeper-general:beeper.com`
|
||
>
|
||
> Here's what it looks like running a slightly customized version of [gomuks](https://github.com/tulir/gomuks/tree/beepberry): https://www.youtube.com/watch?v=fIgzybDcvYk
|
||
>
|
||
> If you are a hacker and want to apply to get one early, fill in [this form](https://docs.google.com/forms/d/e/1FAIpQLScke9gVW86McF3NQB6hFtxSz8nMlbEYUPvr4cpG5gHUSGIHpg/viewform) after ordering.
|
||
|
||
### NeoBoard ([website](https://github.com/nordeck/matrix-neoboard))
|
||
|
||
[Dominik Henneke](https://matrix.to/#/@dhenneke:matrix.org) reports
|
||
|
||
> We are pleased to announce the [NeoBoard](https://github.com/nordeck/matrix-neoboard) — an open-source collaborative whiteboard widget for Matrix! The NeoBoard is an ideal tool for creating and sharing content, conducting presentations, and collaborating with colleagues or friends. All data is stored as Matrix events within the Matrix room, leveraging Matrix's native end-to-end encryption, decentralization, and data privacy features.
|
||
>
|
||
> The widget uses CRDT documents (conflict-free replicated data type) and WebRTC to provide a seamless and fast editing experience. It is used in the German public sector and is now available to anyone looking for a powerful and secure way to collaborate.
|
||
>
|
||
> The NeoBoard is the latest widget from [Nordeck](https://github.com/nordeck), which we have been developing behind the scenes in the past months, and we're excited to finally share it with the Matrix community. If you have any questions, reach out to us at [#nordeck:matrix.org](https://matrix.to/#/#nordeck:matrix.org).
|
||
>
|
||
> 
|
||
|
||
## That's all I know
|
||
|
||
See you next week, and be sure to stop by [#twim:matrix.org](https://matrix.to/#/#twim:matrix.org) with your updates!
|