Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Foobar

google.com

Post reply on HN
Print view View original

81–90 of 178 posts

Re: Foobar

#81

Post by wanda »

alvarosm wrote: post #76
wanda wrote: post #73

Reminds me of HackThisSite & notpron. I have many happy memories of my peers sweating at the thought of not solving those puzzles. +1 to Google HR department, they know what they're doing. It'd be amusing if it was a social experiment to see how many devs/wannabe devs frantically searched for Python topics after this foobar site was discovered. Like a contrast MRI to illuminate the people who wanted a job at Google.

yeah, no doubt... http://www.theregister.co.uk/2013/06/20/google_hiring_proced...

I didn't mean they'd hire good people, I just meant they know how to reach people.

Re: Foobar

#82

Post by dontreact »

dontreact wrote: post #79
barbudorojo wrote: post #62

In one of the js files there is window.opener.handleAuth(..), perhaps changin allow from false to true can result. This seem to be a js related essue.

When you click the login button, the following function is called: launchPopup=function(){ window.open("/login/","AppLogin","resizable,scrollbars,status,width=600,height=400")} Which opens https://foobar.withgoogle.com/login There, an object a: a = { message: ' Error(6): Login unavailable. Try again later. ', logoutUrl: 'https://foobar.withgoogle.com/_ah/logout?continue=https://www.google.com/accounts/Logout%3Fcontin…

Put more simply, you can redefine the handleAuth function to automatically set the allow property to true

window.handleAuth=function(a){ a.allow = true; a.logoutUrl?window.location.href=a.redirectUrl:window.location.reload()}

and then click the button.

But it won't help for the reasons explained above.

Re: Foobar

#84

Post by danielweber »

Reef wrote: post #58
jcfrei wrote: post #48

Earlier quoted context omitted.

Very interesting but I wonder what the legal implications are. Some companies might file a lawsuit claiming that Google gains an unfair advantage if they continue to seek potential employees this way. I'm not saying I agree with this view but Google does have a HUGE potential in matching employees with their potential employers and might just turn the recruitment services industry on its head.

Is there a law which specifies which advantage is fair and what is not? Why should any company be forbidden from utilizing assets their employees legally developed, especially when they want to use that asset in pursuit of a key objective ("hire more smart people")? Should a large newspaper be forbidden from advertising their openings in the printed newspaper itself just because other newspapers failed to acquire com…

The legal question is if there is a disparate impact.

On a personal level, I really don't like "we hire Python devs if you search on Google for python topics," but that's separate from saying there is a legal challenge here.

Re: Foobar

#85

Post by toblender »

I got a little further.

If you append /login to the url, you get another script:

Points to:

https://foobar.withgoogle.com/_ah/logout?continue=https://ww...

I've tried some ways to login to appengine etc but didn't work.

https://appengine.google.com/_ah/logout?continue=https://foo...

I've managed to get it to log me out of my google account. Not sure what's up.

Re: Foobar

#86

Post by barbudorojo »

jengamaster wrote: post #72
barbudorojo wrote: post #62

In one of the js files there is window.opener.handleAuth(..), perhaps changin allow from false to true can result. This seem to be a js related essue.

That was my thought too, although I'm not sure how it would be done.

I was thinking about a = document.getElementbyId("login"); a.addEvenListener("click",function(a){a.preventDefault()...}

Perhaps if one can avoid preventDefault the object login may has some href to the real login. Just guessing.

Re: Foobar

#87

Post by toblender »

toblender wrote: post #85

I got a little further. If you append /login to the url, you get another script: Points to: https://foobar.withgoogle.com/_ah/logout?continue=https://ww... I've tried some ways to login to appengine etc but didn't work. https://appengine.google.com/_ah/logout?continue=https://foo... I've managed to get it to log me out of my google account. Not sure what's up.

Also I get:

Error(6): Login unavailable. Try again later.

Re: Foobar

#88

Post by Ironchefpython »

rudolf0 wrote: post #71
NamTaf wrote: post #23

Earlier quoted context omitted.

That sounds right, which implies that you have to be logged in to a google account and searching interesting terms to them. They'll redirect you to that and you can carry on.

I Google Python-related things all the time from work, including yesterday and today, but I prefer not to login to any of my Google accounts when doing so. I've not yet received any kind of popup or redirection to foobar.

> I Google Python-related things all the time from work, including yesterday and today, but I prefer not to login to any of my Google accounts when doing so.

Same thing here... I'm guessing that Google figures anyone cynical enough not to trust Google implicitly is a less desirable potential hire.

Re: Foobar

#89

Post by Donzo »

toblender wrote: post #85

I got a little further. If you append /login to the url, you get another script: Points to: https://foobar.withgoogle.com/_ah/logout?continue=https://ww... I've tried some ways to login to appengine etc but didn't work. https://appengine.google.com/_ah/logout?continue=https://foo... I've managed to get it to log me out of my google account. Not sure what's up.

I got one like this.

https://appengine.google.com/_ah/conflogin?continue=https://...

Throws a 500 error.

Re: Foobar

#90

Post by jengamaster »

abdullahdiaa wrote: post #83
josu wrote: post #77

Interestingly https://www.google.com/foobar/ and https://foobar.withgoogle.com/ seem to be the same page, but they have different source codes.

Actually https://www.google.com/foobar wraps https://foobar.withgoogle.com in an iframe with [absolute/top:0/left:0] positioning.

Also https://www.google.com/foobar uses JS to set the src of the iframe holding https://foobar.withgoogle.com and appends window.location.search to it.
Post reply on HN