You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, a public channel I get email notifications for has been switched to encrypted (but still public). The result is weird: the messages just say "an encrypted message", and I seem to get a notification about every new message, even though notifications are configured only for messages mentioning me. I can understand why the server wouldn't be able to see or filter the messages (although it is a public channel so in theory some kind of system account should be able to join and see the messages) but it is still disorienting, and even more so - I imagine - for someone who doesn't know much about the concept of E2EE. At a minimum the notification email should contain some sort of explanation about what's going on.
The text was updated successfully, but these errors were encountered:
The whole point of E2EE is that the server can't read the messages. Also, it is pointless to enable encryption in a public room - if someone wants to read the messages they can just join the room. There should be a dialog to warn you about that
That being said, I agree - there should probably be some info about this in the email.
Recently, a public channel I get email notifications for has been switched to encrypted (but still public). The result is weird: the messages just say "an encrypted message", and I seem to get a notification about every new message, even though notifications are configured only for messages mentioning me. I can understand why the server wouldn't be able to see or filter the messages (although it is a public channel so in theory some kind of system account should be able to join and see the messages) but it is still disorienting, and even more so - I imagine - for someone who doesn't know much about the concept of E2EE. At a minimum the notification email should contain some sort of explanation about what's going on.
The text was updated successfully, but these errors were encountered: