Public facing gateway and pinning #94
Comments
|
Your gateway fetches and stores the data, but doesn't pin it. It gets removed with the next garbage collection run. |
|
Thank you for your answer. If this is true then it seems to be a potential liability issue. |
|
This is what you get running a public gateway. Either way someone could download illegal content from it which implies that this content would pass through your machine. There are works to make opt-in badbits lists which would block illegal contented . |
|
Personally, I don't believe that intellectual property exists as an actual property right, but my opinion will not stop the "Department of Making you Sad" from throwing me into a cage for distributing so called intellectual property. The opt-in list is a good idea to minimize legal liability for the users as well as the IPFS project itself. There are so many useful and legal services that can be made from a system like IPFS. I believe that IPFS is an amazing technology and I really want it to succeed. If you are curious about why I believe the way I do then read: |
|
any guides on how to create public facing gateway? please! |
I suppose you just install ipfs node and make nginx proxy to it, right? |
|
Yes, also enable garbage colection in config, I don't think it is enabled by default (or run it manually in cron/timer job once a day, few hours or something). |
|
Thanks. I've already done it with some other app, but encountered a problem with my ports. They just don't open, no matter what I do. But it's not a problem with IPFS, so it's OK)) Bye! |
|
This issue has been moved to https://discuss.ipfs.io/t/public-facing-gateway-and-pinning/449. |
Kolomona commentedFeb 4, 2016
If I have a public facing gateway and a person retrieves a file through it. Does the file get pinned into my gateway or does the data just pass through without getting pinned? Thanks
The text was updated successfully, but these errors were encountered: