{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihb375g6s2ojp7zuyeuj7nkcmztr4l4wrvdyfu2iy63jcbvlqg5wa",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mogbkgm5rhv2"
  },
  "path": "/t/curl-summer-of-bliss-curl-will-not-process-security-vulnerabilities-in-july/38553#post_6",
  "publishedAt": "2026-06-16T16:18:46.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "@maqp",
    "@EsperZero"
  ],
  "textContent": "response to @maqp and @EsperZero . No one is forcing anyone to work on Curl, so I don’t get the ‘enslavement’ narrative. As I said, there are probably multiple maintainers so they can just put one of them in standby while other take vacation and rotate that way.\n\nAlso, I will reiterate that I don’t get why they have to take vacation all at the same time. The reason you create a project with an institution is precisely so it doesn’t rest on the shoulder of one maintainer. That also means you should get the benefit of both being humane (allowing off-time) and being reliable (having off-time for devs without abandoning the project).\n\nAnd again, even if you were to do such a thing, don’t announce it in advance… And don’t release a new version a week prior.",
  "title": "Curl summer of bliss (curl will not process security vulnerabilities in July)"
}