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

The unofficial Google shell

goosh.org

Post reply on HN
Print view View original

11–20 of 56 posts

Re: The unofficial Google shell

#11

Post by keyle »

Wow I've been thinking of writing something very similar lately using nodejs and parsing the html (maybe using lynx --dump). But this is pretty much as good idea and blazing fast!

Re: The unofficial Google shell

#12

Post by pfarrell »

JonnieCache wrote: post #7
djacobs wrote: post #6

Very cool. `man login` says that you only see the username we type in. How are you authenticating?

I'm guessing it all happens client side from the browser.

I don't want to "guess" that. I'd like it really spelled out. I tried "login" and got a 500 from a debian server. I wouldn't send my credentials through some random server just because it was on HN.

--edit: I was wrong, it wasn't a 500 error, it was a 404. I don't want to cast too much suspicion here, just making a point about being appropriately paranoid about giving out my creds. This site could be totally cool, I want it transparent to me before I login.

Re: The unofficial Google shell

#17

Post by zheng »

cleverjake wrote: post #2

http://news.ycombinator.com/item?id=1025039

Here's how I see reposts. I agree that people shouldn't just repost things because they were popular at one point, and they want the karma. However, realize that for people who weren't around when that was posted (over a year ago), this is pretty cool. There is also no way I would have ever thought "Hey, I wonder if there is a shell-esque interface to google? Oh, I bet HN will have a link about it! Let me go search!". So, I think when spaced out enough reposts are good. Over a year seems like long enough to me.

Re: The unofficial Google shell

#18

Post by elliottcarlson »

pfarrell wrote: post #12
JonnieCache wrote: post #7

Earlier quoted context omitted.

I'm guessing it all happens client side from the browser.

I don't want to "guess" that. I'd like it really spelled out. I tried "login" and got a 500 from a debian server. I wouldn't send my credentials through some random server just because it was on HN. --edit: I was wrong, it wasn't a 500 error, it was a 404. I don't want to cast too much suspicion here, just making a point about being appropriately paranoid about giving out my creds. This site could be totally cool, I…

I'm assuming it's trying to load an OAuth screen - but the page is broken so won't even work to begin with.

Re: The unofficial Google shell

#19

Post by djacobs »

JonnieCache wrote: post #7
djacobs wrote: post #6

Very cool. `man login` says that you only see the username we type in. How are you authenticating?

I'm guessing it all happens client side from the browser.

While the client side has some login-related logic, it looks like authentication happens server-side.

From the source:

  goosh.module.login = function () {
    this.name = "login";
    this.aliases = new Array("login");
    this.help = "login with your google account *";
    this.helptext = "goosh sees only your username";
    this.parameters = "";
    this.cb = function (A, B) {
      if (goosh.ajax.iscontext(A)) {
        if (B && B != "guest") {
          goosh.lib.cookie.set("loggedin", "1", 365)
        }
        goosh.config.user = B;
        if (goosh.config.user != "guest") {
          goosh.gui.outln("You're logged in as: "
            + goosh.config.user + "
");
          goosh.set.init();
          goosh.gui.updateprompt();
          goosh.gui.showinput();
          goosh.gui.focusinput();
          goosh.gui.scroll()
        } else {
          goosh.ajax.query("http://goosh.appspot.com/dologin?")
        }
        goosh.gui.showinput();
        goosh.gui.focusinput();
        goosh.gui.scroll()
      }
    };
    this.call = function (A) {
      goosh.ajax.query("http://goosh.appspot.com/
        status?callback=goosh.modobj.login.cb")
    }
  };
  goosh.modules.register("login");
Post reply on HN