Pull Request checklist

<!-- Before submitting the PR, please address each item -->

• [ ] Tests: This PR includes thorough tests or an explanation of why it does not
• [ ] Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
• [ ] Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

After merge

• [ ] Milestone: Make sure issues finished by this pull request are added to the milestone of the version currently in development.

To download an APK when reviewing a PR:

1. click on Show All Checks,
2. click Details next to "Taskcluster (pull_request)" after it appears and then finishes with a green checkmark,
3. click on the "Fenix - assemble" task, then click "Run Artifacts".
4. the APK links should be on the left side of the screen, named for each CPU architecture

Hi, @ShatteredPixel - my name's Mike Hoye, and I'm Mozilla's Engineering community manager.

About "... all the "promises to welcome my feedback during this transition" were all probably false!", and a selection of other comments you've made to that effect: as much as we value community participation, this is both the public face of our project and our professional working environment, and we're not going going tolerate this ongoing, abrasive, passive aggressive commentary in our issue tracker.

Like all Mozilla forums, we expect participants in our Github repositories to adhere to Mozilla's community participation guidelines:

https://www.mozilla.org/en-US/about/governance/policies/participation/

As well, participants in all our issue trackers - Bugzilla, Github, and others - should read our Bugzilla Etiquette Guidelines:

https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

... and I strongly encourage you to take them to heart if you intend to continue participating in our development processes.

Thank you.

That we aspire to be welcoming hosts does not entitle guests in our house to act as they please, and that's quite enough of that.

If you have something constructive you'd like to add to this discussion and find that you cannot, feel free to contact me directly to discuss it.

Description

I suspect because it's frequently update, running Riot-Web in Firefox Nightly produces a very large number of "sessions". This was not a big deal before e2e rolled out, but this morning I deleted maybe ninety sessions (so much clicking tedium!) in order to validate the remaining real ones.

I think that this consequently breaks validation, somehow, as a result. I'm pinwheeling during the validation phase now, when this did work earlier today.

Steps to reproduce

Using riot-web and a previously-validated Riot.IM on Android, update nightly and reconnect, and try validating a session.

The result pinwheels forever.

I'm using Riot-Web current, Riot.IM on Android presumably also current (on Android One) and can reproduce at will.

After going to to https://desktop.jitsi.org/Main/Download and pulling the Windows clients, it looks like the client linked there is out of date. (I certainly haven't been asked for my AIM or ICQ accounts in quite some time.)

The Windows download links should probably point to the Electron client instead, which works a treat: https://github.com/jitsi/jitsi-meet-electron

Thank you.

Very good!

Hmmmm. I have attempted to do so, but don't see them....

<!-- Please report security issues by email to security@matrix.org -->

<!-- This is a bug report template. By following the instructions below and filling out the sections with your information, you will help the us to get all the necessary data to fix your issue.

You can also preview your report before submitting it. You may remove sections that aren't relevant to your particular case.

Text between <!-- and --​> marks will be invisible in the report. -->

Description

Matthew and I are participating in a conversation in which he is unable to see my message decrypted, but I'm quite able to see his.

Steps to reproduce

I'm using both RiotX and the Riot-Web to participate in this conversation, same user account on both. Messages from the web client are undecryptable to Matthew, RiotX works fine. I can see everything decrypted on both clients.

Describe how what happens differs from what you expected.

<!-- Please send us logs for your bug report. They're very important for bugs which are hard to reproduce. To do this, create this issue then go to your account settings and click 'Submit Debug Logs' from the Help & About tab --> Logs being sent: yes/no

<!-- Include screenshots if possible: you can drag and drop images below. -->

Version information

Riot-web current (Firefox Nightly, as of today) and RiotX current as of today.

For the web app:

• Browser: Firefox Nightly, current as of today.
• OS: Windows 10 current.
• URL: chat.mozilla.org