Re:LinkedIn sued over allegation it secretly reads Apple use...
by gruez on Saturday July 11, 2020 @11:19AM
(#23802790)
Your solution of "only let the OS initiate pasting" only really works when dealing with os provided text editing widgets. What if an app wants to implement a paste button/gesture? eg. paste and go to url that chrome/safari has, or terminal emulators that paste on control-shift-v rather than control-v, or photo editors that don't really have a text box to "paste" to begin with.
[ Parent
| on HN ]
Re:LinkedIn sued over allegation it secretly reads Apple use...
by pavel_lishin on Saturday July 11, 2020 @11:23AM
(#23802816)
Yes, these are hard problems, but I would prefer that they either be solved - or go without some features - rather than let every app be able to read the contents of my clipboard.
Re:LinkedIn sued over allegation it secretly reads Apple use...
by kshacker on Saturday July 11, 2020 @11:40AM
(#23802968)
Hard problems sometimes (but not always) have simple solutions.
Putting apps copying clipboard up in your face is one such solution and it seems to be highlighting the abusers, no?
Even if an app has a genuine need to copy clipboard, having it in front of user every time will be useful.
Re:LinkedIn sued over allegation it secretly reads Apple use...
by stanmancan on Monday July 13, 2020 @10:09AM
(#23820941)
I know those are probably just a few examples of many but:
Paste and go isn’t a feature worth sacrificing the privacy of your clipboard contents
Terminal emulators, not sure to be honest. Why not stick to traditional cut and paste shortcuts?
Photo editors: nobody said you need a text box to paste to. Set your UI element as “pasteable” or whatever’s needed and let the app handle whatever clipboard contents comes it’s way. If it’s not supported it gets ignored.