4 ms·

The web is moving on without you. Edit: Your blog doesn't even use SSL...

spookthesunset 6y ago
The “documents not applications” battle is like 10 years old at this point. The web moved on a decade ago... I’ve had the “how to deal with folks who disable JavaScript” discussion for well over 10 years and the answer in every shop I’ve worked in has always been the same... don’t bother. And it was the developers themselves making that call, not the “business people”.
- weird-eye-issue 6y ago
  Yeah I was being nice. It moved on so long ago I'm not sure how he calls himself a developer. Okay there... I said it.
milkey_mouse 6y ago
Sometimes "the industry" "moves on without" a valuable perspective. That doesn't mean those "left behind" (e.g. Richard Stallman) should give up. Something something "marketplace of ideas." But yeah, GP, get a Let's Encrypt certificate for the sake of your readers!
- nashashmi 6y ago
  OT : What http site is left we can go to when isp or WiFi greets with a welcome login page. Going to https sites gives an error.
  - depressedpanda 6y ago
    http://example.com/ http://example.com/
  - ziml77 6y ago
    http://neverssl.com http://neverssl.com or http://detectportal.firefox.com/canonical.html http://detectportal.firefox.com/canonical.html
  - krazerlasers 6y ago
    You are welcome to use my site: http://krazerlasers.com http://krazerlasers.com You are also welcome to use my html boilerplate: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <link rel="stylesheet" type="text/css" href="blue-white.css">
  - deathanatos 6y ago
    ISPs & WiFi APs can stop trying to attack connections like that, and implement RFC 8910[1]. Otherwise… example.com, maybe. I guess we'll see how long the http version of that lasts. I assume ISPs will get around to this a few decades after implementing IPv6. [1]: https://tools.ietf.org/html/rfc8910 https://tools.ietf.org/html/rfc8910

The “documents not applications” battle is like 10 years old at this point. The web moved on a decade ago... I’ve had the “how to deal with folks who disable JavaScript” discussion for well over 10 years and the answer in every shop I’ve worked in has always been the same... don’t bother. And it was the developers themselves making that call, not the “business people”.

weird-eye-issue 6y ago
Yeah I was being nice. It moved on so long ago I'm not sure how he calls himself a developer. Okay there... I said it.

milkey_mouse 6y ago

Sometimes "the industry" "moves on without" a valuable perspective. That doesn't mean those "left behind" (e.g. Richard Stallman) should give up. Something something "marketplace of ideas." But yeah, GP, get a Let's Encrypt certificate for the sake of your readers!

nashashmi 6y ago
OT : What http site is left we can go to when isp or WiFi greets with a welcome login page. Going to https sites gives an error.
- depressedpanda 6y ago
  http://example.com/ http://example.com/
- ziml77 6y ago
  http://neverssl.com http://neverssl.com or http://detectportal.firefox.com/canonical.html http://detectportal.firefox.com/canonical.html
- krazerlasers 6y ago
  You are welcome to use my site: http://krazerlasers.com http://krazerlasers.com You are also welcome to use my html boilerplate: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <link rel="stylesheet" type="text/css" href="blue-white.css">
- deathanatos 6y ago
  ISPs & WiFi APs can stop trying to attack connections like that, and implement RFC 8910[1]. Otherwise… example.com, maybe. I guess we'll see how long the http version of that lasts. I assume ISPs will get around to this a few decades after implementing IPv6. [1]: https://tools.ietf.org/html/rfc8910 https://tools.ietf.org/html/rfc8910