Sure, you and I understand that term, but what does it mean for a person stuck for a week trying to sync? Or as you pointed having to sync yet another time?
The fact that chia software doesn’t shut down cleanly and is not always closing blockchain db is just ridiculous. It is also possible that during those dust storms some dbs are being corrupted. I noticed few people having busted dbs, and it looks like for all of them it happened around the last dust storm.
Haha. When it will be pain to download, it may also be pain to sync. Oh wait, it is already pain to sync.
Again, the problem is not that someone is offering a solution that tries to address sync issues / db corruptions, but rather the fact that chia is not addressing this problem in the first place. As you pointed out, other blockchains can handle way bigger dbs basically easily, and chia is just in its infancy (since the official release, not really from when it started - 2017, if I am not mistaken).
Yeah, I think that person may be behind something like dropbox - maybe ipfs.io.
By the way, i think that the whole sync process should be split into two parallel threads. The first would draw data from peers and save results on disk, where the second would be parsing whatever has been downloaded. This way, the download process would be done in an hour or so. Of course, the processing would still take whatever it takes. However, that “processing” process would be a nicely isolated one, potentially much easier to get it improved (e.g., outsource it to someone with a better experience).