Maybe I have expressed myself unclear, but I don't want to advocate against networked software and loading resources over a network in general. I would like to

Maybe I have expressed myself unclear, but I don't want to advocate against networked software and loading resources over a network in general. I would like to have a more "typed" API to networking services (including web-pages) that provides sufficient information to render the application on my client - the term "whitelist" may indeed be a sub-optimal term. > Having "specifications" that websites and authors would have to enforce based on content would make the web less free. We already have enforced specifications (HTML, HTTP, TCP, ...) and they did make the web free, as you could and can participate, when you implement these specifications (at least to a sufficient degree). However we could go further and provide specifications for more high-level tasks. Consider the problem of going from A to B via public transport. Cities with a working public transport infrastructure normally provide a webpage that allows you to search for routes and reporting journey time, cost and additional information. However these webpages are more or less convenient to use and every transportation provider has to implement its own shitty webpage. Hypothetically it could implement an API that provides this information and the "Browser" has its builtin GUI (configurable by the user) to access this information. > Software authors have the right and the freedom to write whatever they like, any way they choose, up to and including the UI. I am more talking about users who should have the possibility to access the information they seek in an uncluttered way. And we can keep stuff like <canvas>, so you are still able to draw your pixels.