I think that’s already a consequence, TCP/IP is very much a protocol suite that works well for client/server architectures, and HTTP (which eventually, somehow, became the de facto “everything” protocol) even more so. So when you mix these roles and you have machines that act as both client and server at the same time all the deficiencies come to light quite easily. A world with first-class support for mutual authentication and authorization, encryption, peering, roaming, etc at the lowest of network levels was possible, but that ship has sailed.
I think that’s already a consequence, TCP/IP is very much a protocol suite that works well for client/server architectures, and HTTP (which eventually, somehow, became the de facto “everything” protocol) even more so. So when you mix these roles and you have machines that act as both client and server at the same time all the deficiencies come to light quite easily. A world with first-class support for mutual authentication and authorization, encryption, peering, roaming, etc at the lowest of network levels was possible, but that ship has sailed.