Pixls.us forum / Discourse: Browser not supported [Solved]

Thad E G · Unread post by **Thad E G** » 2024-01-04, 08:17

Operating system: Linux Mint 21
Browser version: 32.5.2
32-bit or 64-bit browser?: 64
Problem URL: https://discuss.pixls.us/
Browser theme (if not default):
Installed add-ons:
Installed plugins: (about:plugins):

If possible, please include the output of help->troubleshooting information (as text): below

Unfortunately, your browser is unsupported. Please switch to a supported browser to view rich content, log in and reply.

This happened yesterday. I had previously used the pixls.us forum daily without problem

Ironic that an open-source forum seems to be blocking an open-source browser whilst welcoming the commercial big guns

Discourse supports the latest, stable releases of all major browsers and platforms:
Microsoft Edge
Google Chrome
Mozilla Firefox
Apple Safari
Additionally, we aim to support Safari on iOS 15.7+.

https://www.discourse.org/about#browser

Any tweak suggestions?

troubleshooting information:

Kerebron · Unread post by **Kerebron** » 2024-01-04, 08:32

Add this rule to your adblocker:

Code: Select all

https://discuss.pixls.us/assets/browser-detect-*

Thad E G · Unread post by **Thad E G** » 2024-01-04, 08:56

Kerebron wrote: ↑
2024-01-04, 08:32
Add this rule to your adblocker:

Many thanks! that is working

Bilbo47 · Unread post by **Bilbo47** » 2024-01-09, 22:54

Kerebron wrote: ↑
2024-01-04, 08:32
Add this rule to your adblocker:
Code: Select all
https://discuss.pixls.us/assets/browser-detect-*

Okay but, might you have time to mention what the overall idea of this solution is? Like, the "adblocker" answer makes me think we're setting the browser to reject aka not-request resources matching the wildcard expression. (I use Adblock Latitude in one browser, where the expressions have a different syntax.) But the question seems to be about the site rejecting non-accepted browsers, which this denial of service is often based on the User Agent string.

So how can an adblock entry affect per-site browser acceptance? Would this trick of not-requesting certain assets also work for other sites? How come the answer is not "set up a per-site UA string to spoof an accepted browser"? Thanks for any illuminating detail you can add.

Unread post by **Moonchild** » 2024-01-09, 23:27

Bilbo47 wrote: ↑
2024-01-09, 22:54
Okay but, might you have time to mention what the overall idea of this solution is?

it's pretty simple.
Discourse uses that browser detection script to basically discriminate against any browser they "don't want" and hard block. By blocking the detection script, it keeps the censor at bay. and you can continue as-usual.

Kerebron · Unread post by **Kerebron** » 2024-01-10, 07:09

What Moonchild said.

Bilbo47 wrote: ↑
2024-01-09, 22:54
Would this trick of not-requesting certain assets also work for other sites? How come the answer is not "set up a per-site UA string to spoof an accepted browser"?

For any site that is kind enough to use a separate script for browser detection - sure. As long as they use this method, it's much easier and simpler to avoid being identified altogether, than playing whack-a-mole with UA strings.

Bilbo47 wrote: ↑
2024-01-09, 22:54
I use Adblock Latitude in one browser, where the expressions have a different syntax.

I use ABL, as well, and this rule works fine.

Lucio Chiappetti · Unread post by **Lucio Chiappetti** » 2024-01-10, 14:38

I am not familiar with the syntax of ABL (which I use out-of-the-box) but just adding a plain URL like that (for another forum) works nicely.

Bilbo47 · Unread post by **Bilbo47** » 2024-01-10, 23:41

Kerebron wrote: ↑
2024-01-10, 07:09

Bilbo47 wrote: ↑
2024-01-09, 22:54
Would this trick of not-requesting [the browser-detection javascript] also work for other sites?
For any site that ... uses a separate script for browser detection - sure

Thank you! This works here as well, and I expect it will also work for other sites using the same forum-ware.

frostknight · Unread post by **frostknight** » 2024-01-22, 02:49

Kerebron wrote: ↑
2024-01-04, 08:32
Add this rule to your adblocker:
Code: Select all
https://discuss.pixls.us/assets/browser-detect-*

How can I prevent browser detect on a multi website level, for ublock origin.

This doesn't work on ublock origin as far as I know.

redyoshi49q · Unread post by **redyoshi49q** » 2024-03-08, 04:06

Kerebron wrote: ↑
2024-01-04, 08:32
Add this rule to your adblocker:
Code: Select all
https://discuss.pixls.us/assets/browser-detect-*

I would actually recommend the following code instead (assuming that the risk of a false positive block is tolerable):

Code: Select all

/assets/browser-detect-*

This should, in theory, work on all sites that use Discourse for a forum at the root level of their website (and don't change the name of that script) without having to list each one out specifically (I ran into this issue recently with the Framework community forums, but I've run into it previously on other websites, too; I finally got around to looking for a workaround). Adding an extra asterisk at the beginning would also catch Discourse instances hosted in a subdirectory of a domain, but the risk of a potential false positive block would increase.

Thanks for the idea of using an adblocker for this; it's not something that would have occurred to me to try.

miroR · Unread post by **miroR** » 2024-03-21, 18:41

redyoshi49q wrote: ↑
2024-03-08, 04:06
I would actually recommend the following code instead (assuming that the risk of a false positive block is tolerable):
Code: Select all
/assets/browser-detect-*
This should, in theory, work on all sites that use Discourse for a forum at the root level of their website (and don't change the name of that script) without having to list each one out specifically (I ran into this issue recently with the Framework community forums, but I've run into it previously on other websites, too; I finally got around to looking for a workaround). Adding an extra asterisk at the beginning would also catch Discourse instances hosted in a subdirectory of a domain, but the risk of a potential false positive block would increase.

For these discourse forums:
the e.foundation forums
it worked as well.
With my UBO I opened the tab "My Filters", so in the address bar it reads:
chrome://ublock0/content/dashboard.html#1p-filters.html
and in the form simply pasted:

Code: Select all

/assets/browser-detect-*

and hit enter.
And those forums are now all there for me.

Pale Moon forum

Pixls.us forum / Discourse: Browser not supported [Solved]

Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported

Re: Pixls.us forum / Discourse: Browser not supported

Re: Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported [Solved]

Re: Pixls.us forum / Discourse: Browser not supported

Re: Pixls.us forum / Discourse: Browser not supported

Re: Pixls.us forum / Discourse: Browser not supported