On Jun 8, 4:59 pm, Andrew Leach <[email protected]> wrote: > On Jun 8, 7:33 am, stang <[email protected]> wrote: > > > There seems to be an alarming silence about Google's insane decision > > to shut down Googlepages and move everything to Google sites instead. > > The latter does not allow javascript and so is incompatible with > > Google Maps. Apparently this is a security feature, although I know > > enough about security to find that claim rather dubious. > > It *is* a security feature, though whether it's a justifiable one may > be debatable. But presumably because every site is on the same domain, > (x.googlepages.com), it's impossible to stop cross-domain scripting > between different googlepages sites. Is there anything on any googlepages sites that needs to be secure? If so, the problem could be solved by Google simply telling everyone not to use the site for sensitive information. But if not, there is no security problem.
> That's fine when it's a company's > own website with different subdomains; more of an issue with entirely > separate people on each subdomain. Most ISPs offer web hosting for their clients. Are these all insecure? > > However, it's also difficult to see how Google could make money out of > Google Pages. With Groups and Mail for example, they can advertise in > the sidebar. Firstly, getting a GMail account was a requirement for getting a googlepages site. Secondly, it is not difficult at all: they could advertise on the site management page (the one that users land on when they go to www.googlepages.com). And of course the stuff uploaded could be used by Google to target the ads. > > > The obvious implication of this shutdown is that not only do we lose > > the best free host on the entire internet, but we will all start > > having to worry about API keys again, and have to change them every > > time each page is moved. > > Every time each page is moved? You would have to get a new key if you > moved your pages out of the googlepages.com domain -- with a key for > "googlepages.com" your pages would work in any subdomain. You don't need a key at all for googlepages.com, and if you move from another site to there it still works despite having the wrong key! But take the page somewhere else and you need one key for your ISP to test things and one for the domain you're uploading to. Of course those could be the same, but then if I switch ISP (which is not just a commercial decision - I may move to a different country for example) I'd need to change the key on every maps page... > I agree that Google Pages is probably the best free host on the net. > > > I expected there to be a lot of outrage about this in the Google Maps > > API group, but there is no mention at all. Why not? Is nobody else > > aware? Are there moderators censoring all mention of it? Or is there a > > way to keep maps pages hosted on Google? If so, what? > > There has been mention of > it:http://groups.google.com/group/Google-Maps-API/search?group=Google-Ma..."Google+Sites" I see now - I had searched, but not that far back, as when they stopped accepting new members, the problem didn't affect me. > and the moderators are not censors. I don't believe there is a way to > keep map pages hosted by Google :-( and I guess that most maps users > don't use Google Pages. They haven't been accepting new members for > ages, and the announcement about its shutting down was made at least > nine months ago. > But the announcement failed to mention that Google Sites couldn't do the things that googlepages could. > I believe that for good hosting of a fairly permanent site, it's > necessary to pay for it. But why should it be necessary to pay many dollars for a site that costs a few cents to host? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
