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/idan/gistio/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/idan/gistio/issues/17#issuecomment-24902076 .

[jvns]

It would be amazing if gist.io supported private gists :)

[jvns]

Is there anything I could do to help this to happen?

[joallard]

It's now been a year my rejected pull request has been submitted.

[shortcircuit3]

@joallard You should make a fork and host it on your own! Call it gist2.io!

[datenreisender]

Sadly gist.io is not just having problems with private gists. At the moment it also cannot handle gists that once where private but then turned public.

This is, what I just tried with https://gist.github.com/datenreisender/0128e842631b1c0b908f . After making it public I wanted to create a nice gist.io link for it but then discovered that http://gist.io/0128e842631b1c0b908f does not work.

Only way for me to solve it would be to copy the content into a new gist that was public from the beginning on. But since this does not fit my workflow I rather abstained from creating a gist.io link.

[x3ro]

@datenreisender You could try draft.sx (disclaimer: my own fork). I would normally not announce that here, but since @idan seems to have abandoned the project...

[Potherca]

@idan ✔️ Issue can be closed.

Working URLs:

• https://gist.io/85126ceb850513ecc276 ➡️ https://gist.io/@divideby0/85126ceb850513ecc276
• https://gist.io/0128e842631b1c0b908f ➡️ https://gist.io/@datenreisender/0128e842631b1c0b908f

---

Regarding

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

or

a robots:none header

I'd suggest opening a dedicated issue for that if it is (still) desirable.