rvermeulen98

5 ms·

1. 1.▲
   by rvermeulen98 9mo ago

   Just released version v0.2.1 eliminating the need for CGO, thanks for your contribution!
2. 2.▲
   by rvermeulen98 9mo ago

   The goal has never been to create something that can replace nmap, the goal was to learn more about networking and about building TUIs in Go. Honestly I am quite overwhelmed by the amount of traction it got today, definitely not what I expe
3. 3.▲
   by rvermeulen98 9mo ago

   In the current version yes, never intended to build it as pure cli app. But if there is a lot of interest in this functionality this is something I can focus on in upcoming releases.
4. 4.▲
   by rvermeulen98 9mo ago

   I started off using tview/tcell, and only later found out about bubbletea and the charmbracelet ecosystem. Then I didn't really find a solid reason to switch over to bubbletea. So far I really enjoyed the experience building the a
5. 5.▲
   by rvermeulen98 9mo ago

   Would it help to get it on the "official" homebrew, instead of a custom tap/cask? Might try to do an application for that somewhere in the upcoming weeks.
6. 6.▲
   by rvermeulen98 9mo ago

   Thanks a lot for your contribution, this is something I will look into in the upcoming days. I totally agree that CGO isn't ideal, I had to make the build/release process also a lot more complicated purely for that clipboard requi
7. 7.▲
   by rvermeulen98 9mo ago

   Thanks for sharing! This is definitely something I will look into, I am all in favor to simplify the current implementation of finding the "default" OS network interface.
8. 8.▲
   by rvermeulen98 9mo ago

   I think this is only a problem when building from source, right? It is indeed because of the dependency on https://github.com/golang-design/clipboard . I hesitated a bit bringing in this feature. On one hand, I really l
9. 9.▲
   by rvermeulen98 9mo ago

   Thanks, I am glad you like it! I couldn't find a Go API that just returns the OS "default" network interface, so struggled a bit with a correct implementation for that part. When reading some blog posts, I found often a solut
10. 10.▲
    by rvermeulen98 9mo ago

    It doesn't start port scanning by default, maybe this is a feature I can build in the future. When you are on the `detail` view of a device, you can press `p` and that will open a pop-up to perform the port scan. Also the list of ports
11. 11.▲
    by rvermeulen98 9mo ago

    That's correct. To avoid overloading the local network, the initial scan has a built-in safeguard: 1. It only scans the subnet of the configured network interface. 2. The scan is limited to a maximum size of a /16 subnet. 3. It ru
12. 12.▲
    Show HN: Whosthere: A LAN discovery tool with a modern TUI, written in Go(github.com)

    278 points by rvermeulen98 9mo ago|89 comments
13. 13.▲
    by rvermeulen98 9mo ago

    I've been working on a LAN discovery tool with a Terminal User Interface (TUI) written entirely in Go. It's called Whosthere, and it's designed to help you explore devices on your local network without requiring elevated pri