Quite the opposite. For this set up, you still need to pay for hosting, or host it yourself, and you need to deliver the underlying frontend code to the user's devices that makes all of this possible. Then you also need a backend to handle the socket connections and send it from user to user (this is not P2P). The constant pinging to see if anyone is waiting for a copy, and then sending it out, will only continue to eat up resources the more people are looking at it.
From an efficiency standpoint, this doesn't come close to beating a simple static cacheable text file. Definitely still a very cool concept, but offers limited real-world use.