{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaequcfs6t7k5knlbjq6smffvvp3hpovgsnqvks64nsesb57jyaoq",
    "uri": "at://did:plc:hwpfviglvxef74s5w4fhywt7/app.bsky.feed.post/3mdtesjpwwrx3"
  },
  "contributors": [
    {
      "did": "did:plc:dqehxkfb3kv6bx7tfkvyzdt4",
      "role": "author"
    }
  ],
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidlr7pssytulurkdc6u6wg5ovzcb5dv6moxeqf5lsdtf3sfexwyae"
    },
    "mimeType": "image/png",
    "size": 45338
  },
  "description": "As I’ve written about before, I use Tailscale for a lot of things. I thought I had it set up in a reasonably secure manner, but I recently noticed a problem. I use Tailscale’s ACLs to limit what each node can access, based on the tags I apply to it. So an app node can’t access anything via Tailscale, while an integration or server node can access things tagged with either app or ...",
  "path": "/tailscale-docker-gotcha/",
  "publishedAt": "2026-01-29T00:00:00Z",
  "site": "at://did:plc:hwpfviglvxef74s5w4fhywt7/site.standard.publication/3mnmr7tmggs2e",
  "title": "An interesting Tailscale + Docker gotcha"
}