1. I haven't look closely enough to solve this bit just yet. 2. Use a gadget that goes with the robot (can the robot add it?) that you can fill in information (maybe even store a cookie for next time).
3. 2 would contain this information (URL, user, pass, title=subject). My thoughts would be to add robot as first participant, have robot store info then clear gadget to protect info before adding more participants. 4. To fake events, they need your password. 5. Of course. The post is created and editted in a single (i believe the proper term is wavelet). When people that you add to the wave reply, these are the comments. When a non wave user replies on the site, the robot creates a wavelet for that person. 6. If somebody besides the wave creator (stored by the robot) tries to edit the main wavelet, the robot does not publish the result and resets the content to the last published. 7. Yes, this would require custom software, but I can help with this. Christopher Baker On Nov 9, 2009, at 8:22 AM, David Nesting <[email protected]> wrote: > On Sun, Nov 8, 2009 at 11:52 PM, Christopher Baker <[email protected] > > wrote: > Personally, I think that the blogs with waves embedded in them look > rather funny, even with matching colors. I would think that the best > option would be to create a robot that updates the blog based on the > wave content. I plan on finding out if anybody has done this, or > doing it myself, although I have not had the time to do this. > Perhaps there's even a simple way? =] > > I'm playing with doing this. Unfortunately it's not > straightforward, and at least two Wave bugs preclude a well-designed > solution, IMO. There are several issues I'm thinking of ways around: > > 1. Serializing the blip to HTML. It's easy enough to generate <p> > and <br> elements to get the structure of the blip, but what about > overlapping annotations? Embedded gadgets? Images[1]? > > 2. How does the robot authenticate to the place you'll store the > content? Bloggy solves this by hosting the content locally. This > pretty much requires something like OAuth. If the target for your > content doesn't support that, that may mean more work implementing it. > > 3. When you add the robot to the wave, how does the robot know where > to send the content? What if multiple people want to use the same > robot to post to separate places? More UI/configuration needed. > > 4. How does the robot know that the events it's receiving from Wave > are legitimate[2]? You don't want someone sending fake events that > cause the robot to publish something it's not supposed to. > > 5. Do you plan to integrate comments? How? > > David > > [1] http://code.google.com/p/google-wave-resources/issues/detail?id=61 > [2] http://code.google.com/p/google-wave-resources/issues/detail? > id=344 > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave 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-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
