@lycaon noscript is an accesibility tool, not a thing only security snobs see
I've been working on reviving a blog that has 0 dynamic presence, and that allows a group of collaboratng authors to create a content stream when they all don't know each other. It can't be done via static content.
My goal is to not have a trusted server for executable content integration. The intent is to protect the privacy of a group of collaborating authors while still making their content visible.
@Efi I'm curious how I might communicate that in a way that doesn't make people noscripting the web.
As the web becomes a distributed application platform it's going to get more common, but I struggle to explain to people that noscripting is essentially a way to access an older part of web, and there are parts that cannot be accessed without an executable context even if they're just serving content.
@Efi Anything using a blockchain without central storage requires an integration pass.
Another context is that a full execution context for content integration is much more expensive than static hosting. So there is a dimension of economic accessibility. Client-side web apps have an excellent code-delivery story and are less expensive for the hoster.