Hacker News new | ask | show | jobs
by rajasimon 1546 days ago
Oh I got it. There is multiple reason that can happen and I called those are Ghosts accounts. There is high chance if you request to GitHub they will grant use it.
4 comments

> those are Ghost accounts… high chance if you request to GitHub they will grant use

From sibling comment:

    wheybags 0 minutes ago | root | parent | next [–]

    My username is wheybags on github, I actively use the account, 
    both public and private repos, and it shows as available on your site.
This doesn’t sound like a ghost account.

More to the point, I’m reasonably aggressive about registering my preferred nick, and your site thinks it is available where it is definitely in use by me.

GitHub shows available, it is not.

Based on what comes up as green vs. red when I test your site, it occurs to me you may be failing to detect the difference between public and private preference settings. For instance, if someone turned off public search preference, or public graph.

Chiming in here — not sure about this. I checked for a name that showed as "available" on the link above. I requested the owner of that Github handle a year ago if they were willing to release it to me, as they have zero public repos on there. Long story short, they didn't.

No chance that Github will take the handle off them and give it to us too.

My point is, this is definitely a bug, since the above account is not a ghost account.

This is also not working for me on Github, Facebook and Instagram...

I don't think it has anything to do with Ghost accounts, maybe your app has reached some quota limit...

When I try the api link with my account*, I get the data returned.

On the site, it says my account is available.

When I put something random on the api link, it returned the not found message.