Users report a bug where Discourse forums fail to load properly when using Tor Browser set to “safest” security level (with NoScript active), causing JavaScript to be blocked. blueberrybee demonstrates the issue with a video and notes it’s reproducible on meta.discourse.org, suggesting it may also occur in other browsers with NoScript enabled. Moin questions whether it’s a bug since Tor Browser isn’t officially supported, citing Discourse’s supported browser list (Edge, Chrome, Firefox, Safari). Lhc_fl points out that Discourse is JavaScript-heavy and disabling JS naturally breaks functionality. adrelanos confirms reproducing the issue in Chromium with all JS disabled and argues that since Discourse has documented noJS support (citing meta.discourse.org threads), the broken initial load — which sometimes fixes on reload — may indicate a bug. Lhc_fl notes they couldn’t reproduce the issue with JS fully disabled in Chromium. blueberrybee re-uploads the video after the original link expired and reiterates that the problem likely requires a Discourse-side fix rather than browser tweaks.
I’ve noticed a consistent problem when browsing a Discourse forum using the Tor Browser (TB). Specifically, when the security slider is set to its “safest” level, which turns on NoScript, there are instances where page loading encounters issues.
So you turned off some or all of Javascript? Discourse is a highly Javascript-driven web application. Turning off Javascript or letting some Javascript not load will of course cause the page to break.