Great suggestion. Thank you!
It made the same to me before using a cryptographic data management.
This “crypto land” is no more a directory and files structured place, it becomes lost hash in a bitswap, where keys memorize chains (hash+timestamp+signature).
IPFS brings it to network level level and creates a “fluid virtual drive” from all or bunch of running nodes. Actually CDN are using it, but it is a technology for people using ipfs to run away from data-centers, lots are still missing the point.
Compared to “Hard Disk Drive” semantics.
Astroport.ONE creates a kind of “BIOS” for IPFS drive used with a key pair
Port 1234 is redirecting to “Master Boot Record” (ip:port) redirecting to the “Allocation Table” showing files to the “Operating System”. We use TW as allocation table and admin, debug interface to help developing Distributed App above it.
TW automatically benefits of a “collective distributed hosting service”.
From the “alpha stage” login (BIOS) page http://qwantic.com:1234
clic on the link in the “yellow pop” to reach the form creating a new one.
Click on the “next yellow” pop (and refresh as it could take 30s to get ready)
From 2 pass phrase and an email, it generates keypair and permanent ipns address of the TW (only those who have the key installed in their ipfs keystore can modify it)
Hope it helps.