Re:Swift-Keylogger – Keylogger for MacOS written in Swift us...
by zaksoup on Tuesday October 17, 2017 @02:11AM
(#15489013)
I'm not sure I buy that requiring user opt-in to camera access is why the Mac app ecosystem is is much larger than that of iOS. Can you elaborate on what apps/innovations would become impossible because of a mandatory opt-in? I cannot think of any...
[ Parent
| on HN ]
Re:Swift-Keylogger – Keylogger for MacOS written in Swift us...
by sametmax on Tuesday October 17, 2017 @05:30AM
(#15489651)
Everything that is either very low level or is used for deep introspection of other parts of the system.
I'm not against sandboxing, but if there should be a way to say i know what i'm installing, go with it. Otherwise you will say good bie to new ways of debugging, alternative drivers, unusual way of routing network packets, innovative UI interactions that are not part of the standards widgets, or anything you haven't think of yet.
The computing experience you have today is the result of all the stuff we fiddle with for the last 30 years because it was allowed to. It would be foolish thz big players invented most of it.
Re:Swift-Keylogger – Keylogger for MacOS written in Swift us...
by icebraining on Tuesday October 17, 2017 @03:17AM
(#15489213)
The problem with an opt-in system is that you have to sandbox the whole app (otherwise, evading the opt-in would be trivial) and therefore lock out any advanced access not explicitly listed as an opt-in permission.
If you want an example, there's F.lux, which doesn't work (without rooting) on Android and iOS.