I'm really going to have to set aside a year and find some funding to do the browser, aren't I? 😝
Conversation
This Tweet was deleted by the Tweet author. Learn more
The problem is that they're all either forks of the same codebases or toys, and none are built around an adversarial model of the content they're interacting with. That's not something you can tack on. Has to be built-in from day zero.
1
4
This Tweet was deleted by the Tweet author. Learn more
So have I. I know how to see problems that can't be solved in existing implementations and this is the deepest one I've ever seen.
1
This Tweet was deleted by the Tweet author. Learn more
All the existing good work has come from Tor Browser, but it's built on a foundation with no capability to cut off fingerprinting entirely. To do that you need 100% determinism.
This Tweet was deleted by the Tweet author. Learn more
No, deterministic runtime behavior for code hosted by the browser (js).
This Tweet was deleted by the Tweet author. Learn more
This Tweet was deleted by the Tweet author. Learn more
Used to be turned on in -CURRENT when it was being tested, but it has been turned off now that there's another branch where it's used, whereas -CURRENT has more need to have the revision printed in uname (which is one of the things that make a build irreproducible).
1