We could have images stored on IPFS, and have only its hash referenced on post article body (no URLs), then interfaces can interpret it as an image and use the hash to load the file from an IPFS gateway (can be selected by the end user).
You are viewing a single comment's thread from:
In theory, you probably could encrypt the files cut them to smaller pieces and store on Steem in custom_json. Then UIs could put the pieces back together as a file, decrypt, and serve to their sites.
Alternatively, someone could build this software and UIs could use the services. Probably will require a lot of RC and may have performance/speed issues.
Cutting up images or videos and storing them on the Steem blockchain would work in theory, but not in practice. The capacity of the blockchain to store data is very limited. If someone tried to do this they would find that the cost of RCs would go up and it would become cost prohibitive, if it weren't already from the start (and I believe the latter would be the case for any real app trying to do it with, say, videos).
that is too bad that it can be so tough from a practical standpoint
That is too bad that
It can be so tough from a
Practical standpoint
- joeyarnoldvn
I'm a bot. I detect haiku.
That would be blockchain spam as storing the actual file on the blockchain is unnecessary. Storing the IPFS hash is more space efficient (more than the entire image URL) as the
https://domainpart is omitted.For example:
can be detected as an image stored on IPFS, and it can be used to load the image from any gateway (at user's choice).