Auto-approve rageshake event capabilities for virtual Element Call widgets

[robintown]

For element-hq/element-call#657

Notes: Automatically request logs from other users in a call when submitting logs
element-web notes: Automatically request logs from other users in a call when submitting logs

---

Here's what your changelog entry will look like:

✨ Features

• Automatically request logs from other users in a call when submitting logs (#9492).

[t3chguy]

How would this work if the clients are reporting to different rageshake servers? Would this be user opt-in?

[robintown]

It is opt-in yes, in that a rageshake request causes a modal to appear inside Element Call prompting the user to add their debug logs to the other user's report, if they wish. Each user's logs are sent to the respective rageshake servers used by their Element Call deployments, which does mean that reports could get split across different rageshake servers, but I don't think this will be a problem in practice.

[t3chguy]

which does mean that reports could get split across different rageshake servers, but I don't think this will be a problem in practice.

It could be for our customers, where the primary report is sent to their own rageshake server but the peer is on an unconfigured Element Desktop which would then send logs to Element's rageshake server exposing info about the client. This needs some kind of warning IMO.

[robintown]

If a customer is on an unconfigured Element Desktop, then rageshakes outside of Element Call are just as capable of leaking info about the client, no? EW's debug logs already give away who the user is interacting with, so is your concern that call-related data is too sensitive to request in this manner?

(For reference, this is the pop-up's exact wording: )

[t3chguy]

Yes, but the modal implies you're sending them to the user, it doesn't have all the regular disclaimers:

[t3chguy]

Oh this is for the rageshake logs within EC only, not including the Element Web/Desktop logs, that's less severe then