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
Blurti is enthusiastic...
...look at the address:
https://ipfs.blurt.world/ipfs/QmSQSD2LyBj5ugKLkgKaBLMn3MFk9wELAVCZ4DHDgsaXXwOften writing things down makes us look at them from a different perspective. I hope all goes well. Thank you for all your hard work and dedication.
All points are really important for making a good platform.
Congratulations to the HF5, dear Jacob!
Congratulations, your post has been curated by @r2cornell
Also, find us on Discord (https://discord.gg/BAn2amn)
https://discord.gg/BAn2amn
"Store images in ipfs" mmm... but it doesn't actually store anything - the nodes store file pieces, so the only way to guarantee images exist is to have our own nodes. It is really a distributed file transmission protocol.
Hence, we perhaps should look at some ipfs nodes run by members, similar to other nodes. Members could, of course, install ipfs on their machines and help distribute those file pieces, but that still doesn't guarantee complete redundancy for each image.
One good thing about IPFS is that it does not store duplicates of images, so commonly used images, say footers, will be stored only once.
Hi @rycharde!
All my images of my contents posted before the HF are all broken, I knew that we were still using the link of blurt.buzz to post images. Now that blurt.buzz is not in existence(?) anymore.... (@ericet´s) all banners and GIFS image links are of course broken, too. So I have urged members of the Filipino Community to renew their banners and post them anew (thru host postimage.com) for the new URL. I did mine already and is now ok.
Thanks for the info, altho I'm not the best person to talk to regarding servers and their issues.
Also, 99% of time I use html and an external image host precisely to avoid most image issues.
Good job with HF5, hope everything will run smoothly! Thank you.
Congratulations to the HF5