3 ms·

I also fail to understand how "lets install native code to run on our OS" results in more security and privacy. The browser is inherently more locked down than

I also fail to understand how "lets install native code to run on our OS" results in more security and privacy. The browser is inherently more locked down than native apps. A Facebook app on your computer can read anything on it without any pesky browser security and privacy features getting in the way.

fnordsensei 5y ago
The Twitter thread isn’t discussing security or privacy. It’s discussing who (effectively) controls web standards right now, and who should do so in the future.
threeseed 5y ago
> A Facebook app on your computer can read anything on it without any pesky browser security and privacy features getting in the way This is not true, at least on OSX. It will ask the user to confirm whether the app is allowed to read/write to key locations e.g. Documents, Photos as well as access key sources of data e.g. Contacts.
- smorgusofborg 5y ago
  That just leads to decision exhausted users saying yes by accident. Traditional browser policy errs more on the side of not making things that are too often dangerous especially if they are rarely beneficial over safer flows. Trying to make progressive web apps do whatever an app can do is basically being bug for bug compatible with bad ideas that sound "convenient".
  - murukesh_s 5y ago
    >decision exhausted users saying yes by accident true this. day before yesterday, i had a webapp ask camera and mic permission and after giving yes to both got a third dialog immediately - i read it but gave yes accidentally before realizing it was permission for push notification - such a dark patterns can be used for exploiting users.
- solarengineer 5y ago
  Unlike on iOS, we are unable to determine access per app at a file level on MacOS (OSX). The permissions are at a folder level. Thus, if we give access to the Documents folder today and then pick a single file, the app is actually free to scour the Documents folder and act on its own (scan the meta data of all the files, upload all the files somewhere, for e.g.)

fnordsensei 5y ago

The Twitter thread isn’t discussing security or privacy. It’s discussing who (effectively) controls web standards right now, and who should do so in the future.

threeseed 5y ago

> A Facebook app on your computer can read anything on it without any pesky browser security and privacy features getting in the way This is not true, at least on OSX. It will ask the user to confirm whether the app is allowed to read/write to key locations e.g. Documents, Photos as well as access key sources of data e.g. Contacts.

smorgusofborg 5y ago
That just leads to decision exhausted users saying yes by accident. Traditional browser policy errs more on the side of not making things that are too often dangerous especially if they are rarely beneficial over safer flows. Trying to make progressive web apps do whatever an app can do is basically being bug for bug compatible with bad ideas that sound "convenient".
- murukesh_s 5y ago
  >decision exhausted users saying yes by accident true this. day before yesterday, i had a webapp ask camera and mic permission and after giving yes to both got a third dialog immediately - i read it but gave yes accidentally before realizing it was permission for push notification - such a dark patterns can be used for exploiting users.
solarengineer 5y ago
Unlike on iOS, we are unable to determine access per app at a file level on MacOS (OSX). The permissions are at a folder level. Thus, if we give access to the Documents folder today and then pick a single file, the app is actually free to scour the Documents folder and act on its own (scan the meta data of all the files, upload all the files somewhere, for e.g.)