> The developers are silent as spies.
Until just now: https://github.com/matrix-org/matrix.org/issues/2483#issueco...
In Matrix.org Breaks Federation: Users Can't Decrypt Messages from Other Serversmatrix-org
matrix.org
JavaScript2019–2024
matrix-org / matrix.org
matrix.org
matrix.org public website
25Distinct people
37Mentions
0Explicit recommenders
631GitHub stars
What to know before exploring
What it is
matrix.org public website
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year37 dated mentions
Observed mentions: 2019-04-12 07:47:30 UTC to 2024-09-24 07:51:00 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 19 | 3 | 16 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 8 | 1 | 7 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Matrix.org Website
If you want to contribute to the website, make sure the problem you're trying to
fix or the feature you want to implement has been discussed in our issue tracker
and that we are interested in reviewing and merging such a contribution.
We are self-documenting our processes in CONTRIBUTING.md
and how to write content for the website in CONTENT.md.
To discuss maintenance of this site, please come talk to us, the
Website & Content Working Group, in
#matrix.org-website:matrix.org.
Cloning the Repository
Due to historic growth and media the repository is quite large. Therefor we
suggest the usage of --filter=blob:none when doing a fresh clone:
git clone --filter=blob:none git@github.com:matrix-org/matrix.org.git
This allows to only fetch the actually needed things from the git repository
instead of all of the (at the time of writing) 1.18GiB of data.
With this command at the time of writing this reduces the downloaded data to
just 612MiB.
For more information on this please check out these 2 articles which also
explain why --depth=1 is not ideal and which implications this has:
https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone/
https://web.archive.org/web/20241001150554/https://nayak.io/posts/git-clone-optimizations/
Building the website
Install version 0.20.0¹ of Zola, clone the repo,
and from the root of the repo type
zola serve
Zola will build the website and start a web server, usually at
http://127.0.0.1:1111
¹ This is the Zola version that is being used to build the website in CI.
See ./.github/workflows/zola.yml.
Read the full README on GitHubWhat Hacker News says
37 sourcesMatrix.org Breaks Federation: Users Can't Decrypt Messages from Other Servers
32 points · Open discussionThe default and largest server for registering accounts on the Matrix network — matrix.org — has broken federation. Specifically, it has disrupted the exchange of encryption keys with all other servers.
Users with accounts on matrix.org can communicate among themselves but cannot decrypt messages from users with accounts on any other servers. The error 'unable to decrypt message' appears in Element, and 'message could not be decrypted due to missing key' in Nheko.
Meanwhile, there are no key exchange problems between users on any other servers.
In other words, matrix.org has isolated itself, forcing everyone else (those who set up their own servers or registered on small company servers, for example) to create accounts on matrix.org to avoid losing contact with the majority of people on the network.
The developers are silent as spies: htt
Read the rest
ps://github.com/matrix-org/matrix.org/issues/2483
Although the problem has been observed at least since the end of July.
The problem was tested on different clients (both on PC and Android), in various operating systems, with different servers, under VPN and without, with different residentional providers. The /discardsession command was tried — it's definitely not something that broke on my end personally.
I believe that amid the fight against end-to-end encryption in England, Germany, and France, authorities have simply approached them and asked to create a walled garden to prevent people from spreading across uncontrolled servers.
That's a very interesting thread, because this is one of the major issues we have with Matrix. It's not directly a product but a (technical) protocol that can't be presented as such to the general public.
We definitely aim for Matrix-based products to be used by the general public, in the same way emails are. For this to happen, we need to be mindful of who our audiences are, what they are looking for, what they know and don't know, and how to deliver a message that works for them.
If you're interested in how we thought the website, you can check https://github.com/matrix-org/matrix.org/issues/1502 and https://github.com/matrix-org/matrix.org/issues/1543 for example
In The Matrix TrashfireIndeed the documentation generally needs much more love. In an ideal world, every single page of the documentation would have a person in charge of keeping it up to date.
We're a rather small team on the Foundation side and lack the personpower to do so.
We're in the process of listing what documentation we need and what we need to update. This will be the foundational work to apply to Google Summer of Docs and for individual tech writers to apply to grants like NLNet (who doesn't usually fund "large" organisations like us) to help us out.
I'm also adding instructions on how people can step in and contribute to the docs if they have the time and desire to do so: https://github.com/matrix-org/matrix.org/pull/2155
We're doing our best with our limited resources, but I'm confident we can improve the situation eventually!
In The Matrix TrashfireFor the matrix.org website, we landed https://github.com/matrix-org/matrix.org/pull/2179 as a quick fix, but we can do better.
I think there are several things we can do improve, and the process should be fairly similar with Element:
1. Refine who the website is for, and what they are coming here for. We need to narrow down who our audiences are, what they want, what they known and don't know, and how we can best serve them.
2. Conduct user research with a diverse set of people representative of who we think our audiences are. We need to sit down with them, ask them to create a matrix account unguided, and ask them to comment what they are doing and how they feel about things.
One of the difficulties of the website is to find the right balance between not overwhelming the user with difficult decisions (picking a client? picking a server?
Read the rest
I just want to chat with my friends!!) without being too biased. We need to be opinionated to guide newcomers through a decently simple process, but we need to leave room for all the vendors to thrive.
Hi, I'm the Thib person mention in this article, and I agree that QA is super important. I can mostly talk about matrix.org, since I have little power over the Element clients. Disclaimer though: I'm technically employed by Element (to make paperwork simpler since I'm France-based, Element has an entity in France, and the Foundation is UK-based), but I'm working for the Foundation full time.
This kind of article is super valuable since it gives us the perspective of a new user. I opened https://github.com/matrix-org/matrix.org/issues/2178 to translate the gripes mentioned in the issue into actionable items for us. I took action on the most urgent one (updating the Try Matrix page), but want to take the time to go beyond the surface symptoms and address the root cause of the other gripes.
On the Foundation side, we're a small but mighty te
Read the rest
am of four. The website is currently maintained part time by me and a volunteer who is doing an excellent job at it.
As I wrote recently in a blog post "Tracking what works, not people" (https://ergaster.org/posts/2024/01/24-tracking-what-works/), I would love to have the resources to conduct user research and user testing on the website but I unfortunately don't. We deployed privacy-preserving analytics to see where people drop and what confuses them. It's not nearly as good as proper QA and user testing, but that's what we can afford for now.
Overall I'm grateful to the author for documenting their frustration, and even more grateful for reacting constructively to our responses and integrating them in the blog post! One of the strengths of open source is to find and address issues collectively. I consider this blog post to be a good open source contribution.
If people around believe in our mission and want to help us with their brainpower, I invite them to join our "Office of the Matrix.org Foundation" room: https://matrix.to/#/%23foundation-office:matrix.org
For those aligned with our mission and who want to support us financially, the https://matrix.org/support/ page should give you all the information you need to help us out.
no idea what's going on here; the post hasn't been changed since it was published: https://github.com/matrix-org/matrix.org/commits/main/conten...
In The Future of Synapse and DendriteScalar (the integration manager) is not open source [1] (though there was some effort to reverse-engineer its protocol [2]); and some of their anti-abuse scripts aren't public [3]
[1] https://github.com/vector-im/element-meta/issues/260
[2] https://github.com/turt2live/matrix-dimension/blob/master/do...
[3] https://github.com/matrix-org/matrix.org/issues/557
In Matrix 2.0: How we’re making Matrix go voomMatrix Cryptography Clarifications
2 points · Open discussionElement currently piggybacks on the Matrix.org Foundation bug bounty programmes (which are the relevant ones here anyway, given matrix-appservice-irc is a Matrix.org project - i.e. owned by and managed by the Foundation, albeit with lots of contributions from Element employees)
Right now the Matrix.org Foundation is between bug bounties - we ran an EU funded one via Intigriti last year (https://portswigger.net/daily-swig/intigriti-launches-eu-bac...) until the funding was consumed, and I'm literally about to sign the contract on a new permanent one for the Matrix Foundation funded by Element run by YesWeHack.
EDIT: https://matrix.org/security-disclosure-policy/ will get updated when the new bounty programme is live. You can see the history of that page over at https://github.com/matrix-org/matrix.org/commits/master/gats... in terms of wh
Read the rest
en bounties have come & gone over the years.
PRs are welcome against github.com/matrix-org/matrix.org to list clients :)
(it looks like cinny is built on matrix-js-sdk, which also powers element web, so inherits the e2ee support and could inherit voip etc from there).
In Show HN: A web-based matrix client: Cinnyoops, fixed at https://github.com/matrix-org/matrix.org/commit/ae44fd66a71b... - thanks :)
In Combating abuse without backdoorsShowing the 15 most recent of 37 sources. Enable JavaScript to search and browse every indexed mention.