I did install Dooble web browser on beta 6 because it works fast on my old HP laptop but I cannot login on the forum - there are no options. I did test it on browseraudit.com and I got it
398 passed and 33 warnings which is the same as I got with Firefox on FreeBSD with arkenfox user.js.
Test results here, Iceweasel: 400 passed, 31 warnings
Epiphany (50.4) 402 passed, 29 warnings 
Maybe request webserver admin to see if webserver can support Dooble…
This isn’t a problem with the webserver,but the Discourse forum software.
And the developers there don’t see it as a problem but a feature.
They’re trying very hard to lock out slightly outdated browsers that would otherwise work just fine or with minimal bugs.
I’ve had that happen multiple times with Basilisk browser.
There were even custom userscripts to trick Discourse browser detection and prevent it from locking out Basilisk,and after each Discourse update,it was broken again.
Feel free to complain to the Discourse developers to stop that hostile behavior.
Agree with @nipos here… Discourse is an horrible platform…
If you are using 64 bit version of Haiku, try Firefox, but if your hardware is old, performance will be awful too. Under 32 bit, the only browser that (barely) works with the forum is WebPositive. Not a pleasant experience, however (scroll is slow, typing have noticeable input lag, etc)
In my experience with dooble a couple of years ago, it couldn’t log in on a number of sites, maybe any. That would be an issue with the cookies these sites use for authentication, I imagine. Behavior was inconsistent - exact symptoms depended on the site, other people claimed to be able to get it to work. But it was clearly messed up in a way that I have never seen before.
Dooble 2026.08.21
Results: 399 passed and 32 warnings
If you go into Settings, you can now change the Global User Agent:
“Mozilla/5.0 (X11; Haiku x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/5.15.18 Chrome/87.0.4280.144 Safari/537.36 Dooble/2026.08.21”
Still tinkering with certain websites to get them to work with the browser.
Wasn’t there some offending file that did this? can we patch this out on our end?
Yes,that’s the file: https://discuss.haiku-os.org/assets/browser-detect-eda0902d.js
Adding it to the adblocker filter list makes Discourse try to work in every browser.
As a negative side-effect,you’ll get a blank white page in browsers that are really technically incompatible,rather than a read-only view (try Otter Browser for example).
Instead of removing/blocking that file completely,it probably makes sense to remove the CSS.supports() checks where missing support only results in styling issues,but keep the checks for Javascript functions where missing support breaks the whole page as-is.