Update: Add livematrix client

[awtj8o81ryywg793]

Description

Add livematrix client. Closes #1365.

✔️ Checklist

• Keep this checklist
• Check for common mistakes:
  • Wrap plain URLs in <> to linkify them (learn more).
  • Use the right level of headings: The page title will use a level 1 headings, so your headings should use level 2 and below.
  • Use internal links: when linking to another page on https://matrix.org, use the Zola [label](@/target.md) syntax.
• For blog posts:
  • Verify the date and post ordering on the /blog page, especially for multiple posts on the same day. Prefer UTC format, e.g. 2025-12-01T14:00:00Z for Dec 1st, 2025, 2pm UTC.
  • Set the correct author and category. Browse existing ones at https://matrix.org/author/ and https://matrix.org/category/ to match them.
• If you hold a specific role in relation to the content you are contributing, such as project maintainer or on behalf of a team or organisation, please let us know. See example.
• If your PR is time-sensitive in any way, please mention the attached timeline and context in the PR description.
• Mention any issues related to the PR. Use GitHub keywords as appropriate.
• Your individual commits or pull request is signed off.

[HarHarLinks]

What's its server component about? I'm not sure I would classify this as a regular client (i.e. implementing/targetting compliance with the Matrix C2S API). We might want to consider introducing some new places to put more unusual projects, including this one, ejabberd, cactus comments, ...

The project also doesn't seem too active with the last real commit being in 2022.

[awtj8o81ryywg793]

Quoted from a previous comment:

What's its server component about? I'm not sure I would classify this as a regular client (i.e. implementing/targetting compliance with the Matrix C2S API).

@osousa, would you be able to offer any insight?

Quoted from a previous comment:

We might want to consider introducing some new places to put more unusual projects, including this one, ejabberd, cactus comments, ...

I'd back such a move. If we're to list projects like Cactus Comments separately, then we should list livematrix as such too.

Quoted from a previous comment:

The project also doesn't seem too active with the last real commit being in 2022.

In the absence of actual formal releases, I wonder what the best date is to use in extra.latest_release? I'd assume the date of the most recent yet meaningful commit. However, what would count as being meaningful?

I'll revise extra.latest_release to match the date of c959d3b.

[osousa]

@HarHarLinks i agree, this was a pet project that got way more downloads than i ever expected.

The server (livematrix) in this context is in reality a "client" (A literal client account must be set to intermediate conversations) that operates as a middleman within a server (using the mautrix SDK), whenever someone starts a chat through the live chat in your website, a room pops up in your main matrix account, something like this:

[Chat Browser] <---TLS---> [livematrix] <---e2ee---> [Matrix homeserver] <---e2ee ---> [matrix personal account]

Its a simple concept but works very well (I have 2 gifs in the main repo, if you wait a bit you can see how it works in 30 seconds)

The project also doesn't seem too active with the last real commit being in 2022.

True, but if added to an official (even if secondary one for unusual projects) list , i'll absolutely take on this again ASAP to refactor, refine and improve.

[osousa]

@awtj8o81ryywg793 thank you very much for this, it really would be awesome to be a tiny part of te echosystem, even if in a secondary list for unusual usecases :)

In the absence of actual formal releases, I wonder what the best date is to use in extra.latest_release? I'd assume the date of the most recent yet meaningful commit. However, what would count as being meaningful?

I agree with an "expirity" date based on latest releases, each case is particular, but a project being active does make it more appealing and secure. I am more than willing to revamp and improve the codebase to bring it to new heights feature wise, as being in an official list (even if on the misfits one) would be a huge incentive for me

[awtj8o81ryywg793]

Quoted from a previous comment:

@awtj8o81ryywg793 thank you very much for this, it really would be awesome to be a tiny part of te echosystem, even if in a secondary list for unusual usecases :)

No worries! Thank you for your contribution to the ecosystem!

Quoted from a previous comment:

In the absence of actual formal releases, I wonder what the best date is to use in extra.latest_release? I'd assume the date of the most recent yet meaningful commit. However, what would count as being meaningful?

I agree with an "expirity" date based on latest releases, each case is particular, but a project being active does make it more appealing and secure. I am more than willing to revamp and improve the codebase to bring it to new heights feature wise, as being in an official list (even if on the misfits one) would be a huge incentive for me

It would probably be a good idea to branch this particular point into its own discussion and discuss it in more detail. Perhaps as part of a wider push to better document the information needed for ecosystem projects? See this comment for another reason why I think we should improve on this front.

[osousa]

@awtj8o81ryywg793 yes, very pertinent to have that discussion.

I do think there's merit to livematrix and cactus to be on some list considering some others in the official "integrations" one, recognition is always a major booster :)

It would probably be a good idea to branch this particular point into its own discussion and discuss it in more detail. Perhaps as part of a wider push to better document the information needed for ecosystem projects? See #3052 (comment) comment for another reason why I think we should improve on this front.

Agreed. It could be a nice project to automate housekeeping of Matrix ecosystem, check for latest releases and archiving, notifying the ones with the need for new releases, and maybe tag or remove the ones that were archived. For example, chooj was archived , it seems kaiOS made things difficult to continue for them.