Thanks for clearing that up, I was a bit taken back by the use of the word illegal for scraping websites. I suspect that we will start to see the nature of scraping change in the near future as websites become the API. Pages written in valid XHTML/HTML 5 with meaningful naming conventions (like micro formats). I don't think scraping can be a dirty word anymore. But I can understand the need for a company like Google to control where and how the bandwidth is used.
Rich On Oct 14, 4:11 am, "pamela (Google Employee)" <pamela...@gmail.com> wrote: > Sure, good point, let me clarify, though please keep in mind that I'm not a > lawyer... > > According to the Google Wave terms of use, it is not permitted to "modify, > adapt, translate, or reverse engineer any portion of the Service unless > expressly authorized". In Oliver's prototype, he essentially reverse > engineered the client display mechanism to extract the content. You can read > more of the policies at:http://wave.google.com/help/wave/program_policies.html > > Once we have an API to let you programmatically extract the content -- which > is something we're working on -- then that API could be used to build this > prototype without having to reverse engineer. Another thing to consider, > more in the wave protocol effort, would be a client/server protocol -- but > things are early there at the moment. > > - pamela > > On Wed, Oct 14, 2009 at 1:48 PM, Joe Developer > <joe.d.develo...@gmail.com>wrote: > > > > > On Wed, Oct 14, 2009 at 7:42 AM, pamela (Google Employee) < > > pamela...@gmail.com> wrote: > > >> Hey Oliver- > >> I responded to you offline, but will also respond here to keep the thread > >> in the forum. > > >> I assumed that was how you were doing this, but wanted to give you a > >> chance to explain. It is generally considered illegal to "scrape" the HTML > >> of webpages that do not grant explicit permission for that. That is why > >> webpages provide APIs- so that developers can legally use content. > > >> Really? Generally considered illegal? I would appreciate a link that > > documents such a finding. I would imagine that google search results would > > be fairly sparsely populated if they could only include those pages that > > include explicit permission for google to scrape. > > > I would advise on waiting until we offer some sort of Google data API to > >> distribute a program like this. > > >> - pamela > > >> On Wed, Oct 14, 2009 at 8:27 AM, Oliver Baker <ocba...@gmail.com> wrote: > > >>> How dare you Andrey! > > >>> I do not store any of your information what so ever excluding the last > >>> Wave server you selected. > > >>> Any Login information you enter is immediatly put into the Google Wave > >>> Login page to log the application into the Google Wave login page. > > >>> To enter your login details on Version 2 (Sorry I made this a little > >>> stupidly) you will need to left click on the Notify Icon or right > >>> click the icon, go into the Waves item, then click the login to see > >>> your waves button. > > >>> Also, make sure you have Google Chrome Frame installed on your > >>> computer for this to work. I am still working out the bugs. > > >>> On Oct 14, 10:07 am, Andrey Fedorov <anfedo...@gmail.com> wrote: > >>> > Uhoh, I hope you guys are at least running antivirus as you run exe's > >>> you > >>> > downloaded online? > >>> > - Andrey > > >>> > On Tue, Oct 13, 2009 at 2:15 PM, Scott Breakall <break...@gmail.com> > >>> wrote: > > >>> > > I've downloaded the exe, but am I missing something? There's nowhere > >>> > > for me to enter my wave credentials? > > >>> > > ~Scott~ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
