> You're not going to allow JS? Well, at least not in the "main app" of the Web Browser. I'd rather integrate an automateable sandboxing concept for webapps, s

> You're not going to allow JS? Well, at least not in the "main app" of the Web Browser. I'd rather integrate an automateable sandboxing concept for webapps, so that users can choose to e.g. use Instagram or Facebook; but without having to worry that the localStorage and cookie quirks in there can be used for any tracking. In my head it will be probably something along the lines of if "other" is activated, display a little notification under the address bar that asks something like "Do you want to bookmark this as a sandboxed Webapp? [x] Yes [ ] No" which will lead to a new window being opened that is sandboxed with its own WebKit cache and its own WebKit userdata folders etc. Regarding video players: I'm also thinking about integrating youtube-dl (probably as a JS API/runner(?) as my Browser is implemented in node/ES2018) for video websites, but currently I'm not sure whether this will be an endless task to compete with, as a lot of video streaming sites work with mixed transfer channels such as WebSockets or chunked transfer encodings wherein the video chunks themselves are not transferred via 206 Partial Content.