What part of the headline suggests the feature is mandatory? Assuming its mandatory doesn’t pass the critical thinking “sniff test” because what is sensitive is purely subjective. Microsoft has no way of knowing what data you consider sensitive. As in, there’s no way Microsoft could make it mandatory on only “sensitive” data.
That’s a charitable reading, and likely justified by the article, but based only on the phrasing, it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data. Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data.
Hang on. If you’re rejecting rational use cases that companies use Teams for, then your assumption must be that Microsoft will block ALL screen capture when a teams meeting is occurring whether its of the Teams meeting content being shared or not. As in, even the presenter would be blocked from doing screen captures of their own system. Why isn’t that your conclusion?
Why are you, again, from the headline only, assuming that screen capture would mandatory for just content shared to you by a Teams presenter? You chose a middle ground, but why didn’t you choose full blocking?
Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
So are you adapting yours back now because yours was proven wrong?
Well, ‘proven wrong’ is a bit of a stretch. ‘will soon block screen capture’ doesn’t leave a lot of wiggle room, but also isn’t that crazy to read into it that maybe it would block screen capture on the presenters screen… especially if you grant that it might only have control over the teams portion of the screen. I’ve had it black out windows on my own machine even when not presenting.
But further than that, it’s not fair to say everything has to be read only from the most or the least charitable viewpoints. Context is a thing and if you’re even a little bit familiar with the history of software enshittification, it’s reasonable to assume that an uncharitable reading is fair without assuming the app will now melt your computer for spare parts if you try something that is disallowed. ‘As shitty as we can get away with’ might be a good rule of thumb.
What part of the headline suggests the feature is mandatory? Assuming its mandatory doesn’t pass the critical thinking “sniff test” because what is sensitive is purely subjective. Microsoft has no way of knowing what data you consider sensitive. As in, there’s no way Microsoft could make it mandatory on only “sensitive” data.
“Microsoft” “will” “block”
Those parts of the title.
The source though indicates that it will be a Feature and it even has its own name. Sadly it doesn’t point out that it will be optional.
Additionally you can see in the comments of the article that people think this will be mandatory.
That’s a charitable reading, and likely justified by the article, but based only on the phrasing, it’s just as likely to read that as assuming Microsoft will block all content in order to ensure the safety of sensitive data. Sniff tests have to be adapted when things tend to stink in general, or companies regularly try to cover up their smell.
Hang on. If you’re rejecting rational use cases that companies use Teams for, then your assumption must be that Microsoft will block ALL screen capture when a teams meeting is occurring whether its of the Teams meeting content being shared or not. As in, even the presenter would be blocked from doing screen captures of their own system. Why isn’t that your conclusion?
Why are you, again, from the headline only, assuming that screen capture would mandatory for just content shared to you by a Teams presenter? You chose a middle ground, but why didn’t you choose full blocking?
So are you adapting yours back now because yours was proven wrong?
Well, ‘proven wrong’ is a bit of a stretch. ‘will soon block screen capture’ doesn’t leave a lot of wiggle room, but also isn’t that crazy to read into it that maybe it would block screen capture on the presenters screen… especially if you grant that it might only have control over the teams portion of the screen. I’ve had it black out windows on my own machine even when not presenting.
But further than that, it’s not fair to say everything has to be read only from the most or the least charitable viewpoints. Context is a thing and if you’re even a little bit familiar with the history of software enshittification, it’s reasonable to assume that an uncharitable reading is fair without assuming the app will now melt your computer for spare parts if you try something that is disallowed. ‘As shitty as we can get away with’ might be a good rule of thumb.