Thanks for the input @Jeffrey Yasskin <[email protected]> .
> Do you have an Alternatives Considered section somewhere > <https://github.com/screen-share/capture-all-screens/blob/main/explainer.md> > that > explains why the bikeshed is painted this color? e.g. this could be > `getMultipleDisplayMedia()` and be identical to `getDisplayMedia()` except > that it returns a sequence<> and lets the user pick more than one screen to > present. The UI could have a checkbox for "all screens" if that's a common > option. There could be an enterprise policy to auto-accept requests from a > particular origin, but such an API could also be useful on the open web, as > Elad argued in https://github.com/w3c/mediacapture-screen-share/issues/204 > . > I added a paragraph with the considered alternative in the explainer here <https://github.com/screen-share/capture-all-screens/pull/19>. Do you want to work with your screen always being recorded? > > > There are many factors that go into choosing an employer, and some > drawbacks can be offset by other benefits. Depending on the opportunities > available to me, I could definitely see myself accepting employment at a > company which recorded *their* screen while I was using it - provided that > I was properly informed! And this is what Simon's API offers over > alternatives - whereas native apps running on Windows, Mac or Linux can > record a user without their knowledge, an application using the API > proposed here would be forced to announce itself to the user. > > Would I have preferred a world where no employer ever recorded their > employees? Probably. But I don't think we can build this world. So I prefer > this lesser evil. > > That said, one thing that appears to be missing from the current spec, is > a guarantee that users would be informed *in advance* of recording. I would > advocate adding this requirement before proceeding. > +1 to what @Elad Alon <[email protected]> said. I added a draft for the improvement suggested by @Elad Alon <[email protected]> here <https://github.com/screen-share/capture-all-screens/pull/15> . Best, Simon On Tue, May 23, 2023 at 2:10 PM Elad Alon <[email protected]> wrote: > Do you want to work with your screen always being recorded? > > > There are many factors that go into choosing an employer, and some > drawbacks can be offset by other benefits. Depending on the opportunities > available to me, I could definitely see myself accepting employment at a > company which recorded *their* screen while I was using it - provided that > I was properly informed! And this is what Simon's API offers over > alternatives - whereas native apps running on Windows, Mac or Linux can > record a user without their knowledge, an application using the API > proposed here would be forced to announce itself to the user. > > Would I have preferred a world where no employer ever recorded their > employees? Probably. But I don't think we can build this world. So I prefer > this lesser evil. > > That said, one thing that appears to be missing from the current spec, is > a guarantee that users would be informed *in advance* of recording. I would > advocate adding this requirement before proceeding. > *Simon Hangl* Software Engineer [email protected] Google Germany GmbH Erika-Mann-Straße 33 80636 München Geschäftsführer: Paul Manicle, Halimah DeLaine Prado Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich bitte wissen, dass die E-Mail an die falsche Person gesendet wurde. This e-mail is confidential. If you received this communication by mistake, please don't forward it to anyone else, please erase all copies and attachments, and please let me know that it has gone to the wrong person. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEdDZo9N7Bm5GJVPiOkf7NUpxa5_7hUCsmiuEzdTJN%2BfXwq1Gg%40mail.gmail.com.
