CloudFlare creates an IPFS gateway
https://blog.cloudflare.com/distributed-web-gateway/
If folks check their ISP's Terms of Service they will probably find a clause which describes several forbidden uses. In the ToS for my ISP is
xi To use or run public servers;
I noticed that after I had experimented with IPFS.
If you install Apache2 on your system and then expose your website on it, even as an IPFS node, you are using and running a public server. Your ISP may object.
It is that Apache based website which you create and serve as an IPFS node visible to other users on IPFS. When they visit your site they can copy your site to their local IPFS server and "host" it, if they wish. If you shut down your computer for the evening but the folks that "host" your website do not then your website is still available to other users of IPFS. Visitors to those sites may end up hosting your webpage as well.
When I installed and tested IPFS on my laptop, which, at the time, was an i7 CPU Acer V3-771G that had 6GB of RAM and a 750GB HD, connected to a 30MiB Internet cable service, I ended up with a couple hundred webpages from that many IPFS nodes. They were installed on my system just by virtue of my visiting those website. At 20Mb per website those webpages consumed most of my HD, 2/3rs of my Internet bandwidth, and six of my 8 core. At one time I had over 500 other IPFS users visiting my computer at the same time. That's the default mode. You have to take charge and set parameters which limit how which or how many websites you host on your machine. IF your ISP allows you to do it. Most do not.
CloudFlare's portal is nothing more or less than a man-in-the-middle IPFS implementation. IF you are using a standard web browser and IPv4 or IPv6 addressing then they can see and identify your browser packets going into their https://cloudflare-ipfs.com/ip... [cloudflare-ipfs.com] gateway and the packets coming out of their https://cloudflare-ipfs.com/ip... [cloudflare-ipfs.com] gateway going to your browser.
The real IPFS way begins at your browser URL with: http://localhost:8080/ipfs/has... [localhost]
That method, which is what IPFS intends, starts at your browser with an encrypted tunnel and ends back at your browser with an encrypted tunnel.
A free Internet is free for everyone or it is free for no one. Even for Marxists and Nazis and everyone in between. They can shout but you do not have to listen, just like you should be able to shout regardless if anyone listens to you or not.
Remember that CloudFlare deleted at least one website they were hosting, so its only a matter of time before they delete another, maybe yours.
If folks check their ISP's Terms of Service they will probably find a clause which describes several forbidden uses. In the ToS for my ISP is
xi To use or run public servers;
I noticed that after I had experimented with IPFS.
If you install Apache2 on your system and then expose your website on it, even as an IPFS node, you are using and running a public server. Your ISP may object.
It is that Apache based website which you create and serve as an IPFS node visible to other users on IPFS. When they visit your site they can copy your site to their local IPFS server and "host" it, if they wish. If you shut down your computer for the evening but the folks that "host" your website do not then your website is still available to other users of IPFS. Visitors to those sites may end up hosting your webpage as well.
When I installed and tested IPFS on my laptop, which, at the time, was an i7 CPU Acer V3-771G that had 6GB of RAM and a 750GB HD, connected to a 30MiB Internet cable service, I ended up with a couple hundred webpages from that many IPFS nodes. They were installed on my system just by virtue of my visiting those website. At 20Mb per website those webpages consumed most of my HD, 2/3rs of my Internet bandwidth, and six of my 8 core. At one time I had over 500 other IPFS users visiting my computer at the same time. That's the default mode. You have to take charge and set parameters which limit how which or how many websites you host on your machine. IF your ISP allows you to do it. Most do not.
CloudFlare's portal is nothing more or less than a man-in-the-middle IPFS implementation. IF you are using a standard web browser and IPv4 or IPv6 addressing then they can see and identify your browser packets going into their https://cloudflare-ipfs.com/ip... [cloudflare-ipfs.com] gateway and the packets coming out of their https://cloudflare-ipfs.com/ip... [cloudflare-ipfs.com] gateway going to your browser.
The real IPFS way begins at your browser URL with: http://localhost:8080/ipfs/has... [localhost]
That method, which is what IPFS intends, starts at your browser with an encrypted tunnel and ends back at your browser with an encrypted tunnel.
A free Internet is free for everyone or it is free for no one. Even for Marxists and Nazis and everyone in between. They can shout but you do not have to listen, just like you should be able to shout regardless if anyone listens to you or not.
Remember that CloudFlare deleted at least one website they were hosting, so its only a matter of time before they delete another, maybe yours.