In a discussion titled ‘Concerns regarding safe mode’ under the Support category, Karl_Romanowski raised concerns that safe mode bypasses server-side restrictions—such as 404 pages hiding /faq, /tos, and /privacy—on forums like Overwatch, exposing site statistics and other hidden content. While he noted there’s no major security threat, he questioned whether safe mode disables Akismet. Falco clarified that safe mode only disables client-side elements (CSS/JS/HTML), not server-side protections. codinghorror acknowledged the issue and consulted sam, who emphasized that sensitive content should be restricted server-side, not merely hidden via soft 404s. codinghorror then directed the decision to eviltrout, who agreed that disabling safe mode via a site setting is a good idea. In a later update, eviltrout confirmed that the latest Discourse version allows admins to disable safe mode entirely via a site setting. Additionally, eviltrout implemented a change ensuring staff members retain access to safe mode even if it’s disabled for regular users, a suggestion originally made by sam.
I think the issue here is that they did not disable stuff hard enough server side on said forum, if we feel like we do not want end users to get certain info we got to close the tap on the server side, a soft 404 on part of the endpoint may not be enough