#OtterBrowser #OpenSource
pretende recriar os melhores aspectos do Opera 12 e reavivar o seu espírito. Nosso foco é fornecer os recursos poderosos que os usuários avançados desejam, mantendo o navegador rápido e leve. Também aprendemos com a história e decidimos lançar o navegador sob a GNU GPL v3.
https://otter-browser.org/
https://github.com/OtterBrowser/otter-browser
Otter Browser

Otter Browser aims to recreate the best aspects of the classic Opera (12.x) UI using Qt5.

It's a bit of a pity that the only open source browser with proper JPEG XL‌ support currently seems to be #OtterBrowser https://otter-browser.org/
Otter Browser

Otter Browser aims to recreate the best aspects of the classic Opera (12.x) UI using Qt5.

Is #OtterBrowser using chromium now instead of WebKit? Damn…

Mate, fuck google and that chromium shit. They’re killing all non-chrome browsers.

My daily workflow progress on #freebsd :

- #neovim works perfectly, including all plugins  !
- Can't run @Vivaldi, but Otter browser is there for the rescue (and you won't stop me from running it with Qt6 Web Engine 😈) #otterbrowser
- Alacritty is ok, need to try Terminator
- KDE Plasma is ok, but I'm running fvwm3 now for some old school unix feel.

Next challenge are obscure VPNs and Electron 💩 like Slack and Teams.

@dottorblaster @Uilebheist

I use #Firefox primarily at the moment, because it's still the least worst around, but that's not going to last for long, especially with @mozilla's complete inability to actually investing in it to help preserve the open web instead of chasing other questionable endeavors. If didn't rely so heavily on #Blink/‍#Chromium I would be using @Vivaldi instead, or maybe #OtterBrowser https://otter-browser.org/ if it was a bit more mature.

Otter Browser

Otter Browser aims to recreate the best aspects of the classic Opera (12.x) UI using Qt5.

The only browser I actually know of that _can_ support #JpegXL is #OtterBrowser https://otter-browser.org/ —a basically one-man effort to wrap the classic Opera/Presto UX on top of Qt-based web engines— and even then under the very specific conditions that the QtWebKit engine is used, with an environment variable set to enable support for “unsafe” formats (this, BTW, enables support for #MNG too).
Otter Browser

Otter Browser aims to recreate the best aspects of the classic Opera (12.x) UI using Qt5.

the #openWeb today has no champion. It's really as simple as that. The biggest competitor to Google in the user agent space (#Mozilla #Firefox) has no backbone, and innovation/resistance is mostly left to small realities like the partially closed source @Vivaldi or the one-person project #OtterBrowser —that still depend on #Google (or at best #Apple) for the rendering part. This is dramatic. This is even worse than the browser wars of lore.

I really like the UI of #WebPositive on #HaikuOS, but it doesn't yet support video. Videos work in #OtterBrowser. Youtube is sluggish, but I think that's because of my X200. Videos loaded through my local #Invidious instance run well.

Pictured here is an ad company's futile attempt at persuading me to install an incompatible ad delivery system on Haiku.

Why is it that #Falkon and #Konqueror can leverage KIO to provide generic protocol access, and #OtterBrowser can leverage the extensive Qt image format support when using the QtWebKit engine to support more exotic formats (or the new #JpegXL standard), but neither #Chrome nor #Firefox nor #Vivaldi offer comparable extensibility?
I'm sure somebody will try to make a claim about “security”, but I very strongly doubt that's anywhere close to the actual reason.
Maybe I'll submit a patch for the #OtterBrowser