idea

make DistBB but in the browser, with WebRTC
all data = cookies

>>18
I guess another solution is to introduce the concept of privileges so an application can run with the minimal access to you machine required. Games can run in file system jails with only access to audio, video, and key events within their window. Something like that could help. But there's always the danger of jail escaping. Just like a javascript exploit in a browser finding a way to execute arbitrary code on the victim's machine. If it's open source, exploit attempts will be obvious to see. All it takes is one programmer to see the source, spot the suspicious code, and start a pr storm on it online.

2nd thing

what the fuck is this and why did you link to it?

yeah, that'd be nice. While that isn't here, there's still sandboxing, but casuals won't use it. JS is actually pretty secure too, I think all it can do is either lag your browser, CSRF if the target site doesn't use sessions correctly, or XSS if it doesn't escape html as it should. But yes, nothing is immune to newfound exploits

what the fuck is this and why did you link to it?

online curl, you can see any page's source code before opening it

>>20
people are terrible at writing secure interpreters. They'll never be secure. Sandboxes can still be escaped.

I can't believe that actually exists. I suppose it could be used as a proxy with the right userscript.