I often find that writing something out makes it easier to accomplish.
I already did a diagram for ipfs.
But let's walk through this:
When we upload a file to a Steem UI, we sign it. This proves that the user is who they claim to be, and the file gets stored. This is desirable because otherwise I worry about illegal content and "crap" writ large.
We already have a very serviceable IPFS endpoint that lives at ipfs.blurt.world/ipfs
So next we need to:
- sign images same as we do now (non-standard practice which will require special purpose code)
- Upload the image (standard, boilerplate)
- verify signatures same as we do now (non-standard practice which will require special purpose code)
- Store images in ipfs
- Deliver images in http via ipfs gateway at https://ipfs.blurt.world/ipfs
Sounds easy, right?
Well, I hope so.
If properly developed, this will be useful to many chains and several chain software ecosystems.
BLURT LOVES YOU!
-JACOB
Progress continue to move in the right direction. Blurt is happy.
This is what is needed to be able to drive the front ends, to gain stability. It's a complex job that needs to be simplified but still be very effective for the purposes of the platform.
oops. Sorry bout the double-post.
Hi there.
First of all, thank you for the work you do. I don't take it for granted and I'm very happy to see that the system grows and thrives.
But something else. It has become a little running gag between @nerdtopiade and me in the Discord if you still remember the not sent 500 Blurt, which you wanted to send me once for the photo with the RasPi. ;)
It's been a bit now, but I didn't want to bug you with it in the Hard Fork Stress. :) But now I thought I poke a round. :D