|
|
|
|
|
by sneak
334 days ago
|
|
Not really. You could have tinyweb/oldweb sites identify themselves with a meta tag, and have a browser that only browses those. A opt-in, web-within-a-web. And turns off js, cookies, and images. You don’t need another transport protocol. |
|
If your goal is precisely to create an parallel ecosystem that's "airgapped" from the mainstream web, and you're already going to have to develop custom clients, content formats, and server-side configuration to implement it on top of HTTP, and engage in lots of development work to imperfectly isolate the two ecosystems from each other, why wouldn't you just develop a parallel protocol and start with a clean slate?