I'm increasingly baffled by ppl who draw a distinction between "the web" & "the browser". Most interesting properties are abt the browser.
the hyperlinks need a general-purpose protocol for display. `twitter://` doesn't work on Android so it doesn't qualify.
-
-
URL + "global protocol for what to do with a URL" is the web. The browser is the general version of that protocol.
-
the browser isn’t a general-purpose “protocol” for how to handle URLs, though, because as you say it can’t handle twitter:// etc.
-
thus the web is larger than browsers—and I believe will continue to move further away from browsers
-
I just don't understand the point of that definition. It's abstract and doesn't encapsulate enough.
End of conversation
New conversation -
-
-
the scheme of the uri defines the protocol, in this example that's how you launch the native twitter app...
-
doesn't work on Android or Windows so it's not a "web location"
-
URIs are bigger than "the web"
-
what I mean to say is that URIs are not scoped simply to browsers or the web; that is just a very popular use
-
URLs that aren't pointing at content described by web standards are URLs but not the web.
-
URLs are more abstract but the concreteness of the web helps make it broadly useful.
-
a website isn’t really any different from an app. they can link back and forth, just built with different tech
-
a website can be displayed by any web browser capable of displaying standard web content. An app works on one OS.
- 4 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.