search

element-hq / element-web

A glossy Matrix collaboration client for the web.
https://element.io
GNU Affero General Public License v3.0
11.13k stars 1.98k forks source link

in a new (verified) session on element, all earlier messages from verified users appear as unverified #14506

Open huguesdk opened 4 years ago

huguesdk commented 4 years ago

description

after logging in on https://app.element.io/, all earlier messages coming from users that have be verified by cross-signing (including myself) appear with a grey shield with a description saying: “the authenticity of this encrypted message can't be guaranteed on this device”.

previously, i added new sessions on riot (web or desktop), and all messages appeared the same. is it something new from element 1.7? since they are verified by my other sessions, could they appear as verified on this new one too? i would prefer all messages to appear the same on all sessions.

steps to reproduce

all earlier messages coming from users verified with cross-signing appear with a grey shield. messages coming from non-verified users appear without a shield.

bildo

it would be better if all messages would appear the same in all sessions.

logs being sent: no

version information

mrjohnson22 commented 4 years ago

This happens on Firefox & Chrome desktop, and in v1.6.8 too. Dup of https://github.com/vector-im/element-web/issues/14323 ?

snowlove commented 3 years ago

I'm having this same issue with the Element client on debian, below I posted a screencap I sent first message from my PC, and then one from my android phone, then got on my laptop and I get this same message on debian-amd64 Element. All devices are using the Element client

screencap_21-09-23_0000

piotrcki commented 3 years ago

The issue also exists in the desktop client provided by flathub.

Any fix method (for users), even a dirty one, would be appreciated.

byquanton commented 2 years ago

/discardsession helped in my Case.

foresto commented 2 years ago

/discardsession helped in my Case.

@byquanton To fix it, did you run /discardsession on the client that was seeing messages with grey shields, or on the client(s) that sent those messages?