Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

per-message e2e info should tell you which devices you encrypted a message for. #3019

Open
ara4n opened this issue Jan 21, 2017 · 3 comments
Open

per-message e2e info should tell you which devices you encrypted a message for. #3019

ara4n opened this issue Jan 21, 2017 · 3 comments
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement X-Needs-Design

Comments

@ara4n
Copy link
Member

ara4n commented Jan 21, 2017

now we have all the blacklist-unverified and blacklisting stuff, it'd be super-useful for the user to actually be able to ask Riot which set of devices a given message was actually targeted to
@ara4n
Copy link
Member Author

ara4n commented Jan 21, 2017

would this not also help with debugging UISIs a bunch?

@ara4n
Copy link
Member Author

ara4n commented Jan 22, 2017

for instance, whilst testing the blacklist-unverified stuff, the only way i can see if it's working other than actually running target clients is to look at JS console logs. this seems very wrong.

@richvdh
Copy link
Member

richvdh commented Jan 22, 2017 •
edited
Loading

I thought we had a bug for this already, but yes this is definitely needed.

Possible I was thinking of #2494

@richvdh richvdh mentioned this issue Feb 9, 2017
Closed
@turt2live turt2live added X-Needs-Design O-Uncommon Most users are unlikely to come across this or unexpected workflow and removed P2 labels Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE O-Uncommon Most users are unlikely to come across this or unexpected workflow T-Enhancement X-Needs-Design
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jryans @turt2live @ara4n @richvdh