The URIs of all gist comments are changing immediately. The new URI pattern for gist comments is`/gists/{gist-id}/comments/{id}`. (See[gist comments section of the docs](/v3/gists/comments/) for more details.) This change is necessary because the auto-incremented ids of gist comments are easy to guess. This predictability allows anyone to view comments on private Gists with relative ease. Obviously, comments on private gists should be just as private as the gist itself.

Adding theid of thegist id to the URI makes it impossible, in practical terms, becausethat idis avery large randomnumber. This is, unfortunately, a breaking change but one that cannot be avoided because of the security implications of the current URIs. We apologize for the inconvenience.

Adding the gist id to the URIof commentsmakes it impossible, in practical terms,to guess the URI of abecausethe idof private gists arevery large randomnumbers. This is, unfortunately, a breaking change but one that cannot be avoided because of the security implications of the current URIs. We apologize for the inconvenience.

For your convenience wehave also added a`comments_url` member to the Gist documents. The`comments_url` link provides access to the comments of a Gist in a way thatis resilient to changes in the URI patterns used by the GitHub API. We are increasing our use of links in order to make changes such as this one less damaging to clients. We strongly encourage using`url` and`*_url` properties, where possible, rather than constructing URIs using the patterns published on this site. Doing so will result in clients that break less often.

Wehave also added a`comments_url` member to the Gist documents. The`comments_url` link provides access to the comments of a Gist in a way thatwill insulate clients from changes in the URI patterns used by the GitHub API. We are increasing our use of links in order to make changes such as this one less damaging to clients. We strongly encourage using`url` and`*_url` properties, where possible, rather than constructing URIs using the patterns published on this site. Doing so will result in clients that break less often.