Decentralized has one advantage though. You choose your user agent. For example your browser, your bitcoin client, your email client and so on.
I think it's because the tools were too un-opinionated and unconstrained, so if you wanted to do e.g. a blog then generic HTML editors were too much work even though they were visual. Also, static content publishing is almost never enough. You at least want(ed) search and to understand if anyone is visiting, but then you're into the realm of needing databases and such.
Those are WYSIWYG tools only, which besides being a nightmare to work with, don't solve the actual serving problem. The earliest product that came close to that use case AFAIK was Opera's Unite in 2009, but it didn't last long. By that point it was already too late, since users mostly had asymmetric connections, so serving any type of content from their home network was infeasible. (Had the web launched with easy publishing tools, ISPs would've been forced to offer symmetric connections from the start, and this wouldn't have been a major issue.)
> Also, static content publishing is almost never enough.
True, but there's no reason these tools couldn't have evolved to allow dynamic content as well. Nowadays we have many different approaches that could make this possible, cobbled together from bits and pieces of native and alternative web technologies. Centralized services do make this easier, and who knows, we might've settled on them anyway, but I believe the general perception about user data would've been much different for the better had these tools existed from the start.
I think this is a problem the early web should've solved[1]. Now that the centralized model is dominant, most people wouldn't see a reason to change their habits, even if a new solution would be easier and simpler, and not just better on a technical or privacy level (which most people don't care about anyway).
[1]: https://news.ycombinator.com/item?id=38659814