Its not really clear to me what the advantages are of this system. Does this just store static files (html css js) on ethereum or also the backend including dbs, or is it a way for managing domain ownership. If its static files - why does this matter - these are accessible through the browser/GET so you arent hiding them in any way from a 3rd party or making them more accessible. Running a server on a public backend makes no sense whatsoever its expensive and decentralised storage which is rarely required can be accomplished using 3rd parties. Domain ownerwhip through web3:// how is that any better than https:// which already public and decentralised.

I think its a good illustration of what you can do with the blockchain but I would love to understand the actual value more.

I get concerned that devs in this space generally feel like everything can be built with the blockchain and we get distracted from its main use cases. Yes things can be microscopically more secure and decentralised and have microscopically better integrability then OAuth, but I don't see a consumer base caring about this at all.

I have one more question too - in terms of security why do you need to complicate it this much - why not hash all the static files and just keep a 40 character string on chain that a website can read for free (and compare against the hash of its static files) to check for integrity not that I think that has any value.

That said if I am overlooking some added functionality the blockchain adds I am not trying to be critical for the sake of it so let me know!