Oddbean

Tradeoffs: None that I can think of, it is your device, your own relays, your own connection. You are always private, only the people you choose can access your service in private mode, and the publically sharable key lets others access your stuff..

I would say there are the same privacy issues as BitTorrent, IF you are using it publicly or for a service that is known to be criminal or “unapproved of.” Basically IP addresses are exposed like any normal clearnet if someone at scale is trying to ping and investigate what every peer is doing. The reason it’s hard to call this a “trade off” exactly however is because this is literally no different than it’s ever been, to the contrary it’s better in a P2P system like this than with normal internet usage. You have more privacy because there’s not any indication as to what is being communicated, what you are connecting to, or why. (Everything is a generic key, not a visible, discoverable domain like ReallyWeirdFetish.com or something) So it’s more of an “it doesn’t really solve privacy” consideration rather than a trade off. Another case could be made for DDOS risk, since you are working directly with your personal IP address. You’re a bit more open to attack in P2P than through using central servers and services to connect through. But that’s really kind of a dodge, a little like saying “well if you hold your keys you might lose your bitcoin.” Yeah sure, but that just comes with being sovereign. Lastly is that P2P is often less reliable for data persistence, but this is a device problem, not a P2P problem. If you treat a peer node like a server, it’ll be as reliable as a server. Honestly from everything I’ve dug into, from a purely theoretical sense, there just aren’t that many trade offs, aside from calling the fact that it doesn’t solve every single problem that we may want a “trade off.” But in regards to the alternatives… it’s just better.

Zeus specifically could use something simpler like: https://github.com/nostr-protocol/nips/pull/1276 There is not a lot of communication going between the Zeus app and the LND on my home computer. It’s not video-streaming, it’s just some requests and responses that could be wrapped similar to Nostr DMs.

Sure, but it all requires implementation on both ends. We’re working on one end right now and should have it done very soon. Plus the connection can be used for plenty of other things in the future, it’s a very versatile tool. If you want to implement the other then I’d happily put sats on getting NEC into Zeus as well. I think the Nostr/relay model is a fantastic backup connection method honestly. I think doing P2P first, then falling onto relays if it fails for some reason could be a really reliable & yet decentralized design.

as it is right now, holesail is essentially a server, so it takes implementation on both ends. you are wanting the zeus app to create the tunnel from the outside without any server side implementation?

A note to @TheGuySwann, you might need to cough up the "big sats" soon. Holesail is now super easy to implement on Android with https://github.com/holepunchto/bare-expo 👀 Take the bounty guys, and I will help you every step of the way to do this. nostr:note1v9072gse3ztk73d80tw0sahzjat6fchs5gjt9cmd6xe023tm0luqyp9982