pull down to refresh
0 sats \ 2 replies \ @justin_shocknet 5 Dec 2023 \ parent \ on: Find Your Co-Founder/Building Partner on Stacker News! ⚡ bitcoin
Nostr would add unnecessary overhead to that, but you could wrap in the elements you want (like the identity keys) with regular sockets. Tunneling SSH over WS is not entirely uncommon.
lol, you must be in the MSP world... my condolences
Nostr relays are like rendesvous points on the internet, which could replace the need for many centralized services, such as RMM services.
Nostr would add unnecessary overhead to that
Tor imposes a lot of overhead, but SSH works well when connecting to a server via a Hidden Service, which involves multiple TLS tunnels.
This program/protocol would only use ephmeral events, so only a few NIPs need to be implemented.
lol, you must be in the MSP world... my condolences
Thankfully I am not really in the MSP world. But, a part of my job requires that I use an RMM service, which is very rough around the edges, due to some serious design flaws.
I have looked at all other options, and making a new protocol is the only option -- well, other than quitting this job.
reply
Nostr relays are like rendesvous points on the internet
I was just comparing to a more general socat-like server, but yea compared to Tor it'd still be a massive improvement and might have added benefits by being able to hide amongst other traffic on public infrastructure.
ephmeral events, so only a few NIPs need to be implemented
You probably wouldn't need any in that case as the relay will just dump them, your protocol would just be an application that uses nip01 as it defines kind ranges for ephemeral events... then yours is just an application with a specific kind, there's a few like that including ours: https://github.com/nostr-protocol/nips#event-kinds
reply