4 ms·
Sorry the original tweet didn't call out Apple. Tweet 2/3 in the thread does (https://twitter.com/breckyunits/status/1576794330580148225 https://twitter.com/bre
by breck 4y ago
Sorry the original tweet didn't call out Apple. Tweet 2/3 in the thread does (https://twitter.com/breckyunits/status/1576794330580148225 https://twitter.com/breckyunits/status/1576794330580148225). It didn't click for me until a little later that Apple went out of its way to explicitly add an API to disable some basic functionality in macOS. The end result is the user expects one thing to happen (a screenshot) and instead get a black screen.
A very unethical decision, IMO.
- Someone 4y agoThat tweet doesn’t mention what API that is, and Google doesn’t give it to me. The best I can find (via https://stackoverflow.com/questions/18680028/prevent-screen-capture-in-an-ios-app https://stackoverflow.com/questions/18680028/prevent-screen-...) is https://developer.apple.com/documentation/uikit/uitextinputtraits/1624427-issecuretextentry https://developer.apple.com/documentation/uikit/uitextinputt...: “A Boolean value that indicates whether a text object disables copying, and in some cases, prevents recording/broadcasting and also hides the text“ ⇒ People seem to creatively use this to hide views shown behind text views from screenshots. I wonder what those “in some cases” are, though.