narragansett

4 ms·

1.
by narragansett 2mo ago
thanks for the catch :)
2.
by narragansett 2mo ago
Pls see reply above.
3.
by narragansett 2mo ago
You actually bring up a good point. v6 genuinely helps here. It gives every device a routable address, so no nat, but it doesn't open a hole through the firewall, which still defaults to blocking inbound, and it doesn't address au
4.
by narragansett 2mo ago
Yes, I started using AI for coding (Claude Code) after much consternation -- it's been really good at boosting my productivity. This is a passion project I tackle in my spare time, I like coding, but I don't like much of the cod
5.
by narragansett 2mo ago
This is a really useful feature and on the top of my todo list https://github.com/richlegrand/bitbang-cli/issues/9
6.
by narragansett 2mo ago
Yes, that should work. "serve" prints the URL and the 6-digit pairing code to stdout, so your ssh session sees them, and shutting it down is just killing the process. One suggestion for the untrusted-PC part: bitbang serve -epheme
7.
by narragansett 2mo ago
Remote access lacks a certain amount of sex appeal -- thanks for reading the through the techno-babble and not giving up :) And yes -- open source and self-hostable is a big part it. The other half is that the connecting side can be a brows
8.
by narragansett 2mo ago
here's hoping! :)
9.
by narragansett 2mo ago
Iroh's discovery is genuinely neat, and node-IDs-as-public-keys is similar to bitbang. A browser can't join a DHT though because of no UDP sockets, so the connecting side would need a native client, which is the thing bitbang avoi
10.
by narragansett 2mo ago
Yes -- if direct P2P fails, everything rides the TURN relay that gets inserted automatically -- it's DTLS end-to-end so the relay only sees ciphertext, never plaintext or the access code. On cost: I pay for it on bitba.ng and it's
11.
by narragansett 2mo ago
Thank you -- and if you're the Sean who wrote Pion, this is built on your work, so that means a lot. :) The friends case is exactly the gap I kept running into. A mesh VPN is fine for my own devices and hopeless the moment someone else
12.
by narragansett 2mo ago
Right, bootstrapping needs a rendezvous point -- that's true of any P2P system, including the wg version. The difference is what the rendezvous knows and costs. Here it holds no accounts, no registry, and nothing that grants access, so
13.
by narragansett 2mo ago
It's a single Go binary, shaped like ssh. The main difference is the transport -- WebRTC instead of TCP -- so it doesn't need the machine to be reachable in the first place. Run "bitbang serve" and it prints a URL. Open
14.
Show HN: BitBang – Reach machines behind NAT from a browser, no account(github.com)
97 points by narragansett 2mo ago|39 comments
15.
Show HN: BitBang – P2P tunnels to localhost, no account required(github.com)
4 points by narragansett 6mo ago|1 comments
16.
Show HN: Qast – Cast anything (files, URLs, screen) to any TV from the CLI(github.com)
4 points by narragansett 7mo ago|1 comments
17.
by narragansett 1y ago
It's completely useless, but I still want one.
18.
by narragansett 3y ago
Agreed. IoT is a shitshow of ways to grab your data and PaaS monthly fees. Maker-friendly IoT like this is welcome. Remember Blynk? It started well enough, but became just another platform to coral its customers to the paywall.