Matrix

244 readers
4 users here now

The secure messaging protocol.

founded 10 months ago
MODERATORS
1
 
 

In April, we introduced policy servers to help tackle the spread of harmful content on Matrix. Today, we’re announcing that our implementation is available as open source. Say hello to policyserv v1!

Source code: https://github.com/matrix-org/policyserv

2
3
4
 
 

I'm trying to migrate over one of my smaller Discord groups to Matrix. There are obvious UX shortcomings, but most of them are no big deal and worth it for getting away from an enshittifying platform.

I created a Space, and inside of it created several Rooms. The Rooms are all encrypted, and set "Access: Space members", and were initially set "Who can read history? Members only (since the point in time of selecting this option)".

I thought this should mean that if I create a new Room (with that setting) in my Space, send some messages, and the others later join the Room, they would be able to see the messages. Unfortunately, this did not appear to be the case. Does anyone know what these options actually do?

Unfortunately, the official documentation on the Element website is particularly unhelpful:

From here the options are self-explanatory, simply change as desired to meet your requirements.

The other options, Members only (since they were invited) and Members only (since they joined) are also a bit unclear, in the context of a Space. Is someone "invited" from the moment they receive an invitation to a Space that automatically grants entry to a Room? Had they "joined" from when they joined the Space, or only upon joining the specific Room? (I would assume the latter, but considering my assumption about the first option was evidently wrong, I'm considering anything to be possible.)

5
 
 

Bridges are one of the reasons Matrix is called Matrix: let’s matrix all the networks together! They are key to onboard new users into the network. However, maintaining and operating bridges, in particular to closed, proprietary platforms, is expensive: they need to be kept up to date with any change made by the platform on a regular basis and they’re fiddly to keep up and running.

6
7
8
 
 

I've joined a few communities, but most seem to be pretty dead. Any recommendations would be welcome. Size doesn't matter, all that matters is that they are active.

9
10
 
 

I’m looking for an Icelandic or Irish server for lower latency.

11
12
13
14
15
16
7
submitted 3 months ago* (last edited 3 months ago) by kate@lemmy.uhhoh.com to c/matrix@programming.dev
 
 

minor bug fixes but good version number

17
18
19
20
 
 

The Matrix.org homeserver ^[2]^ is currently experiencing a "major outage" ^[1.1]^ — the server is currently offline ^[1.3]^. The timeline of events is currently (2025-09-03T00:14Z) as follows:

  • On 2025-09-02T17:39Z, an issue with the matrix.org database was reported by status.matrix.org ^[1.3]^.
  • At 2025-09-02T19:01:27Z, the Matrix.org Foundation later reported that the matrix.org secondary database lost its filesystem at 2025-09-02T11:17Z, and subsequently lost its primary database filesystem at 2025-09-02T17:26Z. ^[5]^
  • At 2025-09-02T21:39:25Z, the Matrix.org Foundation reported that they were unable to restore the primary database filesystem, so they are restoring a 55TB database snapshot from the previous night. This restoration is expected to take more than 10 hours to recover the data, then greater than 4 hours to restore the data, then greater than 3 hours to catch up on missing traffic. ^[6]^

References

  1. Type: Website. Publisher: "Matrix.org". Accessed: 2025-09-03T00:18Z URI: https://status.matrix.org/.
    • This is the "system status and incidents" website for The Matrix.org Homeserver ^[4]^
    1. Type: Image.

    2. Type: Image.

    3. Type: Image.

  2. Type: Meta.
    • As seen on status.matrix.org, the site which tracks the system status and incidents of The Matrix.org Homeserver ^[3.1]^, the section "Matrix.org" contains the context: "The Matrix deployment on matrix.org" ^[1.2]^. Within that section, Synapse, which is reported to have the outage ^[1.1]^ is a Matrix homeserver ^[5]^.
  3. Type: Article. Title: "The Matrix.org Homeserver". Publisher: "The Matrix.org Foundation". Accessed: 2025-09-03T00:30. URI: https://matrix.org/homeserver/about/.
    1. Type: Text. Location: ¶3.

      System status and incidents

  4. Type: Website. Title: "Servers". Publisher: "The Matrix.org Foundation". Accessed: 2025-09-03T00:38Z. URI: https://matrix.org/ecosystem/servers/.
    • Type: Image.

  5. Type: Post>Text. Author: "The Matrix.org Foundation" ("@matrix@mastodon.matrix.org"). Publisher: "mastodon.social". Published: 2025-09-02T19:01:27.000Z. Accessed: 2025-09-03T00:46Z. URI: https://mastodon.matrix.org/@matrix/115136245785561439.

    So: the matrix.org database secondary lost its FS due to a RAID failure earlier today (11:17 UTC). Then, we lost the primary at 17:26. We're trying to restore the primary DB FS (which could be fastish), while also doing a point-in-time backup restore from last night (which takes >10h). We believe the incremental DB traffic since last night is intact however. Apologies for the downtime; folks on their own homeserver are of course not impacted.

    • "FS" is presumed to mean "filesystem" from

      […] the matrix.org database secondary lost its FS due to a RAID failure earlier today (11:17 UTC). Then, we lost the primary at 17:26. We're trying to restore the primary DB FS […] ^[5]^

      combined with

      […] we haven't been able to restore the DB primary filesystem to a state we're confident in running as a primary […] ^[6]^

    • "earlier today (11:17 UTC)" is assumed to mean 2025-09-02T19:01:27Z as this post was published on 2025-09-02T19:01:27.000Z.

    • Since no other qualifying information is given, and given its successive nature to 11:17, "17:26" is presumed to mean 2025-09-02T17:26Z.

    • […] Then, we lost the primary at 17:26 […]

      This is presumed to be referring to the primary database filesystem given the context:

      […] the matrix.org database secondary lost its FS due to a RAID failure earlier today (11:17 UTC). Then, we lost the primary at 17:26 […]

    • "DB" is presumed to mean "database" given the following context

      […] the matrix.org database secondary lost its FS due to a RAID failure earlier today (11:17 UTC). Then, we lost the primary at 17:26. We're trying to restore the primary DB FS […]

  6. Type: Post>Text. Author "The Matrix.org Foundation" ("@matrix@mastodon.matrix.org"). Publisher: "mastodon.social". Published: 2025-09-02T21:39:25.000Z. Accessed: 2025-09-03T00:50Z. URI: https://mastodon.matrix.org/@matrix/115136866878237078.

    Sorry, but it's bad news: we haven't been able to restore the DB primary filesystem to a state we're confident in running as a primary (especially given our experiences with slow-burning postgres db corruption). So we're having to do a full 55TB DB snapshot restore from last night, which will take >10h to recover the data, and then >4h to actually restore, and then >3h to catch up on missing traffic. Huge apologies for the outage. Again, folks using their own homeservers are not impacted.

    • "DB" is presumed to mean "database" ^[5]^.
21
22
23
24
25
view more: next ›