Hacker News Reader

Comment by kodablah | Hacker News Reader

My default browser is one I built, and it hasn't worked with Google auth since they disallowed auth from CEF. Not warned, put captchas in front of, etc but disallowed. Yes the ignorance in HN comments can seem depressing, but I decided to respond to this one anyways.

View on HN

I'm interested in this browser code you speak of...as a fledgling browser builder.

https://cretz.github.io/doogie/ - I don't publish prebuilt releases anymore because I don't really work on it anymore, but I build it for myself with the latest CEF every update. There's a bug here and there, but it is by far more productive for me than other browsers.

But user beware, you can't login to any Google account using it since they disallowed it.

Yours is very edge case though, and the grandparent is rightly pointing out that the headline is a little misleading and comments are generally negative for a positive aspect.

It's a very important edge case. Every new browser, by definition, starts out as a self-compiled project.

If this happened in the 90s, would we ever have had Mozilla? Would tabbed web browsers exist?

This.

If something can't be accessed by any standards-conforming client, then it isn't the web.

>Yours is very edge case though

Not using google chrome is itself an edge case. That's kinda part-and-parcel with monopolistic predatory behaviors.

One man's edge case is another man's line in the sand.

If you think impersonating another browser's user-agent string for compatabililty reasons as a full fledged "real" browser is an edge case ...

You should remind yourself what the Chrome user-agent string actually is.

Have you checked YOUR user agent? This is rediculous.

Reply on news.ycombinator.com