Thanks so much for all your explanations. Taking time to educate a muggle.....
I understand the difference between 'ipfs get' (saving the exact file structure+sub-directories and anything else in the #hash to your local storage) and 'ipfs cat' (view cached version in browser, delete upon closing browser). Maybe we have different ideas about content rights but to me this is a huge difference. Having the exact file or having a cache version, for me, is not the same at all..... (Am I repeating myself too much? sorry...Do I really not get it?).....
Does having a cached version give you the ability to recreate or manipulate the content after you leave the website?
I realize most creative content websites only include thumbnails, short audio samples or watermarked images and videos to protect the content. This is what I will do if there is no other way to protect my originals from being downloaded. Customers would view samples, then request a file. I would encrypt it and send the key (i guess by email) so they could unlock the file on their local storage. I was really hoping IPFS would have this kind of node protection built it but if not...I'm still using IPFS!!
I've tried to test what you guys say about saving a webpage with "Ctrl + S" but it doesn't seem the same as "ipfs get" at all.
This is my IPNS testing space
As you can see the output of the 2 commands is quite different.
'ctrl-s' simply saves the current page. When I go offline I can only view the content on the page I saved, not the rest of the site. No sub-directories or apps folder available.
"ipfs get' on the other hand gives me everything...even files that are not displayed on the page. (I realize this is what the command does. It's just to show difference.)
Saving a page with ctrl-s video