I like your words. It's not a different problem. Doubly said "expression of systemic moral hazards" leak into these successful platforms. They get fat and then formally hire 1000x more inhouse devs, biz, and design folks when they could ad hoc pay the people who were there from the beginning. Or new people who spring up and bring the platform forward. It's creativity in contracts the status quo is lacking.
I am curious - where are the "public highway" equivalents of Twitter or Facebook? Who owns the infrastructure all this data is passed through? It's definitely not publicly owned. In my opinion, your analogy is mismatched.
TCP/IP, DNS, HTTP is the major part of the internet's virtual infrastructure (although you might say that there are others, such as router configuration protocols). The physical infrastructure is rather complicated, and owned by large ISPs which connect to each other and smaller ISPs that connect to one or more large ISPs. The 'last mile' provider collects money for access to this infrastructure.
Free physical access is provided in the US by public libraries. De facto free access is provided by a wide range of retail businesses, such as coffee shops.
With your own device connected to the internet you will have a NAT'd IP address from which you can request anything you want. Unfortunately, until IPv6 becomes commonplace, one has to jump through hoops to expose the device - the most common being some form of dynamic DNS.
At the coffee shop the packets that your computer sends are travelling around the world on de facto public infrastructure. It's true that a bad actor can shut down routes, but the internet is rather cleverly designed to treat a shutdown or reduction as "damage" and simply use a different route.
I am curious - where are the "public highway" equivalents of Twitter or Facebook? Who owns the infrastructure all this data is passed through? It's definitely not publicly owned. In my opinion, your analogy is mismatched.