SoylentNews is people
SoylentNews
The Web began dying in 2014. André Staltz writes about how and why. In a nutshell, traffic from mobile and tablet devices now surpasses that from regular desktop computers and of that traffic the overwhelming majority goes to either Faecebook or Google. Amazon is also in there. None of them have any interest in defending the open Web any more. Rather the situation is the opposite, they are aiming to carve out a section and establish very isolated walled gardens. Net Neutrality, or the lack thereof, lie at the heart of their plans based on the direction they have moved since 2014.
This discussion has been archived.
No new comments can be posted.
What the Web Was and What It Has Become
|
Log In/Create an Account
| Top
| 83 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
It's raisins that make Post Raisin Bran so raisiny ...
(Score: 2) by bzipitidoo on Saturday November 04 2017, @02:47AM (5 children)
Change for the sake of breaking things sickens systems. They may recover, or they may die. However, this article is hysteria. The web is NOT dying.
The one irksome change that occurred sometime this summer was port 80 being blocked somehow. I have no explanation for why my web site is no longer visible, and suspect the ISP made a quiet change of policy. Flipped the kill switch, so to speak, on port 80. There's been this big drive to switch from http to https. Guess I'll have to operate on port 443 from now on. But I'm not convinced https should be used everywhere, and I ought to have the option to stick to http if I want. Whatever the merits of https, forcing everyone to use it it does push tiny websites running on marginal servers further to the edge.
(Score: 2) by RS3 on Saturday November 04 2017, @03:15AM (4 children)
https: any chance it's being pushed by people selling certs?
(Score: 4, Informative) by Pino P on Saturday November 04 2017, @06:27AM (3 children)
It's not the CAs. Let's Encrypt makes domain-validated certificates available without charge through an automated service.
HTTPS is pushed in part by people selling domains. If you don't have a fully-qualified domain name for the router, printer, or NAS on your home LAN, you can't run HTTPS over your internal network with a certificate that house guests' devices will recognize.
(Score: 2) by RS3 on Saturday November 04 2017, @04:15PM (2 children)
Thanks for that info.
Could you use a generated self-signed cert. for your LAN https?
(Score: 4, Informative) by Pino P on Sunday November 05 2017, @01:44AM (1 child)
Yes, provided two things:
1. All devices capable of accessing resources on your network are capable of bypassing unknown issuer warnings or installing a private CA's root certificate.
2. All your users are willing to take such measures.
Say you store videos on a NAS on your home LAN, and you've invited friends or relatives to enter your home and view videos. If they are non-technical users, an unknown issuer warning might scare them off.
(Score: 2) by RS3 on Sunday November 05 2017, @02:06AM
Thanks again.
Or, they may do what most people I know of do: "Sure, I'll accept that certificate! Certificates are a good thing- I have many I'm proud of!"