3 ms·
In order to know when you should enable the paste option. It can be an elegant design choice, but also a design choice that appears to be or is an abuse of pri
by csa 6y ago
In order to know when you should enable the paste option.
It can be an elegant design choice, but also a design choice that appears to be or is an abuse of privacy.
- landryraccoon 6y agoCouldn't IOS just have a peek API that tells the application if the clipboard is empty or not without revealing it's contents?
- RandallBrown 6y agoThey've had one for several years. https://developer.apple.com/documentation/uikit/uipasteboard/1829416-hasstrings https://developer.apple.com/documentation/uikit/uipasteboard...
- deleted 6y ago[deleted]
- m0xte 6y agoPerhaps the destination should define whether or not you can paste into it and the OS can provide that option instead. This looks like a violation of “tell, don’t ask”.
- beamatronic 6y agoI should be able to paste into specific GUI elements that allow pasting. The application presenting the GUI element to me should be blind to whether I typed that data, or pasted it into there.
- creato 6y ago> It can be an elegant design choice, but also a design choice that appears to be or is an abuse of privacy. For decades, all programs running on your computer had access to the clipboard. A primary intended purpose of the clipboard is precisely to share information between different programs. Maybe it is in fact a security issue that should be rethought, but calling it an abuse of privacy seems extreme.
- xvector 6y ago> calling it an abuse of privacy seems extreme. Absolutely not, this was a terrible decision to begin with. Users copy sensitive things to the clipboard all the time.