{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiauq2xglyosi5nt4juuw4rtrywfkkne55zr4a6af3k2d4nv7lm4am",
    "uri": "at://did:plc:q2k4ilmlzzrnoog5dccpqwor/app.bsky.feed.post/3mj326dhwiys2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreicefhpdqt5texjvkafujqtgbon4dqiatpdmbaxujjutauppmmeefq"
    },
    "mimeType": "image/webp",
    "size": 77280
  },
  "path": "/post/45682520",
  "publishedAt": "2026-04-09T10:59:10.000Z",
  "site": "https://lemmy.ml",
  "tags": [
    "Linux",
    "TheIPW",
    "13 comments",
    "https://the.unknown-universe.co.uk/privacy-security/little-snitch-linux/"
  ],
  "textContent": "submitted by TheIPW to linux\n66 points | 13 comments\nhttps://the.unknown-universe.co.uk/privacy-security/little-snitch-linux/\n\nI saw the news about Little Snitch coming to Linux via eBPF and Rust. On paper, it looks fancy. In reality, the backend is closed source.\n\nPersonally, I don’t see the point in installing a proprietary black box to monitor other black boxes. I’m sticking with my AdGuard Home setup and OpenSnitch for when I actually need to trace a binary.\n\nI wrote up my thoughts on why I think this is a solved problem for most FOSS-first home labs.",
  "title": "Why I’m skipping the proprietary \"Little Snitch\" for Linux"
}