| Skynet can be used for any sort of data. Public facing portals and hosts serving unencrypted data are of course responsible for the content they serve. People can upload content in two ways: either by using a public facing portal such as siasky.net or by spinning up their own portal client (Sia node) and communicating with hosts directly via the distributed network. It is possible for individual portals and hosts to take down links and stop serving that content, for example after accepting copyright infringement requests. It it also possible for anyone to spin up their own portal and keep content pinned as long as any host on the network will accept it. For example, skyportal.xyz is another public portal. Same goes for hosts. The Skynet (Sia) model aims for thousands and thousands of hosts spread geographically. It becomes extremely difficult to delete any piece of data from the network entirely as long as someone wants to make sure it stays up. Erasure coding redundancy ensures very high resilience from any single host going offline. |
I think this needs to be solved at the protocol level. What if the portal is hosted in a DGAF jurisdiction, but I'm running my node in a different jurisdiction? What forces the portal to keep my interest in mind?