4 ms·
It's different though, extensions are like local apps and deserve persistent storage, while you are talking about how Flash was being used by remote sources. Al
by mckravchyk 4y ago
It's different though, extensions are like local apps and deserve persistent storage, while you are talking about how Flash was being used by remote sources. Also my proposed approach is that this data would be wiped when the extension is removed from the browser - which is what happens for storage.local
- westurner 4y agoSome way to indicate which "WASM contexts" (?) have utilized how much disk space would be great for open source multiple implementations not-Flash, too. From https://news.ycombinator.com/item?id=32953286 https://news.ycombinator.com/item?id=32953286 https://westurner.github.io/hnlog/#story-32950199 https://westurner.github.io/hnlog/#story-32950199 : > - [ ] UBY: Browsers: Vary the {color, size, fill} of the tab tabs according to their relative resource utilization And then that tabs are (sandboxed) subprocesses running as the same user though. Containers may have unique SELinux MCS labels, and browser tab processes probably should too. containers/container-selinux: https://github.com/containers/container-selinux https://github.com/containers/container-selinux https://github.com/kai5263499/awesome-container-security/issues/6 https://github.com/kai5263499/awesome-container-security/iss... > - [ ] ENH,SEC: Browsers: specify per-tab/per-domain resource quotas: CPU, RAM, Disk, [GPU, TPU, QPU] (Linux: cgroups,) Like Flash