Of the 83,830 folks surveyed, Matrix was the #1 chat tool in terms of current users' satisfaction. It was also rated as the most desirable among the open source tools with open governance, but there is a lot of room for improvement in awareness. We’re excited to build on this 2024! 🚀
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.
For those familiar with Travis' weekly task lists of MSCs for the Spec Core Team to review in the Office of the Matrix Spec Core Team room, a new weekly list is now being posted in the Matrix Spec & Docs Authoring room. This list is aimed at technical writers who can help by converting MSC authors' words into PRs against the spec text itself.
This is the final step for getting an MSC integrated into a new release of the Matrix spec, and anyone can try their hand at it! It would also very much help the Spec Core Team by freeing up more bandwidth for review of the MSC backlog, as well as push forward the protocol itself. Thank you!
If you have any questions, feel free to ask them in the relevant Matrix rooms.
This MSC proposes expanding the set of suggested, interpreted HTML tags in Matrix clients to include additional tags related to tables. With them, more control over table rendering is possible. The proposal itself includes one such (albeit fairly arbitrary) example
The proposal is well-written and straight-forward, so do feel free to have a look if the subject interests you!
We’re excited to announce the timeline for our first ever elections as we take the next big step in open governance for Matrix. We’re also introducing two new membership tiers to increase community representation by including open source projects and foundations on the Governing Board.
unlimited file transfer size, given it's streamed - no longer limited to ~1GB to fit inside v8's 1.4GB heap on Web.
O(1) memory usage for sending files, given it's streamed (great for share extensions)
It works by switching from AES-CTR to splitting the file into blocks, and encrypting each one as AES-GCM, muxing into a very simple file format which provides basic headers to allow framing for incremental decryption and random access. Given this changes the security model of attachments significantly, and given the fileformat is homemade, this MSC is now blocked on needing some serious cryptographic review before it proceeds any further :)
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:
There were no new MSCs this week.
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
It's been a quite week from the perspective of the MSC Status list, but there has definitely been activity across various MSCs (at least according to my inbox). MSC3981 has seen discussion, as has MSC4041 and MSC2448 (we're considering switching the proposal to Thumbhashes).
Following on from the release of v1.98.0 (the final release of 2023), as well as seasonal holidays, we expect to return to our usual 2-week release schedule. Starting with a release candidate on Tuesday, January 9th.
As a reminder, Element is switching its development on Synapse to be AGPLv3 at https://github.com/element-hq/synapse, and development from Element's side now continues there (see the blog post if you haven't already). We have done our best to migrate issues from the now-archived matrix-org/synapse repo over, as well as preserving issue and PR numbers. PRs were not migrated, and their PR number has been reserved by a stub issue instead. Huge thanks to Erik and WillL for figuring out the plan there and implementing it (and working with GitHub's heavy rate limits on issue creation!). As well as fixing up CI, packaging, etc. etc.
As things have been a bit topsy-turvy with the migration (and of course the holidays), there's not a huge list of changes to report from the development side. But we did have a few excellent community contributions.
Hello wonderful people. I hope you all are having/had a good break. Over in bridge towers we've been working on a few holiday treats in the shape of hookshot improvements. Let me lay them down for you:
dark mode 🌗 is now a thing! We've moved the majority of the components used in the widget to use Compound, which means a more coherent style and light/dark support. It's still early days so please log bugs as you find them. Also, the dark mode is triggered by whatever the browser believes is your operating systems preference, so currently we don't match any overrides your Matrix client might be setting.
Lots of bug fixes around bits of widget interface not updating properly, particularly around feeds.
Node 18 support has been dropped, as it's not long for this world and we would like to focus on Node 20/21 support.
We have added a list and remove command for webhooks.
We now tell you if your bot doesn't have enough PL to speak, meaning you don't need me to confirm it for you :)
The GoNEB migrator has been removed, though you can still migrate in a prior release and upgrade.
It is a new year 🎆️, and what better way to celebrate this than to release Fractal 6.rc? It has been only 2 weeks since our latest beta release, but we have been hard at work during the holidays.
Here is an excerpt:
Matrix URIs can be opened with Fractal, it is even registered as a handler for the matrix scheme
Our Join Room dialog now shows some room details as a preview upon entering an identifier or URI
The verification flow was rewritten to rely more on the Matrix Rust SDK, hopefully solving most issues that occurred before
Room members now have a profile page that allows, among other things, to kick, ban or ignore them
Speaking of ignoring users, the list can be managed from the account settings
The dialog to view an event’s source was reworked to show more details about the event
… and a lot of other improvements, fixes and new translations thanks to all our contributors, and our upstream projects.
Version 0.4.0 of Element X Android is live on the PlayStore. It includes new features like Read Receipt, Chat backup and Mentions, and lots of other features and bugfixes. Full details here: https://github.com/element-hq/element-x-android/releases/tag/v0.4.0.
We are now focusing on performance, testing and stabilizing the application, in particular around the Rich Text Editor.
Lots of new features are planned for 2024, stay tuned!
In the past months we've had a lot of progress on Element Call our
scalable video and voice conferencing solution with calling built natively on Matrix and so benefitting from Matrix’s end-to-end encryption. Now is the time to slowly convert the existing video solutions to default to Element Call. We are starting with video rooms, which will be using the Element Call stack by default in the near future. If you (still) have a Jitsi video room, you will need to re-create it to make use of Element Call.
The minor update is similar to version 2.0.0, where it introduces a new module Matrix.Event but offers no major functionality at the time. The API interactions are planned to come after implementing an exposed Matrix.Room module for interactions with Matrix rooms.
This week, I would love it if you take a look at the Matrix.Event module, and let me know if the documentation is sufficient and meets your requirements. I'd love to hear your feedback in the Matrix room #elm-sdk:matrix.org.
Dept of Events and Talks 🗣️
The Matrix Community met at the 37th Chaos Communication Congress
The 37th Chaos Communication Congress, sort of a school reunion of hackers, recently ended. From the 27th to the 30th of December 2023, a bunch of nerdy people met up in Hamburg (northern Germany) to discuss all the cool stuff they had been up to. Topics ranged as wide as technology, society, politics and even food hacking as well as a whole lot of other interesting things (talks can by the way be found at https://media.ccc.de/ and most are already uploaded, wow!). We had a Matrix Community Assembly there. An assembly is basically an area for like-minded people to meet up and talk about their topics, in this case Matrix.
We answered questions, sold merch, talked about Matrix-related projects, had workshops about topics like setting up Hookshot, took group photos, tapped beer via Matrix, handed out a bunch of cool new Matrix Community stickers and even fixed some Matrix servers. And Nico bridged the whole Eventphone network to his Matrix account while tinkering and got very confused.
An example minimal website, dynamically sourcing its content from a public matrix room that anyone can read and publish to.
It uses a custom event io.gitlab.ugrp.post (with two keys, title and text) and provide an interface for guest and registered users to create a new post (cannot edit yet, tbd).
The site is built in vanilla HTML, CSS and Javascript, using the @sctlib/mwc library of web-components (the new version v0.2.1 allows to register a formTemplate and displayTemplate to be able to display and create and custom event in a room).
This is all prototypes (and examples), experimenting using public matrix data outside of traditional chat clients (see also matrix-static). The objectives are to allow users to manage and display their data in environments they control, and subscribe to event feeds from sources they chose.
New year, new homeserver! I completed a migration from managed Matrix with EMS to self-hosting using the matrix-docker-ansible-deploy project. It was a bit tricky as someone new to self-hosting Matrix, but a lot of folks helped along the way and the matrix-docker-ansible-deploy project greatly simplified the process.
I wrote up my notes in the Foundation blog in hopes that they'll be helpful, especially for other folks like me who were on small EMS plans that are being discontinued.
As of today, 8389 Matrix federateable servers have been discovered by matrixrooms.info, 2269 (27.0%) of them are publishing their rooms directory over federation.
The published directories contain 168449 rooms.
(Please ignore, that I never know, what year number to attach to such a "Year In")
You may remember I organized a small blog post last year to collect stories from the different community projects and what they did in the year and maybe some sneak peaks at the next year. If not, you can find it here or on the Matrix.org blog.
Anyway, enough about 2022, I now encourage you to talk about 2023 and beyond! If you have interesting stuff to report about your projects or projects you have been involved in in 2023, feel free to join #year-in-2023:neko.dev and talk about it! The usual TWIM rules apply there, just that we talk about a whole year and it may involve lots of manual editing on my side, so don't try to break it. Also please be positive in your news and lets try to end 2023 with a bang!
And please share this with projects you want to hear about. :)
I'll start with a heads-up that the Foundation is going to clean-up all the libera.chat aliases on Matrix. You might want to check the rooms under your control to update the alias and the matrix.to links to it.
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.
As you can make out from the stats, the spec process has been mostly quiet over the past couple weeks. In fact, the stats above are from the last couple weeks, as someone (cough, me) forgot to post a spec TWIM last Friday. All to be expected with the holidays looming however, including my own!
This MSC actually gives background and summarises itself pretty well, so I'm just going to copy/paste from it here as an explainer!
/messages returns a linearized version of the event DAG. From any given
homeservers perspective of the room, the DAG can have gaps where they're missing
events. This could be because the homeserver hasn't fetched them yet or because
it failed to fetch the events because those homeservers are unreachable and no
one else knows about the event.
Currently, there is an unwritten rule between the server and client that the
server will always return all contiguous events in that part of the timeline.
But the server has to break this rule sometimes when it doesn't have the event
and is unable to get the event from anyone else. This MSC aims to change the
dynamic so the server can give the client feedback and an indication of where
the gaps are.
This way, clients know where they are missing events and can even retry fetching
by perhaps adding some UI to the timeline like "We failed to get some messages
in this gap, try again."
It does this by adding a gaps property to the GET /_matrix/client/v3/rooms/{roomId}/messages endpoint, which tells the client which events its missing, instead of the client just assuming incorrectly!
Do check out the MSC if it sounds like something that would be useful to your client!
This week we released v0.13.5. Upgrading to this version is highly recommended, as it fixes several long-standing bugs in our CanonicalJSON implementation.
Here are a few of the highlights:
Fixes
Convert unicode escapes to lowercase (gomatrixserverlib)
Handle negative zero and exponential numbers in Canonical JSON verification (gomatrixserverlib)
Issues around the device list updater have been fixed, which should ensure that there are always workers available to process incoming device list updates.
Fixes around the way we handle database transactions (including a potential connection leak)
ACLs are now updated when received as outliers
Features
Appservice login is now supported!
Users can now kick themselves (used by some bridges)
...and a whole lot more. Check out the release notes for the full set of changes!
As always, feel free to stop by #dendrite:matrix.org to join in on the discussion and if you encounter a bug make sure to report it here.
The long-awaited Release Candidate for version 0.0.96 is finally out - not many changes as the last beta has been reasonably good. 0.0.96 release will be the last one supporting Qt 5.15; packagers are recommended to build it with the most recent Qt 6 at their disposal. Binaries for macOS and Windows are available from the GitHub Releases page linked to above, and a flatpak is already available from the beta channel at Flathub. Totally not promising the release before Christmas ;)
I didn't post many updates recently, but that was mostly because I was working on boring and tedious stuff, that isn't interesting to hear about. Nevertheless, I'll tell you about some of the things now.
On Wayland, if you want to activate your window (as in, bring it to the foreground), you are not allowed to do that. This is for security reasons, since when Wayland was designed, many people were dealing with bad web popups that always stole your focus. In itself that design decisions does make sense, but it does cause some problems. Want to open a notification? App will blink, but not come to the top. Want to open a url in your browser like matrix:r/nheko:nheko.im ? Well, the app will blink and open the url, but stays in the background! Want to run the app from the command line or an icon? Well, the existing window will blink, but not come to the foreground!
However, we fixed that. Usually you should get an activation token, but not all apps provide you with one (like X11 applications, KDEs Konsole, etc). Nheko will now try to use an activation token, when one is passed from your notification manager, but that didn't work reliably for the other ways Nheko could be activated. In those cases Nheko now creates a small window with a loading spinner to get an activation token (because launching a new window of course will bring you to the top...) and then uses that window after 100ms to create an activation token for the main app, sends it to the main app and now the main app can raise itself. Do you think this sounds like a terrible hack? Well, it is, but it works and that's better than nothing! Hopefully all the wayland users won't complain about the useless loading indicator in the future...
Also, on Windows clicking a notification didn't put you in the room. This is now fixed! And we have a shiny new Windows CI runner.
Speaking about Windows, we now also provide an msix for Windows users, that even has a valid signature (that costs quite a lot of money....)! This should make the installer experience quite a bit better for Windows users and soon even should provide auto-updates, but we still need to figure out if we want to enable the "ping nheko.im to check for an update every 15 days" or if we don't want to have our app call home... In theory that should be optional depending on how you install Nheko though. It will only be enabled when you use the appinstaller link, not the msix directly. Apart from that there is a small issue still in the notifications, where the App name now has a weird suffix... and possibly some issues with the protocol handler. If anybody has experience with Windows development, I would appreciate some help. I don't use the platform, so I am mostly flying blind there!
We also now use a different package to manage the single instance behaviour, which should work more reliably on Qt6. However that means you really shouldn't run Qt5 and Qt6 Nheko side by side!
There have been plenty of updates to the spanish translation by CM0use and leaving a space should now properly unhide its rooms again. Begasus also improved the Haiku support by a lot and plenty of smaller fixes!
At the current rate, see you next year, I guess? Thank you for reading our update!
The Elm SDK is an SDK in Elm that compiles to JavaScript and hence aims to be a competitor to the established matrix-js-sdk. This week, the SDK has released its beta 1.0.0 release on the public Elm registry!
The project has received funding from NLnet 💸 and it is now time to start releasing beta versions in an accessible way. The beta versions are experimental and unstable, but feedback is already going to be very much welcome as new versions are going to be released!
You can follow the progress in the Matrix room #elm-sdk:matrix.org and the project will also give you timely release updates on the Fediverse. 🦣
Attention: Changes to the Pricing Model at etke.cc
We're excited to announce a significant update to our pricing model at etke.cc, your trusted managed Matrix servers provider.
Transition to Pay-By-Complexity
In a move towards fairness, we're shifting from a flat-fee pricing model to a more dynamic, pay-by-complexity approach. This means you'll now pay based on the services you choose, allowing for a more tailored and equitable pricing structure.
Fair Pricing for Everyone
The previous flat-fee model sometimes led to discrepancies, where customers with different service needs paid the same amount. With pay-by-complexity, you'll only pay for the services you select, ensuring fair pricing for every user.
Introducing Base Matrix Server at $5/month
As part of this change, we're thrilled to offer a base Matrix server (just a Matrix homeserver and some core services, without bridges/bots, etc.) on your hardware for as low as $5/month—a 50% reduction compared to our previous Maintenance tier. This enables you to enjoy Matrix services at a more affordable rate.
New Services Available
Expanding beyond Matrix, we're reintroducing additional services, such as Miniflux, Radicale, Uptime Kuma, GoToSocial, Linkding, and Vaultwarden, available as paid add-ons. Your feedback will guide us in expanding this service portfolio gradually.
Hello, America and AMD-powered Servers
We're now supporting Hetzner Cloud's new AMD-powered CPX server line, offering improved performance-per-dollar and double the disk space. These servers are available not only in Europe but also in the US, opening up new possibilities for our customers.
FAQs: Your Questions Answered
We understand you may have questions about these changes. We've covered topics ranging from pricing adjustments to server upgrades and service additions in the full announcement, and in the FAQ entry. For existing customers, there's no rush—current pricing remains in place until at least July 1, 2024.
Explore the new offerings and get started with the enhanced etke.cc experience. To stay in touch, join the #news:etke.cc room and keep an eye on etke.cc/news.
There is a large interest in FOSDEM from the Matrix community, and we are very excited to see not just a stand, not just an online track, but an in-person Matrix devroom happening again this year! If you have been following the CfP, you know that the officially allotted time for the Matrix devroom at FOSDEM however is only half a day.
You may be wondering "wait, haven't I read this before?" and you would be correct. Last year, at this point a couple friends from the Community involved with organising several other Matrix events got together and started the "FOSDEM 2023 Matrix Community Meetup", and I dare say, to great success! So, this year again, we got together and sat down with the Matrix Foundation to plan yet another Matrix FOSDEM Fringe event, which is why this time around...
We are happy to announce the FOSDEM 2024 Matrix Foundation & Community Meetup at Hackerspace Brussels (HSBXL)!
The meetup is set to begin on Friday February 02 around noon local time (CET) and will go into the evening. See https://hsbxl.be/enter/ for multiple well documented ways how to find the way there. Thank you HSBXL for providing a location for this!
Further, we are also happy to announce that we have found some sponsors which again will enable us to provide some drinks and food for everyone! If you or your company are planning to attend and are able to contribute to the sponsoring, please contact Thib on Matrix or using legacy comms at mailto:thib@matrix.org!
More details will be announced soon in a blog post, so if you're not subscribed to the feed (https://matrix.org/atom.xml), do so using your favorite feed reader and watch this space!
In the meantime, you can already join #fosdem2024-foundation-community-meetup:matrix.org for all upcoming info, program suggestions, to follow the process & help out, general discussion and everything else related to the event.
Additionally this release contains important improvements and fixes in the chat: for once, you can edit chat messages now from within the Acter app (before it would display them correctly but you couldn't edit yourself) on all platforms. Secondly, we have reworked the entire multimedia handling for chat messages allowing for inline preview and viewing as well as in full-screen now, as well as several fixes around posting media. Learn more about all that in our latest blog post
I've added another section to my Matrix client tutorial, explaining how to encrypt and send to-device events with Olm. I had previously written sections on encrypting and sending to-device events. This new section deals with some of the additional considerations when there are multiple recipients, and how to manage the network requests. Notably missing from this section, so far, is how to deal with errors such as failing to get one-time keys; that will come later. Next up will be encrypting room events (which is already mostly written, but is lacking tests).
As of today, 8330 Matrix federateable servers have been discovered by matrixrooms.info, 2186 (26.2%) of them are publishing their rooms directory over federation.
The published directories contain 272674 rooms.
This Tuesday we released Synapse 1.98.0rc1. Its promotion to the 1.98.0 release proper is planned for the coming Tuesday (12th Dec). We expect v1.98.0 to be the final release of 2023, as the team takes a break over the holiday period.
This week we were sorry to announce that we are not able to bring the Libera.Chat bridge back online. We have already begun working through clean up tasks, such as clearing ghosts, and expect to be done by December 22. If you see any bridge artifacts left past that point, please let us know.
We know that many communities and individuals were relying on the bridge, and we regret the impact this situation has on them.
If you are one of those who have relied on the bridge in the past, you may be asking: what now? You do have options.
People who need a bridge for their community can run their own: the matrix-appservice-irc software is still maintained. Only its Libera.Chat instance, which was configured to persist connections across restarts, is being shut down. Please be mindful of the network, and read Libera.Chat’s recommendations and their Matrix FAQ when doing so.
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.
Get ready for another Hookshot release! The flagship new feature is the ability for Hookshot to respond to webhooks with custom response data, once Hookshot has handled the webhook message. This feature exists because while some services expect an immediate response to webhooks, others wait for the request to complete. With this release, Hookshot can now handle both cases. For more details, refer to the documentation.
The release is available at https://github.com/matrix-org/matrix-hookshot/releases/tag/4.6.0, or by doing docker pull halfshot/matrix-hookshot:4.6.0. And as usual, feel free to direct any questions about Hookshot in our Matrix room: #hookshot:half-shot.uk
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.
Cross-posting from TravisR's announcement in the Office of the Spec Core Team room...
Matrix 1.9
The next release, Matrix 1.9, is scheduled for release on Wednesday, November 29, 2023. This will largely be a maintenance release, but if there's anything you think we might have missed, please let us know.
Matrix 1.10
The Spec Core Team is now accepting MSC and feature suggestions towards the Matrix 1.10 release, due sometime around FOSDEM in February (unsure if it'll be before or after). So far we've got the following features up for consideration:
Extensible Events (at least proposing FCP on the majority of the core system; plan to merge for Matrix 1.11)
Encrypted appservices (like MSC2409)
Custom emoji/stickers (merge)
If there's specific MSCs, or even vague ideas you'd like the SCT to focus on, let us know in the Office of the Spec Core Team room. The SCT will generally find it harder to actually write the MSCs ourselves, but if you're planning on implementing a feature that will need spec review, let us know so we can ensure bandwidth is made available for that review to happen.
This MSC is paving the way towards the use case of a room where, for instance, announcements can be made by admins, while general users can start or participate in a thread branched off from an announcement. But they otherwise would not be able to make "top-level" posts.
This feature is common in services such as Telegram, for announcement or support rooms. And it would be nice to be able to support the same kind of use case in Matrix.
It looks like I dropped the ball on keeping up with the discussion on this one. So excuse me while I go do that!
Hello! today we are announcing the latest minor update, v0.1.3! This contains mostly small bug fixes and UI Improvements, as well as a few quality of life features!
What's New?
Rooms and spaces shared between multiple accounts are visually distinguished
Improved HTML Rendering
Implemented lazy loading of room members
Zoom and pan on images and video
Background task indicator for downloads
Direct messages in spaces are now visually distinct from rooms
Bug Fixes
Fixed an issue where a room shared between multiple logged in accounts wouldn't open correctly
Fixed notifications being displayed for old messages
FluffyChat v1.15.1 has been released with a lot of bugfixes and updated translations.This release also finally makes it possible to select text in the chat on web, desktop but also on mobile. Please be aware that the default long press behavior to select events has changed to normal taps because of this.
For the next release you can also expect the return of presences. While this feature is disabled
on matrix.org, it seems to work fine on other servers. The app tries to filter out users from servers where presences are disabled to
not display them as always-offline. I hope this works fine. As far as I can see, the difference is that on server with presences
enabled there is always a „last_active_ago“ field in the presence content. So the app assumes that, if the user is offline and
last_active_ago is NOT set, then it is better to just not display the presence status at all.
Element X Android 0.3.1 is available on the PlayStore.
We spent the week fixing bugs and improving our codebase. We are also adding the read marker and read receipt rendering to the timeline and are also progressing on the mention epic.
Jorge also made a big improvement on the release time for the Rust SDK. It now takes around 20 minutes, previously it was up to 5 hours!
We’ve tightened scope and started reviewing feedback and iterating on the new room header and right panel designs. Keep your feedback coming, we’d love to hear it!
If you don’t have the new header already, go ahead and try it out on Element Develop by using the labs flag: “Under active development, new room header & details interface”
The team’s been working on streamlining the process we use to release Element Web. We’ve simplified it and are working through different testing tools to ensure that we’ve got our automated tests running smoothly.
Our week has also been focussed on reducing the number of failing notification tests by fixing bugs and working through the test suite.
Another full release 0.23.0 of is out as of a few minutes ago (right as I'm typing this), with some nice bugfixes, nicer features, and important progress for a whole lot more (I'll give you a hint: 🧵)
MatrixJoinLink is bot that allows the creation of invite links to non-public rooms in matrix.
Several months have passed since I initially introduced the bot in TWIM.
In the interim, I've seamlessly incorporated the bot into various work related contexts as well as in private contexts.
The bot addresses the challenge of being unable to invite individuals via a link to a non-public room or space.
Since my last announcement, I further improved UX. The bot is now able to deal with various room identifiers (i.e., matrix.to links, internal room ids, and public room aliases).
How to use JoinLink
MatrixJoinLink simplifies the process of inviting users to non-public spaces.
Here's a guide on how to make the most of it:
Invite the bot into your room.
Once the bot joins, use the command !join help to explore its features. Please note that the bot responds exclusively to users or servers configured by the bot owner.
To create a Join Link, kindly type !join link Demonstration_Link, and the bot will promptly generate a join link for you. Ensure that the bot has the necessary permissions to invite users.
Help
Creation of Join Links (with Developer Mode Details)
Entering a Join Link Room
Feel free to test the bot and raise any issue using GitHub or using the development room that is mentioned in the project's README. Also consult the README for technical details.
a heads-up that the Matrix.org Foundation & Community Devroom has been accepted at FOSDEM24
You can find the CfP here, and submit your talk propositions before December 4
Centralize the Matrix Community at the Chaos Congress
As you may know, the 37th Chaos Congress takes place in Hamburg, 27.-30.12.2023. If you don't know, the Chaos Congress is a collection of cool people mostly from the different Chaos communities to talk about interesting topics ranging from technology all the way to politics. You will however need a ticket, which will only be available in very limited quantities.
Similar to the what we already did at the Chaos camp, we have applied for an assembly at the congress. An assembly basically is a few tables with people centered around a topic, where you can join to chat, participate in workshops or even get someone to fix or setup your Matrix homeserver!
Currently the assembly is not yet approved. However we are announcing it now, so that you can give it some thought if you want to participate and maybe help shape the Matrix Community assembly!
Since the proposal isn't public yet, there is no link to share to find more information about it. But if you are helping to organize the assemblies, you can find it in the backoffice.
So for now (and for later), if you want to discuss it, suggest things to do or have other comments, feel free to join us in #chaosevents:matrix.org!
So far we don't have a program yet, but maybe you have a cool workshop you want to do in our small round? Or maybe you just want to hang out and maybe answer questions people have about Matrix? Or maybe you just want to meet some Matrix developers, that you have always looked up to, to complain about how this one button is slightly of center when running their client on your PDP11?
In the end YOU can decide what you want this assembly to be, but now at least you know about it (if it gets approved)! Further updates will follow as we make progress and when we think you may have forgotten about us!
As of today, 8251 Matrix federateable servers have been discovered by matrixrooms.info, 2068 (25.1%) of them are publishing their rooms directory over federation.
The published directories contain 274767 rooms. Do you know what room isn't one of them? There are no rooms about backpacking among them, so if you're wondering "what an interesting room I can create to find great people to socialize with" - a room about backpacking would be a great choice!