The right to See the URL from which content is displayed
suggested by Danny Birchall2013-10-07
Danny Birchall: 'Trust' in a browser context extends beyond the mechanical issuing and acceptance of HTTPS certificates. Through years of use, we have learned to read URLs as human statements an intentions of ownership and architecture, from the top level domain to the directory structure. Typically technocratic content 'management' systems have obscured these, to the detriment of the user: a well-formed URL is the first element of metadata about a web page that a user encounters, and it tells us something.
Link shorteners like bit.ly initially obscure a URL, but the browser leads you to it eventually. Inside an app, things are different. Because web pages returned natively from the web remain an important source of structured information, many apps include an embedded browser function to display data directly from the WWW. Many omit the browser's 'location' bar, and thus obscure the source of the information. The user's well-honed URL-reading skills are ignored, and the larger context of the web replaced with the narrow context of the app.
A URL attached to content makes that content both addressable and accountable. All web-based content should come with its URL attached.
Brendan Howell: Indeed and if you ever open the network tab in the developer view for some crappy big media web site it can be shocking to see all the tracking, ads and api crap that gets loaded from dozens of different servers.
olia lialina: URL is a weapon and the kez to survival online. Read for example Addie Wagenknecht|s FREE INTERNET FOREVER!!!! http://fffff.at/freewifi/
"When you try to load a page, the router will automatically redirect you to the login page: look at the URL, because from there you can see which system the airport is using"