Hey everyone... I just found a new service that Google hasn't yet announced... Google Mars.
http://blogs.zdnet.com/Google/?p=128 |
unfortunately, the links do not work for this service yet... but don't forget to search for "face"
GREAT find (as usual) Garett! |
And we have a doodle
http://www.google.com/logos/mars06.gif
http://www.google.com/logos/mars06_res.gif
(the link to the known address) |
i smell "april fools" here =) probably because its not yet for release until the date and in "beta" as usual.
Hey would'nt it be cool if Google would allow to register lands (per sq. ft) using your Google Account, so when someone goes to say a long/lat destination anywhere in Mars, that land would be marked as: "Registered to Josue R." .... Now if they get to map other worlds too besides Mars, they have a killer web-app for Earthlins to explore. Hopefully the land is not free and free from "martian ownership".
** Google, hopefully you're reading this message ;)
|
Correction:
i meant to say "hopefully the land is free-of-charge" --- no monetary value |
Josue: use the APIs and code it by yourself ;)
And my green alien should where glasses |
found this under the Google Mars javscript, probably not important (yet) but curious for now...
// Where does the data come from?
// var mapsServer="conspiracy.mars.asu.edu";
// var mapsServer="dhcp-172-24-105-125.corp.google.com";
http://www.google.com/mars/javascript/main.js |
More info on why Mars is probably the precursor to a larger project:
http://thegooglist.blogspot.com/2006/03/google-galaxy-starts-with-mars.html
|
plz go to http://www.javajuggler.blogspot.com a small perl prog traverses thro
google server. |
Josue R. > really strange discovery.
"dhcp-172-24-105-125" must be an IP of a local network.
|
Tom & Josue
I think that is a rest out of testing. Devs mostly use their own machines to test software/pages
And *.corp.google.com looks really like an internal part of google.
And the JavaScript does not look crypted, like all the other Google JSs out there. |
perl webchecker.pl
[I've put the contents of this post here:
http://blogoscoped.com/files/perl-checker.txt
-Ed.] |
Some cool detective work here :) |
Discovering internal/local ip's can only lead to vulnerbilities in Google's network. Knowing only this can make anyone scan a range of ips and lead to a weak insecure machine that can be brute-forced and broken in time which then would allow for the "hacker" to find more Google secrets which then would ruin Google. But see, this is just my theory. Googlers should be more careful. |
