Google and HTTP


55 bookmarks. First posted by hnzz february 2018.


Google and HTTP
What is this?#
I've been writing about Google's efforts to deprecate HTTP, the protocol of the web. This is a summary of why I am opposed to it. DW
Their pitch#
Advocates of deprecating HTTP make three main points:
Something bad could happen to my pages in transit from a server to the user's web browser.
It's not hard to convert to HTTPS and it doesn't cost a lot.
Google is going to warn people about my site being "not secure." So if I don't want people to be scared away, I should just do what they want me to do.
Why this is bad#
The web is an open platform, not a corporate platform.
It is defined by its stability. 25-plus years and it's still going strong.
Google is a guest on the web, as we all are. Guests don't make the rules.
PLATFORMS  toread  readinglist  thefuture  standards 
12 weeks ago by edsonm
A major point of centralization on the web is the browser.
from twitter_favs
august 2018 by wlanderson
On Google’s plan to deprecate http, and why it’s bad:
from twitter_favs
july 2018 by josedante
RT : What Google’s “not secure” means: “Google tried to take control of the open web and this site said no.”
from twitter
june 2018 by netweb
What Google’s “not secure” means: “Google tried to take control of the open web and this site said no.”
from twitter_favs
june 2018 by joi
# I've been writing about Google's efforts to deprecate HTTP , the protocol of the web. This is a summary of why I am opposed to it. DW # Something bad could…
from instapaper
june 2018 by toph
Posted : . Last update : .
from instapaper
june 2018 by kohlmannj
Many of the sites they will label as "not secure" don't ask the user for any information. Of course users won't understand that. Many will take the warning seriously and hit the Back button, having no idea why they're doing it. Of course Google knows this. It's the kind of nasty political tactic we expect from corrupt political leaders, not leading tech companies.
google  web  protocols  security 
june 2018 by jomc
Google is doing what the programming priesthood always does, building the barrier to entry higher, making things more complicated, giving themselves an exclusive. This means only super nerds will be able to put up sites. And we will lose a lot of sites that were quickly posted on a whim, over the 25 years the web has existed, by people that didn't fully understand what they were doing.
google  web 
june 2018 by rubbercat
"Finally, what is the value in being safe?
Twitter and Facebook are like AOL in the old pre-web days. They are run by companies who are committed to provide a safe experience. They make tradeoffs for that. Limited linking. No styles. Character limits. Blocking, muting, reporting, norms. Etc etc. Think of them as Disney-like experiences.
The web is not safe. That is correct. We don't want every place to be safe. So people can be wild and experiment and try out new ideas. It's why the web has been the proving ground for so much incredible stuff over its history.
Lots of things aren't safe. Crossing the street. Bike riding in Manhattan. Falling in love. We do them anyway. You can't be safe all the time. Life itself isn't safe.
If Google succeeds in making the web controlled and bland, we'll just have to reinvent the web outside of Google's sphere. Let's save some time, and create the new web out of the web itself."
Google  HTTP  HTTPS 
may 2018 by cosmic
Google and HTTP # I've been writing about Google's efforts to deprecate HTTP , the protocol of the web. This is a summary of why I am opposed to it. DW # Something bad could…
may 2018 by chadlandman
RT : The web is going to fork.
from twitter
may 2018 by clonezone
RT : The web is going to fork.
from twitter_favs
may 2018 by rubywhite
RT : The web is going to fork.
from twitter
may 2018 by dunstan
Favorite tweet:

Interesting counterargument to Google requiring HTTPS on all websites: many historic sites won't do it, which effectively amounts to a "book burning": https://t.co/KQbfpLyA1G

— Nadia Eghbal (@nayafia) May 24, 2018

http://twitter.com/nayafia/status/999666532916412417
IFTTT  Twitter 
may 2018 by chaoxian
I've been writing about Google's efforts to deprecate HTTP, the protocol of the web. This is a summary of why I am opposed to it. DW

Here is the Google plan:
https://venturebeat.com/2018/05/17/chrome-will-remove-secure-label-on-https-sites-in-september/
HTTPS  technology  To-MB 
may 2018 by W6AZ

The web isn't safe#
Finally, what is the value in being safe?
Twitter and Facebook are like AOL in the old pre-web days. They are run by companies who are committed to provide a safe experience. They make tradeoffs for that. Limited linking. No styles. Character limits. Blocking, muting, reporting, norms. Etc etc. Think of them as Disney-like experiences.
The web is not safe. That is correct. We don't want every place to be safe. So people can be wild and experiment and try out new ideas. It's why the web has been the proving ground for so much incredible stuff over its history.
Lots of things aren't safe. Crossing the street. Bike riding in Manhattan. Falling in love. We do them anyway. You can't be safe all the time. Life itself isn't safe.
If Google succeeds in making the web controlled and bland, we'll just have to reinvent the web outside of Google's sphere. Let's save some time, and create the new web out of the web itself.
PS: Of course we want parts of the web to be safe. Banking websites, for example. But my blog archive from 2001? Really there's no need for special provisions there.
http  https  indie  google  web 
may 2018 by WimLeers
Dave winer
web 
april 2018 by eclectics
Why HTTP ought not be deprecated: . "The web is a social agreement not to break things."
from twitter_favs
april 2018 by connolly
Why HTTP ought not be deprecated: . "The web is a social agreement not to break things."
from twitter_favs
april 2018 by floehopper
Google and HTTP | ... and I totally agree.
from twitter
march 2018 by rickc57
I've been writing about Google's efforts to deprecate HTTP , the protocol of the web. This is a summary of why I am opposed to this. DW Something bad could…
from instapaper
march 2018 by splorp
I'm a big fan of moving over to HTTPS in favour of staying on HTTP. This mainly comes down to two reasons: 1) I want to run on http2 and it requires https; and 2) I want to use Service Workers and have an offline progressive web ap... which also requires HTTPS. I'd never thought of the things that this article points out, looking at all the archives and historic pages on the web that can't afford to, don't have the technical know how, or just don't have anyone managing them any more. It's an interesting take on things.
article  newslettered  299 
march 2018 by justinavery
RT : I updated the Google and HTTP faq.
from twitter
march 2018 by mshook
I updated the Google and HTTP faq.
from twitter_favs
march 2018 by ianchanning
Winer has standing.
s 
february 2018 by jgordon
Dave Winer expands on his blog posts, arguing that the HTTPS movement is an attack on HTTP, done by Google.
https  google  davewiner  security  encryptingtheweb  letsencrypt 
february 2018 by npdoty