@timofej @lavacat the customer is stuck on Element Classic because it’s a big deployment which needs a lot of time to manage the migration to Element X, hence going on their own timeline for it and needing to suppress that message. Paranoia about unexpected hashes is well deserved, but in this instance it’s benign.