Web inventor warns on surveillance

[bbc]

[url]http://www.bbc.co.uk/news/technology-25033577#sa-ns_mchannel=rss&ns_source=PublicRSS20-sa[/url]

[dingusnin]

'Web inventor'.
He didn't invent the internet. He worked in a team that made it possible...

[conna]

[QUOTE=dingusnin;42946060]'Web inventor'.
He didn't invent the internet. He worked in a team that made it possible...[/QUOTE]

[i]Totally ignores the point, posts about something that doesn't matter.[/i]

Tim is right, we have to put a stop to this now.

[Docc]

[QUOTE=dingusnin;42946060]'Web inventor'.
He didn't invent the internet. He worked in a team that made it possible...[/QUOTE]

I think you're getting the Web and the Internet mixed up. He didn't have anything to do with the invention of the internet, he is the inventor of the World Wide Web.

[Swilly]

[QUOTE=Docc;42947545]I think you're getting the Web and the Internet mixed up. He didn't have anything to do with the invention of the internet, he is the inventor of the World Wide Web.[/QUOTE]

Yeah, so he really didn't do anything because the Framework was done by DARPA and UCLA.

[gnomical]

[QUOTE=Swilly;42947564]Yeah, so he really didn't do anything because the Framework was done by DARPA and UCLA.[/QUOTE]

The World Wide Web is a system of transferring hypertext documents using a client server architecture. Tim came up with URLs (a global system of uniquely identifying resources on the web), HTML (how webpages are written), and HTTP (how web pages are transferred over the internet).

DARPA (actually ARPA by the way) came up with packet switching. This is how the internet, a system of interconnecting computer networks, works. The World Wide Web is a system of transferring web pages over the internet.

[TheDecryptor]

One of the best parts about the HTTP/2 spec (being worked on now) is that encryption support is mandatory, unlike the current situation where you don't need to offer the site over TLS (You can still offer HTTP/2 over an unecrypted channel, but you need to offer the same content over TLS as well).

So because the server has to offer access over a secured channel, you can easily make a HTTP/2 browser use [b]only[/b] TLS, which Firefox (at least) will be doing. Chrome will probably be the same, but IE probably won't (MS has been against mandatory encryption from the start)