1. Trust & Possible Phoning‑Home
“Do you still trust them not to do self‑reporting or phoning home, even though it is $0 and closed source?” — righthand
2. Openness vs. Closed‑Source Model
“OpenSnitch is open source. You don't need to trust it as you can see the code yourself. Little Snitch on the other hand, is completely closed source.” — dizhn
3. Linux vs. macOS Technical Limits
“Little Snitch for Linux is built for privacy, not security, and that distinction matters. The macOS version can make stronger guarantees because it can have more complexity. On Linux, the foundation is eBPF, which is powerful but bounded: it has strict limits on storage size and program complexity… The macOS version uses deep packet inspection to do this more reliably. That's not an option here.” — littlesnitch
4. Process Identification & UI Feedback > “Little Snitch must be running when the process starts in order to identify it correctly. You get less ‘Not Identified’ if you run it for a while, or you should get none if you reboot and Little Snitch can start before everything else.” — littlesnitch
5. Business Model & Monetisation Concerns
“I would be fine with a commercial license with source available here… the issue isn’t the price, it’s the fact that you’re asked to MITM every network connection you make under the control of a binary blob.” — foo12bar