Support private gists

[divideby0]

Not sure if this is an intentional incompatibility, but this:

https://gist.github.com/85126ceb850513ecc276

Does not appear to map to this:

http://gist.io/85126ceb850513ecc276

When I attempt to access the gist.io link, I get a 404.

[divideby0]

It would appear that this is due to the routes taking an int as the gist id. As far as I can tell, private gists don't have a numeric id, but can only be referenced via hash.

[tobiastom]

I would also appreciate this feature. Sometimes you might want beautiful texts, but not have them appear in your gist timeline.

[idan]

Will have a think about it. Right now the service explicitly only supports public gists.

[vlucas]

If you do eventually support this, make sure to add the appropriate tags and HTTP headers so the content will not get cached or crawled by search engines: http://www.i18nguy.com/markup/metatags.html

[divideby0]

It might also be enabled as an option via configuration, in case someone wants to run a private-label gist.io on their own site, linking only to their own private gists.

[franciscolourenco]

+1

[joallard]

I've polled the Github API, and it works the same with getting public and private Gists.

So if I understand correctly, we just have to make the routes accept a hash and put a Robots:none header and that's it? Or am I missing something else here?

[divideby0]

That is correct. I wound up implementing this in a grails project as I
needed the feature on a public website and can confirm this approach works.

Sent from my iPad

On Nov 25, 2012, at 11:17 AM, Jonathan Allard notifications@github.com
wrote:

I've polled the Github API, and it works the same with getting public and
private Gists.

So if I understand correctly, we just have to make the routes accept a hash
and put a Robots:none header and that's it? Or am I missing something else
here?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/17#issuecomment-10695722.

[shortcircuit3]

Was this pull request accepted? I would also appreciate this feature. Merge!

[joallard]

@milesalex The maintainer hasn't responded

[shortcircuit3]

@idan - Please?!

[idan]

I'm planning on implementing this, but a lot of changes under the hood will render #51 moot.

[darvin]

Please support it

[idan]

Working on it :)
On Sep 23, 2013 10:08 AM, "Sergey Klimov" notifications@github.com wrote:

Please support it

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-24902076
.