| Website | https://driohq.net |
| Github | https://github.com/drio |
Very cool: @drio has built himself a physical button to play relaxing music in the bathroom, using my https://gokrazy.org/ #golang appliance platform! 🤘
Here’s his blog post: https://drio.sh/posts/relaxswitch-gokrazy/ (contains a demo video!)
@jnsgruk I enjoyed your post: https://jnsgr.uk/2024/07/how-i-computer-in-2024 .
What do you use to run syncthing in your iphone?
I recently switched from iOS to android because I wasn't happy I wasn't able to run syncthing in my phone (at least not in a straight forward way). After moving I discover things like the F-Droid store where you can find very interesting and more privacy aware apps.
I wrote a pretty bold statement in a presentation slide today:
"Wireguard is to networking what Linux was to operating systems"
Too bold?
Network Address Translation (NAT) causes well-known difficulties for peer-to-peer (P2P) communication, since the peers involved may not be reachable at any globally valid IP address. Several NAT traversal techniques are known, but their documentation is slim, and data about their robustness or relative merits is slimmer. This paper documents and analyzes one of the simplest but most robust and practical NAT traversal techniques, commonly known as "hole punching." Hole punching is moderately well-understood for UDP communication, but we show how it can be reliably used to set up peer-to-peer TCP streams as well. After gathering data on the reliability of this technique on a wide variety of deployed NATs, we find that about 82% of the NATs tested support hole punching for UDP, and about 64% support hole punching for TCP streams. As NAT vendors become increasingly conscious of the needs of important P2P applications such as Voice over IP and online gaming protocols, support for hole punching is likely to increase in the future.
Thank you @dgentry for sending the grafana/@[email protected] link. That is *extremely* useful!
If I may. I have big plans for tsnet and wasm but I am having issues (https://github.com/tailscale/tailscale/pull/8325). I think @bradfitz fixed it but I am still having issues. Am I doing something wrong? Maybe it is not possible to run tsnet via wasm yet?
@tailscale I am trying to run a tsnet app in the browser (wasm) but I get the following error when loading the wasm compiled go code in the browser:
tsnet: Executable not implemented for js. Do you know what may be happening here?
If I remove all the ts logic I can successfully run my code in the browser. Things fail when I incorporate the tsnet package and start my tsnet app.
Michael Stapelberg 🐧🐹😺
