- Focussed on privacy, how?
- So, it's a browser, got some screenshots? What's the ACID test score?
- What rendering engine does it run on?
- Privacy, but no https?
- It's an evolution of the Lobo project apparently?
- So, it's a browser, got some screenshots? What's the ACID test score?
- What rendering engine does it run on?
- Privacy, but no https?
- It's an evolution of the Lobo project apparently?
Conservative defaults and easier to audit since it is implemented in a high-level language / runtime. The runtime (java) needs auditing of course, but that cost is distributed over many projects.
> So, it's a browser, got some screenshots? What's the ACID test score?
For the screenshots you need to scroll down the home-page. ACID test score is probably zero; when we last tried it, it was failing catastrophically.
> What rendering engine does it run on?
We haven't named it. It is a library inside the project. I believe the Lobo project wanted to spawn it of as a separate library called COBRA.
> Privacy, but no https?
It does support https. The bullet point in the roadmap was not clear: we need to take it beyond "it works; let's ship". We need to properly configure the networking library (okhttp) with the correct cipher-suites and fallbacks, for example.
> It's an evolution of the Lobo project apparently?
Yes, our credits page lists all the details: https://gngr.info/doc/credits.html
> process isolation architecture
At the moment, it is module isolation rather than process isolation. It leverages the Security System of the Java Runtime.
Process isolation would help too but that's not on our immediate roadmap for lack of resources.