3 ms·
Offline-level privacy is not guaranteed with native apps either, so please don't live under that incorrect notion! If you do not trust the developer of a web a
by osrec 5y ago
Offline-level privacy is not guaranteed with native apps either, so please don't live under that incorrect notion!
If you do not trust the developer of a web app, you can always disconnect from your Wi-Fi, use the app, close the tab and then reconnect to your Wi-Fi.
- quaintdev 5y agoWell at least on Linux I can do something like below with native apps firejail --net=none firefox Disables internet for firefox
- extra88 5y agoSo do that to the browser running the web app after you've downloaded it.
- jeroenhd 5y agoFirewalls have been built into Windows for around 19 years now. There are tons of other options on all other platforms (thought Apple's platforms have more restrictions than others) to prevent outgoing connections. Mobile firewalls seem to use built-in VPN functionality and can often block per domain and per app as well. Web browsers don't come with such a firewall, and they need to be permitted by the system firewall to operate normally. It's technically possible to block outgoing requests with addons and configuration, but that's a pain to get right, especially compared to the simple toggle you can find in most OS firewalls.
- osrec 5y agoYou can throttle (including completely disable) the internet per tab via devtools in most modern browsers...
- jeroenhd 5y agoYou can, and you can also unplug the ethernet cable, but without any user-friendly, ways that are _actually intended_ to do, so it's easy to get wrong. For example: you enable throttling, upload a picture, that picture gets buffered by a serviceworker, you close the tab, therefore closing the dev tools and disabling the throttling you set up, and the serviceworker uploads whatever you resized to the server anyway. Or: the application just tries to upload stuff whenever you open the page, turning the throttling solution into a race between you and your browser. I don't think using dev tools intended to replicate offline-only behaviour are a good way to actually enforce offline-only behaviour.