I have to admit I was hoping this clickbait title would spawn some proper drama in the comments - a controversial thesis on decentralization on a decentralized platform, that's basically throwing a match into a fireworks factory. But looks like the bait didn't quite catch despite the effort :-) So let me be the one to take it. ;-)

The title should really read "cannot be decentralized this way" - because Hive sites already are decentralized. Just not by storing HTML on-chain.

Hive's decentralization lives in the data layer. Posts, transactions, account state - all replicated across dozens of independent nodes. Consensus via elected witnesses. Anyone can run a node, anyone can read the entire chain. That's the decentralization that matters, because that's where censorship resistance lives. Frontends? They're just views. If https://hive.blog goes down, you open https://ecency.com. If ecency goes down, there's https://peakd.com. Or WIP https://blog.openhive.network. Or you spin up your own - the data is right there, on every node. In fact recently haf_api_node includes denser instance for those who wish to Hive it their own way.

The frontend being trivially replaceable IS the decentralization feature. That would be trying to decentralize the least important part of the stack. That would be solving a problem nobody has.

And then there's the punchline. Cloudflare Workers. The most decentralized infrastructure known to mankind A single corporate CDN provider that can terminate your account, filter your content, and that once leaked memory across customer sites (Cloudbleed, anyone?). Don't get me wrong - Cloudflare is genuinely useful, I use it myself for various things. But proposing it as a decentralization mechanism is like proposing to decentralize banking by putting everything in one really big bank. You can't centralize harder than that ;-)

Hive account@logic already found prior art - propolis-wallet, a complete wallet application stored on-chain in 4 parts, reassembled client-side. So Hive account@louis88 "can you store an app on Hive?" question was already answered. The more interesting question isn't can you, but should you - and for what.

The block size analysis tables are solid reference material though. Knowing what fits in a transaction is genuinely useful for anyone building on Hive.

That being said, whether you want to have your Hive blog on Cloudflare Workers, GitHub pages (see My Honey Pot btw), or maybe even Disposable Vapes ...

Feel free.
It's Hive.
(And it's awesome!)

A mic drop pic, just one that takes a little space and doesn't even require loading an image ;-)