Live data from Hacker News

Otter Browser

otter-browser.org

1–10 of 98 posts

Re: Otter Browser

#2
This seems actually viable. And those weekly updates let us know "It's Alive!!" not some zombie. I'm going to make an effort on using this.

I'm currently using a Firefox fork but the maintenance is a little rough and I get conflicts with upstream sometimes that are hard (for me) to resolve.

Re: Otter Browser

#5
post #3

Seems to be a nice UI around QtWebEngine which is based on WebKit or blink (chromium), with quite a solid effort through the years.

Depending on your build, you have a choice between:

- QtWebKit: https://wiki.qt.io/Qt_WebKit

- QtWebEngine: https://wiki.qt.io/QtWebEngine

(I realized I replied to a previous version of the parent comment)

Re: Otter Browser

#6
I'm not well versed enough in the Browser Wars to say one thing or another about except this:

I like the name.

It lends it self to saying "I use the Otter browser" which is not just a great pun but the pun on 'other' defines what Otter is, the "other" browser. The web needs independent browsers. We need to get rid of the idea that websites are designed to work on any one technology. They should work on any browser that supports the standards.

Re: Otter Browser

#7
post #3

Seems to be a nice UI around QtWebEngine which is based on WebKit or blink (chromium), with quite a solid effort through the years.

> chromium

Are there any Google risks for being chromium-based? Honest question here.

Re: Otter Browser

#8

I'm not well versed enough in the Browser Wars to say one thing or another about except this: I like the name. It lends it self to saying "I use the Otter browser" which is not just a great pun but the pun on 'other' defines what Otter is, the "other" browser. The web needs independent browsers. We need to get rid of the idea that websites are designed to work on any one technology. They should work on any browser th…

> The web needs independent browsers...[websites] should work on any browser

Unfortunately, independence ends with the choice between WebKit (QtWebKit) or Blink (QtWebEngine), albeit with a faithful Opera 12-like interface that's less resource hungry than Vivaldi. Otter is still in development and it shows in some rough spots and occasional crashes.

Re: Otter Browser

#9
post #7
post #3

Seems to be a nice UI around QtWebEngine which is based on WebKit or blink (chromium), with quite a solid effort through the years.

> chromium Are there any Google risks for being chromium-based? Honest question here.

As noted in a sibling to your comment, there's a choice between WebKit and Blink (your build allowing).

Here's QT's note addressing your concern in QtWebEngine: https://wiki.qt.io/QtWebEngine#Relationship_to_Chromium

    Auxiliary services that talk to Google platforms are stripped out

Re: Otter Browser

#10
post #7
post #3

Seems to be a nice UI around QtWebEngine which is based on WebKit or blink (chromium), with quite a solid effort through the years.

> chromium Are there any Google risks for being chromium-based? Honest question here.

I can't find a source, but I know Brave has had upstream Google issues in the past. Unfortunately, from what I've heard, Gecko is not very developer friendly, so Google is pretty much the only option.
Post reply on HN