Yeah this is straight up wrong from my practical testing

From the talk: It doesn’t need MAS as that’s built in, and calls work.

This is not developed by the foundation or Element.

I send my grafana alerts via Matrix (selfhosted) and Email (paid service), so either way it reaches me. Has worked out well enough so far

https://blog.metabrainz.org/2026/09/10/picard-3-release-candidate-2/ it gets closer!

We’re still developing it! New major version soon!

That is a painfully AI written article, do you have a better source?

Wildly ambitious editing timeline in that chart there 😔

Developer here, this is Code By Humans

Works ✅

If you want an easier Matrix self-hosting experience https://continuwuity.org/ is a good option :3

Yeah that post is 5 years old, I would think a lot of that has changed by now

Edited, ty

But yeah the support room is more likely to be able to help debug

Given nginx is logging a client disconnect error and curl succeeding, it sounds like the issue is in the client. Trying different clients and/or browsers may reveal the problem.

Moderation tools are powerful but seperate to the server. Asgard.chat offers some hosted options, but meowlnir, Draupnir and policyserv are the usual tools.

Element X doesn’t support the traditional way of making accounts, try use cinny.in to make an account in the browser and then log in with element X. Fluffychat should also present a “create a new account” button above the login button. Make sure to follow instructions in the console for registering the first account.

The federation port not being accessible won’t break local functionality but will break federation, so you won’t be able to talk with other people. Either change the configured port in the well-known file or forward the port via your reverse proxy.

I’d suggest joining the support room via an alt account, you’ll get faster responses.

Posting a 3 coming on 4 year old post, of course it’s not going to be accurate any more. And that’s for the points that aren’t just fear mongering in the first place.

• Redaction exists and removes the contents of events, while keeping metadata needed for the functionality of the room.
• Any program can handily ignore deletion - back when I used discord I had a handy plugin to view deleted messages for moderation, for example.
• Badly behaving servers can behave badly and it will not affect correctly behaving ones, they will apply redactions as expected.
• “Room joins leaves, etc are permanently a part of the room’s history” well yeah, that’s expected. You can upgrade a room if you want to start from scratch there.
• We can now prevent spammers from ever entering the room with join gates, among other things - but if you’re not running a big public community, then our antispam tech is probably completely unnecessary for you
• Currently, timeline ordering is defined by the server. Continuwuity uses a simple, understandable and secure scheme - it orders by the time your server receives messages.
• As per the above point, this doesn’t affect Continuwuity
• That’s a tradeoff of allowing public rooms with tens of thousands of people in the same app as end-to-end encrypted DMs. Good job Matrix isn’t really meant to be a Signal competitor.
• this point was relevant… Four years ago. You’ll only encounter issues if you’re using a broken server or ancient client now.
• “Started trying to filter recently” god you can tell how outdated this is
• It defines it pretty damn strictly now, and this isn’t an issue in practice for a very long time.
• Mmm yeah I don’t think you’re particularly likely to experience one of those in day-to-day usage.
• and this is false lol
• Ancient and fixed
• False. There are many ways to do this.
• I’ve never encountered this, and it’s impossible in new rooms versions.
• Aand outdated by years again
• see above
• see above
• see above

Because it’s not true, and hasn’t been true since 2018 at the latest.

Depends on the client you use. Sable has loads of features like that.