I read the first two paragraphs of your post, tried loading bbs.boingboing.net on Firefox, page went white as yours did. Like you, I have NoScript installed on my Firefox version. Up until today I would allow boingboing.net and discourse.org. There was no discourse.org script listed in NoScript when I loaded bbs.boingboing.net, which is new.
I checked View Page Source.
Then I allowed fastly.net, and the page rendered as normal.
Is this a new change to the site? What is fastly.net and do I need to allow it from now on?
Looking at the Page Source, I note:
< link > tags in the < head > go to
also in the < style > tag:
< style >
src: url(‘https://discourse-cdn-sjc3.com/boingboing/assets/fontawesome-webfont-ff82aeed6b9bb6701696c84d1b223d2e682eb78c89117a438ce6cfea8c498995.woff2?https://bbs.boingboing.net&2&v=4.5.0’) format(‘woff2’),
< /style >
So there appears to be a custom font, and a few .js scripts hosted by fastly.net required to make the text render. Also, discourse seems to be hosted by fastly.net, which is a new change to the site.
'You can make content available through your websites and Internet-accessible (hosted) application programming interfaces (APIs). You can create content (customer-generated content), as can your end users (user-generated content). Fastly’s CDN Service then makes the transmission of that content (which we sometimes refer to as “content objects”) more efficient by automatically storing copies at intermediate locations on a temporary basis. The process of storing these copies is known as “caching” and the server locations in which they are stored are referred to as “caches.” ’
So content isn’t coming from the boingboing.net server, but from its new content delivery network provider fastly, which is why without allowing fastly.net in NoScript, pages in Firefox render white as an early April in St. John’s, NL.