You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/changes/2012-10-31-gist-comment-uris.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,6 @@ author_name: pezra
7
7
8
8
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.
9
9
10
-
Adding the gist id to the URI of comments makes it impossible, in practical terms, to guessthe URI of a because the id of private gists are very large random numbers. 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.
10
+
Adding the gist id to the URI of comments makes it impossible, in practical terms, to guessthat URI because the id of private gists are very large random numbers. 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.
11
11
12
12
We have 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 that will 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.