@supersu How would you compare this to #holesail ? I think the solutions can complete each other - a simple website access could be done via ephemeral nostr events, but heavier communication (i.e. video) should be done over Holesail.
Very interested in how these two compare as well! What makes holesail less ideal for less heavy stuff?
For one, holesail is p2p and can handle more than just http traffic.
Holesail is ideal for both super light and super heavy stuff.
Thanks! Was wondering if there was a some kind of cost/trade-off that would not make it worth it to set up that connection for light stuff. But if there isn't really, and if it's P2P, than you would technically be better of with holesail because of increased privacy. Or am i getting that wrong?
Nostr is not P2P so technically the relays could track the amount of traffic, and if they collect the ip-addresses I guess they could track who is communicating with who. From what I understand Holesail needs the servers/relays only in the initial setup of the communication channel. That’s kind of overhead if all you want to do is one or two http api calls and disconnect (like when you pay a static lnurlp). @supersu Do I understand correctly?
Not really, holesail does not need relays or servers. The P2P network running behind Holesail is a closed network that people can not enter unless they know an existing peer. By default there are three public nodes, Node is a known peer, and anyone can become a node.
Node = Relay = Server? If your destination doesn’t have a domain or a public static IP address, some of the communication has to go through a middleman. Which is fine…