idan
Support private gists
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.
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.
I would also appreciate this feature. Sometimes you might want beautiful texts, but not have them appear in your gist timeline.
Will have a think about it. Right now the service explicitly only supports public gists.
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
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.
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?
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 [email protected] 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.
Was this pull request accepted? I would also appreciate this feature. Merge!
I'm planning on implementing this, but a lot of changes under the hood will render #51 moot.
Working on it :) On Sep 23, 2013 10:08 AM, "Sergey Klimov" [email protected] wrote:
Please support it
— Reply to this email directly or view it on GitHubhttps://github.com/idan/gistio/issues/17#issuecomment-24902076 .
@joallard You should make a fork and host it on your own! Call it gist2.io!
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.
@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...
@idan ✔️ Issue can be closed.
Working URLs:
https://gist.io/85126ceb850513ecc276➡️ https://gist.io/@divideby0/85126ceb850513ecc276https://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:noneheader
I'd suggest opening a dedicated issue for that if it is (still) desirable.
