you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (2 children)

That's it, that's where I got stuck too. I did a little more reading, and I think that either we'd have to publish a list of every saidit related ipfs image in hopes that others would request/save/reseed them, or force share everything to another ipfs-pic instances (again requiring a third party that gives a shit).

[–]magnora7 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (1 child)

I think the latter is what we'd want, or the list would somehow naturally accumulate with code from the site. But I still don't get what actions a user would have to take to actually help host the data, even if they wanted to.

[–][deleted] 3 insightful - 1 fun3 insightful - 0 fun4 insightful - 1 fun -  (0 children)

what actions a user would have to take to actually help host the data

If we only offered ipfs image links or a preference to use ipfs links instead, then people could run a local ipfs instance and this browser extension and then I think when they view the image they are downloading it to their local instance and hosting it for the next guy.

Aside from that, there's the full blown browser only ipfs implementation which can somehow get you swapping media with others directly (no extension, no server side local node, the browser is the node), like BitChute. However I see it's very alpha and they have browser crashing issues. That is some heavyweight js code to be running alongside a site like this too.