I would prefer people did hyperlinks through URI, and we accepted some centrality to access a URI -> URL mapper. I say "some" centrality because the mapping function is a public good, and will probably have to be done by a number of big entities either through sharding, or some distribution of a centrally managed/maintained core. Analogous to the risk in the DNS, but the DNS is also a public good.
The web is still there as the foundation and glue. It's not dead, it's used all the time for eCommerce, support, documentation, research, forums, and most importantly for universal interoperability across whatever "silos" are out there. URI, HTTP, MIME, HTML, and JavaScript are literally the glue that holds even the silos together, or allows our myriad devices to interoperate with them.
How else did TikTok take off? Hyperlinks!
The issue has always been that most software folks and most users prefer centralization because it's "easier". Engineers fought against REST in favor of RPCs (gotta ship now to appease our investors, rather than think through how to build a decentralized service!). Even peek web circa 2012 had Google Reader as the ultimate blog aggregation experience.
All the architecture and tech of the web is sitting there ready to be used. It's up to software creators to make decentralized software people actually want to use.