As far as I understand it, nsecbunker can be on another device than the client. Alby must be on the same device.
Discussion
yeah, nsecbunker can be running on any device and accessed remotely from anywhere
on my way to Miami I published events from the plane signing the events from my LN node back home
Are you opening a port? Using upnp? Or a tunnel like ngrok?
nsecbunker connects over nostr, so it can run behind a firewall just fine
Fuckin hell! That's impressive though as long as it works, but the lengths we go to avoid opening a port is crazy, meanwhile Bittorrent have been using upnp like there is no tomorrow!
There is still the problem of discovery (when suddenly I don't have common relays with the nsecbunker service provider for some reason).
Using Nostr as a replacement for good old web platforms instead of decentralized DNS (Pkarr) and opening port when necessary, sounds as extreme as using p2p stack and holepunching, just more browser friendly.
I need to look more at pkarr; I haven’t tried it since you released it a few months ago but I’m intrigued
#[7]
Well, now is a good time because I just got it to work from behind NAT.
Long story short it is a decentralized root DNS server, you can publish any Resourfe Records for a ed25519 public key and anyone can resolve it from anywhere.
Limitations: it is slow so you need to cache it aggressively, and it is ephemeral so someone needs to keep republishing it every hour or so.
```
npm i -g pkarr
pkarr publish
```
Once you are done you can run the pkarr keepalive command, or just give me the key and I will keep it alive for you.
Plenty of work can be done to make it a robust system and add DNS over HTTPs, but I feel getting feedback is as important at this stage.