Update: Add Extera Next client

[awtj8o81ryywg793]

Description

Add Extera Next client. Closes #3045.

✔️ 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]

We haven't quite formalised this yet, but we need to start tracking asset licenses more properly. Even if we don't end up using that precise tooling contrary to my expectation, I think reuse works well as a stopgap solution as proposed in #2706. Can you add this for the image in this PR?

[awtj8o81ryywg793]

Quoted from a previous comment:

We haven't quite formalised this yet, but we need to start tracking asset licenses more properly. Even if we don't end up using that precise tooling contrary to my expectation, I think reuse works well as a stopgap solution as proposed in #2706. Can you add this for the image in this PR?

Sure! @officialdakari, would you be able to offer some insight here in regard to the license used for logo.svg?

[awtj8o81ryywg793]

Quoted from a previous comment:

Can you add this for the image in this PR?

@HarHarLinks: Which method is preferred for adding REUSE information: within the file itself or in a separate *.license file?

I can see that a separate .license file is used for /bridges/activitypub/logo.svg, so I’ll just mirror that choice for consistency's sake.

[awtj8o81ryywg793]

For the record, while the license for extera-next.svg is not currently noted publicly, after asking in #extera:extera.xyz, I have confirmed with the client's maintainer how the logo is licensed and who created it. I've added extera-next.svg.license, which contains this information. See fd4c00.

[HarHarLinks]

Which method is preferred for adding REUSE information

The REUSE tool usually makes some suggestion I would out of simplicity just follow. I think for images that's the .license file and even though svg is XML under the hood that still seems appropriate as you would usually not easily see the source when opening it. At least I think that was my conclusion with activitypub.

after asking in #extera:extera.xyz, I have confirmed with the client's maintainer how the logo is licensed and who created it

Awesome work! For a clean paper trail it might be helpful to post a link to that message, too ;)

[awtj8o81ryywg793]

Quoted from a previous comment:

Which method is preferred for adding REUSE information

The REUSE tool usually makes some suggestion I would out of simplicity just follow. I think for images that's the .license file and even though svg is XML under the hood that still seems appropriate as you would usually not easily see the source when opening it. At least I think that was my conclusion with activitypub.

My original plan was to include the licence information within the SVG file, given that it is simply XML and not a binary format. However, after observing your approach, I decided to adopt that choice as it enhances consistency and discoverability for both SVGs and non-SVGs.

Quoted from a previous comment:

after asking in #extera:extera.xyz, I have confirmed with the client's maintainer how the logo is licensed and who created it

Awesome work! For a clean paper trail it might be helpful to post a link to that message, too ;)

You can find confirmation of the licence here, and confirmation of the logo's authorship here.