beacon VS HIPs

I readily admit that cooking the mozconfig is some holy hell, but they do have real-world examples in the repo; did you experience problems at that stage, or it literally wouldn't compile?

And while I haven't tried Ungoogled-Chromium, for unrelated reasons I helped an OSS project build their Brave-derivative in a container, so that may interest you: https://github.com/imperviousinc/beacon/blob/main/Dockerfile The only reason it's not already GitHub Actions for them is the chromium_src is 38GB and GHA cache is capped at 10G, but while digging up the link to that Dockerfile, I was reminded that there is a GHA for the macos build: https://github.com/ungoogled-software/ungoogled-chromium-mac...

While not exactly the same audience, one may find the Dockerfile for building Beacon handy as (a) more code, less talking (b) since Beacon is just a patched Chromium, its dependencies should be a superset of vanilla Chromium

Why are you swallowing "error" from invoking the "reall" tool? That seems like a great way to make contributors really frustrated: https://github.com/imperviousinc/beacon/blob/main/tools/src/...

and again https://github.com/imperviousinc/beacon/blob/main/tools/src/...

This trend of "I'm going to invent some build tool because there are not enough build tools in the world" is evidently leaking out of the node ecosystem

For clarity, I did see that this was inspired by the brave-browser model, but of the ones to draw inspiration from, that's for sure not it given that their CI is closed source and they're trying to use npm in lieu of a more structured, comprehensible system

I like trying out alternate browsers, so congratulations on the launch, and I'll for sure try to build it, but I wanted to draw these to your attention because my experience with software is that error handling is about 80% of the job

There was a time when some used /etc/hosts whilst others used DNS. It was definitely a different time. Resolution issues with Handshake TLDs will easily be solved in time.

There are, however, other reasons why one might think Handshake isn't up to par just yet. Those reasons might be, for example, even though it completes the internet, making it significantly more secure and sovereign, the current implementations including DANE aren't as fast. Of course, this too [1] will be addressed with time.

[1] https://github.com/handshake-org/HIPs/discussions/44