Securing Web Sites Made Them Less Accessible – Eric’s Archived Thoughts


60 bookmarks. First posted by heejeroen august 2018.


The drive to force every site on the web to HTTPS has pushed the web further away from the next billion users—not to mention a whole lot of the previous half-billion.  I saw a piece that claimed, “Investing in HTTPS makes it faster, cheaper, and easier for everyone.”  If you define “everyone” as people with gigabit fiber access, sure.  Maybe it’s even true for most of those whose last mile is copper.  But for people beyond the reach of glass and wire, every word of that claim was wrong.
scale 
august 2018 by toddhoff
on https and accessibility
accessibility  performance  security  webdev 
august 2018 by jshwlkr
The drive to secure the web has pushed it further away from the next billion users—not to mention a whole lot of the previous half-billion.
HTTP  security  accessibility 
august 2018 by emerysnyder
In 2018?  Yes.  In rural Uganda, where I was improvising an introduction to web development for a class of vocational students, that’s the reality.  They can have a computer lab full of Dell desktops running Windows or rows of Raspberry Pis running Ubuntu or whatever setup there is, but when satellites in geosynchronous earth orbit are your only source of internet, you wait.  And wait.  And wait.
fridayfrontend  accessibility  https  security  performance 
august 2018 by spaceninja
Securing websites has made them less accessible.
from twitter
august 2018 by donaldjenkins
As i sit reading this via satellite internet...
internet  security  for-brennen 
august 2018 by ToniCorinne
With SSL everywhere, pages can't be cached for low bandwitdh.
performance  accessibility  crypto  security  archive 
august 2018 by archangel
HTTPSだとオフライン・キャッシュがうまく作れないので、転送量に制限がある途上国では閲覧性に大きな問題が起きる話。常時接続じゃない環境をユーザーとして想定するべきかどうか、は重要そう。
security  usability  offline 
august 2018 by hail2u
Due to a slower internet connection and a helpful 'man in the middle' to improve caching for users of the slow internet connection, websites just won't load in a reasonable amount of time over https. This doesn't mean we should go insecure, but instead implement things like services workers to ensure it's not an ongoing issue.
article  321  newslettered 
august 2018 by justinavery
In the middle of last month (July 2018), I found myself staring at a projector screen, waiting once again to see if Wikipedia would load.  If I was lucky, the page started rendering 15-20 seconds after I sent the request.
august 2018 by muhh
I think HTTPS is probably a net positive overall, and I don’t know what we could have done better.  All I know is that I saw, first-hand, the negative externality that was pushed onto people far, far away from our data centers and our thoughts.
internet  security  performance 
august 2018 by leereamsnyder
In the middle of last month (July 2018), I found myself staring at a projector screen, waiting once again to see if Wikipedia would load. If I was lucky, the…
from instapaper
august 2018 by michaelfox
Eric Meyer talks about one of the downsides of HTTPS everywhere, particularly caching strategies that benefit remote regions with high-latency internet connections.
august 2018 by shiflett
RT : HTTPS is a net positive for the web, but it can exclude many people, too:

I’m so glad wrote this.
from twitter
august 2018 by GShaw
"So, [in Uganda] you’re losing half your packets (or more), and the packets that aren’t lost have latency times around two-thirds of a second (or more). Each.
[…]
HTTPS, which by design prevents man-in-the-middle attacks, utterly breaks local caching servers."
HTTPS  webperf  security  TLS  latency  network  cache  clevermarks 
august 2018 by nhoizey
The drive to secure the web has pushed it further away from the next billion users—not to mention a whole lot of the previous half-billion.
august 2018 by lsrgt
This post from @meyerweb notes now our drive for HTTPS has pushed inclusivity further away for people in remote and poor-connectivity areas. 😢
web  inclusivedesign  publishtobuffer 
august 2018 by sonniesedge
In the middle of last month (July 2018), I found myself staring at a projector screen, waiting once again to see if Wikipedia would load. If I was lucky, the…
from instapaper
august 2018 by spinnerin
In the middle of last month (July 2018), I found myself staring at a projector screen, waiting once again to see if Wikipedia would load. If I was lucky, the…
from instapaper
august 2018 by theory
“But there I stood anyway, hoping my requests to load simple web pages would bear fruit, and I could continue teaching basic web principles to a group of vocational students.  Because Wikipedia wouldn’t cache.  Google wouldn’t cache.  Meyerweb wouldn’t cache.  Almost nothing would cache.

“Why?

“HTTPS.”
https  meyerweb  security  2018 
august 2018 by handcoding
Favorite tweet: meyerweb

I recently came face to face with an internet problem I didn’t even know existed, because for me (and probably you), it doesn’t—but it does for thousands or millions of people around the world. https://t.co/UK31x447l6

— Eric Meyer (@meyerweb) August 7, 2018

http://twitter.com/meyerweb/status/1026848459515723777
IFTTT  twitter  favorite 
august 2018 by tswaterman
Securing Web Sites Made Them Less Accessible by

Thought-provoking article. I rem…
from twitter
august 2018 by grigs
Securing Web Sites Made Them Less Accessible
on the slowness of HTTPS in Uganda.
from twitter
august 2018 by codepo8
HTTPS is a net positive for the web, but it can exclude many people, too:

I’m so glad wrote this.
from twitter_favs
august 2018 by jakemcgraw
HTTPS is a net positive for the web, but it can exclude many people, too:

I’m so glad wrote this.
from twitter_favs
august 2018 by heejeroen