> I have asked them to do an anonymous survey of users to ask what action they would take if they were blocked from taking screenshots and users universally say they’d take a picture of their screen with their phone.

Everyone knows this. You don’t need this survey (which surely was a real thing that actually occurred and not something you just conveniently imagined for this argument, right?) to tell you that.

It’s literally written in the linked article.

We know. There are ways around it. But it’s friction, and friction has value. People know it’s not perfect, but it’s another reminder that people aren’t supposed to be doing it.

It’s literally not friction. The average user has no clue how to take a screenshot. They all know how to take a picture with their phone.

It’s a solution searching for a problem it can’t solve.

Friction implies you’re stopping a user from taking an action they consider the easiest way to solve the problem. Since you think I “invented” the survey, I invite you to ask all of you non technical friends and family how they would go about capturing an image of their computer screen if they needed to quickly show you a copy of what they’re looking at.

I absolutely guarantee you that taking a picture with their phone will be the winner by an order of magnitude.

All you’ve shown that there is at least one incredibly out of touch person that “works in security”. Absolutely green behind the ears.

Also, the screenshot stays within your corporate network, whereas the photo is immediately backed up to iCloud, sent over messenger, etc.

The friction pushes the flow into something even worse — while not actually changing the behavior.

Taking out a camera to make a picture is pretty noticeable in a meeting with few participants. The standard way to use a phone camera involves lifting it pretty close to your eye level. Other participants could literally shout to please stop photographing the screen. It will be also very visible who was trying to do so.

Yes, somebody who's clever enough would keep the camera away from view, and maybe would try several times first to hold it in a way that gives a good view of the screen, etc. But this is out of scope, it's a clear malicious intent, when we could expect much more sophisticated means.

I'm not sure what scenario you're imagining, but Teams is mainly for remote meetings.

I think he meant that in a meeting of few people, all with cameras on, a participant can't simply raise his phone and take a picture.

People turn their cameras off for a few minutes all the time. And it’s not like people can’t fiddle with their phones out of frame.

> I would FAR prefer recording who took a screenshot than blocking it as a presenter.

It would be surprising if Teams does not already capture that kind of event in its user activity event trail[0].

The amount of privacy-invasive capturing and reporting that Teams does is so staggering that it can probably rival surveillance that of North Korea on its own citizens.

[0] https://learn.microsoft.com/en-us/microsoft-365/admin/activi...

How exactly did you phrase the question? It's one thing to ask about a purely technical limitation. A different (and more relevant) question would be: if law or company rules prohibit you from recording or taking screenshots in some specific circumstances, and software is helping enforce that, what would you do?