I agree most of the issue is on the "web" and not the physical infrastructure, although there is an internet outside the "world wide web" too:
https://yesterweb.org/zine/issue-05/08/
"The internet and the web are not one and the same. The web is simply one protocol of the internet. You see the "https://" at the beginning of the url bar? That's the Hypertext Transfer Protocol, or as it's more commonly known, The World Wide Web."
I sometimes mention the two because multiple protocols are part of the Transport layer. But then again, relying on one too much may be part of the problem, hence the emphasis on examining all the layers and protocols, like UDP.
But you don't really examine the other layers, just talk about them. You aren't proposing alternatives.
Honestly if you cut through everything that's brought up and left dangling, whats left is Website and App efficiency, and a very sizable percentage of apps are just wrapped websites.
I just did a ctrl+f on the page and couldn't find a reference to UDP.
Edit: One thing I didn't include in the article was file sharing protocols, because of security vulunerabilities. I recall IPFS had some known issues, but others have tried to use similar protocols:
Do they work faster than the regular web? Well, torrents can download faster. But I do not know how much the web depends on it or needs it. I know Microsoft and Steam servers allow downloading games and updates from other PCs, including ones outside a local network. Why they offer it (for Windows system files), is beyond me. Maybe some areas (public networks) share an unsecure wifi network more often and do not own a separate router for trusted internet access. I guess the files are encrypted enough that there is a checksum that can determine if the files are not tampered?
>I must admit I am still having a hard time following you.
You're not the first. A "sister" project I started in 2020 is hardware focused, and later on, I determined that a lightweight suite for internet would complement the offline stack: https://ei2030.github.io/FemtoTX/#about
One could say it's a "solution in search of a problem", but game development also is an incubator:
There are other Jobs inspired R&D groups out there- a notable one is Ink & Switch: https://www.youtube.com/watch?v=9s8OA08ggbM They use an aircraft carrier vs. bicycle comparison, as Steve Jobs preferred the bike metaphor as an extension of user capabilities.
>Why should a household or office download windows update files more than once? Seems like a great idea.
I agree with you on that. I also use it to share files and updates on my own network, often when transferring Steam games from one PC to another. I meant for non private networks (like internet cafes) is where I thought there might be a security issue.
https://www.tomsguide.com/computing/windows-is-using-your-in... I do not really know whether it's secure enough, but I'm going to leave that to the experts.
HTTP isn't the WWW. Back when browsers supported FTP and Gopher, you could deliver the exact same HTML, for the exact same experience, over either protocol.
"The internet and the web are not one and the same. The web is simply one protocol of the internet. You see the "https://" at the beginning of the url bar? That's the Hypertext Transfer Protocol, or as it's more commonly known, The World Wide Web."
I sometimes mention the two because multiple protocols are part of the Transport layer. But then again, relying on one too much may be part of the problem, hence the emphasis on examining all the layers and protocols, like UDP.