By far the most in-depth response yet! Thanks for the contribution franky.
To extend on your thoughts, would there be a better use-case for a different blockchain rather than Bitcoin's?
different blockchain - yes
first thing that needs solving is. what industry needs to have a big batch of information in multiple locations
if data can function from one source. theres not much need to even try introducing blockchain into that industry.
however think about airports which would benefit greatly from having passport data backed up utilised in different locations.
because if you shut one airport. other airports can still run, as long as they have the data..
so if one source goes down..if all the data was in once source. no one can fly anywhere.
but if one source goes down..if all the data was in every airport. anyone one can fly anywhere. by just finding a new airport
where as if facebook.com goes down. it downt matter if their data was on one server or multiple nodes.. theres no point in having blockchain/DLT logged data because the only gateway to that info (facebook.com) is shut down.(you cant just go to another facebook and continue utilising facebook)
yes having facebook back up its data incase the data gets corrupted rather then site shutdown. but from a utility prospective. there is no need to have it scattered across 7000 locations. as it only needs 4-5 backup locations incase of fire/theft.
(facebook doesnt and wouldnt benefit from asking a billion users to hold a copy of the billion users timeline.)
secondly
i was going to waffle into loads of concepts and different 'chain' designs. but there are just so many ways that look nothing like bitcoins design. but the important thing is to work out what industry needs distributed data FUNCTIONALLY that is needed to be UTILISED across locations. rather than just having it as a backup.
i hope you notice the difference between readily available data from different locations being a utility. vs just plain backup of data of one gateway incase of central fault