[Google Wave APIs] Re: Public waves can be made non-public by anyone
Here is the application I was talking about: http://www.wavelot.com/ I just released a 'beta' version. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
But participants may want to be able to remove themselves. So my robot only re-adds two robots at the moment (that are needed for my application to function correctly). On Jun 11, 8:41 am, Nathanael Abbotts nat.abbo...@googlemail.com wrote: One test you should include - check if the person removed themselves (for i in event.participants_removed: if i != event.modified_by: add(i) ) On 10 June 2010 22:42, Anders blabl...@gmail.com wrote: I have written a robot that re-adds participants. It works really great! When one of the participants that gets re-added is removed by a user the robot instantly adds it back again. Within a fraction of a second. This hopefully solves the problem with keeping the waves public. An improvement would be to be able to set a filter so that my robot only gets called for those particular robots (only two at the moment) that I want to re-add. Because as it is now my robot of course gets called every time a participant is added or removed. That's a minor problem and will only become a larger problem if lots of people would use my application. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
Re: [Google Wave APIs] Re: Public waves can be made non-public by anyone
That's what I'm saying - people should be allowed to remove themselves - but I didn't realise that your robot only kept two robots in the wave. On 11 June 2010 08:11, Anders blabl...@gmail.com wrote: But participants may want to be able to remove themselves. So my robot only re-adds two robots at the moment (that are needed for my application to function correctly). On Jun 11, 8:41 am, Nathanael Abbotts nat.abbo...@googlemail.com wrote: One test you should include - check if the person removed themselves (for i in event.participants_removed: if i != event.modified_by: add(i) ) On 10 June 2010 22:42, Anders blabl...@gmail.com wrote: I have written a robot that re-adds participants. It works really great! When one of the participants that gets re-added is removed by a user the robot instantly adds it back again. Within a fraction of a second. This hopefully solves the problem with keeping the waves public. An improvement would be to be able to set a filter so that my robot only gets called for those particular robots (only two at the moment) that I want to re-add. Because as it is now my robot of course gets called every time a participant is added or removed. That's a minor problem and will only become a larger problem if lots of people would use my application. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Ok, yeah only two participants that are needed for my application to work. Maybe a few more in the future, but I will try to keep the number of needed default robots at a minimum. Basically the idea is to have the application be like a container for public waves sorted into predefined topics, similar to a general Internet forum. And only have restrictions when they are really needed. For example, in addition to re-adding the two participants it will have a captcha for creating new waves. Otherwise spammers etc could heavily abuse the automatic wave creation functionality. Yikes! On Jun 11, 5:18 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: That's what I'm saying - people should be allowed to remove themselves - but I didn't realise that your robot only kept two robots in the wave. On 11 June 2010 08:11, Anders blabl...@gmail.com wrote: But participants may want to be able to remove themselves. So my robot only re-adds two robots at the moment (that are needed for my application to function correctly). On Jun 11, 8:41 am, Nathanael Abbotts nat.abbo...@googlemail.com wrote: One test you should include - check if the person removed themselves (for i in event.participants_removed: if i != event.modified_by: add(i) ) On 10 June 2010 22:42, Anders blabl...@gmail.com wrote: I have written a robot that re-adds participants. It works really great! When one of the participants that gets re-added is removed by a user the robot instantly adds it back again. Within a fraction of a second. This hopefully solves the problem with keeping the waves public. An improvement would be to be able to set a filter so that my robot only gets called for those particular robots (only two at the moment) that I want to re-add. Because as it is now my robot of course gets called every time a participant is added or removed. That's a minor problem and will only become a larger problem if lots of people would use my application. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
As I have planned it at the moment there will be no need for the robot to remove participants. All waves in my application will be public. Including the possibility for public users to add all kinds of robots and gadgets to the waves. That will be very powerful but I hope it will not cause too much problems and mess. On Jun 10, 8:19 am, RAVINDER MAAN rsmaan...@gmail.com wrote: An other point which may relate to this is that at present robot can not remove participant.Any thought to deal with this issue? On Thu, Jun 10, 2010 at 6:10 AM, Anders blabl...@gmail.com wrote: I was thinking of having one robot creating all the waves in my application, and each time a wave is created the robot adds the public participant to the wave plus one or a few robots to provide default functionality (such as support for emoticons). So when a user creates a wave in my application, it's the one robot that always is the creator of the wave. And each time a participant tries to remove the public participant or any of the default robots in a wave, then the robot who created the wave gets informed about that through WaveletParticipantsChanged() and immediately re-adds the robot that was removed from the wave. Anyone can remove all the other participants in any of the waves in my application, but since the public participant is always re-added immediately, nobody is blocked from any of the waves and I thought it would be nice to allow anyone to add or remove their own robots to the waves which would potentially provide for powerful capabilities in the waves. I haven't checked if all these things are possible in practice but that's my plan at the moment. And I don't know all the details yet. For example is it possible to catch an event and then consume it before any action has taken place? Or when a robot receives an event, then the action has already happened. On Jun 9, 8:05 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: Yes - but the robot adding public would be able to be removed also, unless it created the wave. On 8 June 2010 23:53, Anders blabl...@gmail.com wrote: Oh, now I discovered this: class WaveletParticipantsChanged(Event): Event triggered when the participants on a wave change. I assume that it can be used for catching all cases when participants are removed from waves. That would be good enough. At least until more fine-grained control has been implemented which I saw is planned for the wave roadmap. On Jun 8, 10:44 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: If it helps - I'm working on a robot that you can use to create waves for you, and it will re-add anyone that was removed, unless they remove themselves. (This robot would have created the wave, so it cannot be removed). On 8 June 2010 21:00, Anders blabl...@gmail.com wrote: I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com google-wave-api%252bunsubscr...@googlegroups.comgoogle-wave-api%25252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I have written a robot that re-adds participants. It works really great! When one of the participants that gets re-added is removed by a user the robot instantly adds it back again. Within a fraction of a second. This hopefully solves the problem with keeping the waves public. An improvement would be to be able to set a filter so that my robot only gets called for those particular robots (only two at the moment) that I want to re-add. Because as it is now my robot of course gets called every time a participant is added or removed. That's a minor problem and will only become a larger problem if lots of people would use my application. -- 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-...@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.
Re: [Google Wave APIs] Re: Public waves can be made non-public by anyone
Yes - but the robot adding public would be able to be removed also, unless it created the wave. On 8 June 2010 23:53, Anders blabl...@gmail.com wrote: Oh, now I discovered this: class WaveletParticipantsChanged(Event): Event triggered when the participants on a wave change. I assume that it can be used for catching all cases when participants are removed from waves. That would be good enough. At least until more fine-grained control has been implemented which I saw is planned for the wave roadmap. On Jun 8, 10:44 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: If it helps - I'm working on a robot that you can use to create waves for you, and it will re-add anyone that was removed, unless they remove themselves. (This robot would have created the wave, so it cannot be removed). On 8 June 2010 21:00, Anders blabl...@gmail.com wrote: I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I was thinking of having one robot creating all the waves in my application, and each time a wave is created the robot adds the public participant to the wave plus one or a few robots to provide default functionality (such as support for emoticons). So when a user creates a wave in my application, it's the one robot that always is the creator of the wave. And each time a participant tries to remove the public participant or any of the default robots in a wave, then the robot who created the wave gets informed about that through WaveletParticipantsChanged() and immediately re-adds the robot that was removed from the wave. Anyone can remove all the other participants in any of the waves in my application, but since the public participant is always re-added immediately, nobody is blocked from any of the waves and I thought it would be nice to allow anyone to add or remove their own robots to the waves which would potentially provide for powerful capabilities in the waves. I haven't checked if all these things are possible in practice but that's my plan at the moment. And I don't know all the details yet. For example is it possible to catch an event and then consume it before any action has taken place? Or when a robot receives an event, then the action has already happened. On Jun 9, 8:05 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: Yes - but the robot adding public would be able to be removed also, unless it created the wave. On 8 June 2010 23:53, Anders blabl...@gmail.com wrote: Oh, now I discovered this: class WaveletParticipantsChanged(Event): Event triggered when the participants on a wave change. I assume that it can be used for catching all cases when participants are removed from waves. That would be good enough. At least until more fine-grained control has been implemented which I saw is planned for the wave roadmap. On Jun 8, 10:44 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: If it helps - I'm working on a robot that you can use to create waves for you, and it will re-add anyone that was removed, unless they remove themselves. (This robot would have created the wave, so it cannot be removed). On 8 June 2010 21:00, Anders blabl...@gmail.com wrote: I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com google-wave-api%2bunsubscr...@googlegroups.comgoogle-wave-api%252bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
One solution could perhaps be to have a robot adding the Public participant and the needed robots each time a user opens a wave in my application. I'm new to Google Wave but I read that robots can add participants (and perhaps even check if a participant is added to a wave or not). I don't know though if that extra check and adding of participants when missing would create too much of an overhead. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
I just posted a comment about that! The re-add solution might work. I think I will implement the robot myself, but it would be good to see some example code for how it can be done (I'm new to Google Wave). On Jun 8, 10:44 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: If it helps - I'm working on a robot that you can use to create waves for you, and it will re-add anyone that was removed, unless they remove themselves. (This robot would have created the wave, so it cannot be removed). On 8 June 2010 21:00, Anders blabl...@gmail.com wrote: I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Another problem is that someone could use a kind of terminator robot that automatically removes participants from my public waves. And then there would be a kind of war between my robot re-adding participants and some 'denial of service' robot frequently removing participants (such as the Public participant and robots) from my waves. So a re-adding solution would perhaps not be fully satisfying. And there is also a potential timing problem, because even human participants can remove the Public participant at any time from my waves and my robot would not be able to fully protect against some users suddenly not being able to use the waves because they no longer are public. I would like to have the option to mark some participants, such as the Public participant and robots as being permanent to the waves, i.e. they can not be removed by anyone else than the participant who created the waves. It's a strange kind of logic to have a public wave that anyone suddenly can make non-public. -- 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-...@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.
[Google Wave APIs] Re: Public waves can be made non-public by anyone
Oh, now I discovered this: class WaveletParticipantsChanged(Event): Event triggered when the participants on a wave change. I assume that it can be used for catching all cases when participants are removed from waves. That would be good enough. At least until more fine-grained control has been implemented which I saw is planned for the wave roadmap. On Jun 8, 10:44 pm, Nathanael Abbotts nat.abbo...@googlemail.com wrote: If it helps - I'm working on a robot that you can use to create waves for you, and it will re-add anyone that was removed, unless they remove themselves. (This robot would have created the wave, so it cannot be removed). On 8 June 2010 21:00, Anders blabl...@gmail.com wrote: I have started developing a wave application with public waves. One problem is that the Public participant pub...@a.gwave.com can be removed by anyone, and then the wave is no longer public! Not good. Another problem is that anyone can remove robots from a public wave, which also is a problem. I would like to have the waves public when it comes to writing to the wave, but not public when it comes to removing participants, such as the Public participant and robots. -- 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-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.comgoogle-wave-api%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en. -- 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-...@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.
[Google Wave APIs] Re: Public waves?
Yes - the same way as on the old system - on the bottom left corner there is a + sign at the contact box - click that one and enter the email pub...@a.gwave.com and hit return. First this didn't work for me - the add button still greyed out. But with a second attempt finally worked. cheers david On Fri, Oct 2, 2009 at 3:43 PM, Joshua L. Davis simplehu...@gmail.comwrote: Has anyone found a way to create public waves in the preview not the dev preview? -Josh On Oct 2, 2:07 am, Sam Osborne sam.tosbo...@googlemail.com wrote: Try searching for with:public -with:bloggy. That searches for any public wave, that don't have bloggy as a participant too, as everything with bloggy as a participant are made public by default, though you can remove this if you so want to. 2009/10/2 Silicon Dragon sdr...@gmail.com Yes, I do have an active account for wave.google.com (I've had one for sandbox, and got auto-invited there). However, unlike in the sandbox, public waves aren't appearing in my inbox (which I consider a big improvement! less clutter). By the current configuration, however, I see no ways to seek out topics, or channels of waves (similiar to what newsgroups are to e-mail) to which I can subscribe. The with:public seems to be a bit too much cluttered. There seems to be a bot called groupy-the-bot; however, the latest available sources http://code.google.com/p/groupy-the-bot/source/browse/point to the 23rd of Jun (massively outdated). Anyone knows of any other existing solution? On Fri, Oct 2, 2009 at 12:46 AM, Graham Anderson graham.ander...@gmail.com wrote: On Friday 02 October 2009 01:08:40 Silicon Dragon wrote: Hey, Anyone knows how to subscribe to public waves, or what other streams could be reached out-of-the-box from the new wave server https://wave.google.com/ As far as things go right now, i believe you need to be logged into the wave preview session to be able to view public waves. This means you'll need an activated account for wave.google.com . -- “Experience is the name everyone gives to their mistakes.” ☘ Oscar Wilde --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Public waves?
It has not worked for me and adding pub...@a.gwave.com has been unsuccessful. Cheers! Date: Fri, 2 Oct 2009 03:13:02 -0700 Subject: [Google Wave APIs] Re: Public waves? From: simplehu...@gmail.com To: google-wave-api@googlegroups.com Has anyone found a way to create public waves in the preview not the dev preview? -Josh On Oct 2, 2:07 am, Sam Osborne sam.tosbo...@googlemail.com wrote: Try searching for with:public -with:bloggy. That searches for any public wave, that don't have bloggy as a participant too, as everything with bloggy as a participant are made public by default, though you can remove this if you so want to. 2009/10/2 Silicon Dragon sdr...@gmail.com Yes, I do have an active account for wave.google.com (I've had one for sandbox, and got auto-invited there). However, unlike in the sandbox, public waves aren't appearing in my inbox (which I consider a big improvement! less clutter). By the current configuration, however, I see no ways to seek out topics, or channels of waves (similiar to what newsgroups are to e-mail) to which I can subscribe. The with:public seems to be a bit too much cluttered. There seems to be a bot called groupy-the-bot; however, the latest available sources http://code.google.com/p/groupy-the-bot/source/browse/point to the 23rd of Jun (massively outdated). Anyone knows of any other existing solution? On Fri, Oct 2, 2009 at 12:46 AM, Graham Anderson graham.ander...@gmail.com wrote: On Friday 02 October 2009 01:08:40 Silicon Dragon wrote: Hey, Anyone knows how to subscribe to public waves, or what other streams could be reached out-of-the-box from the new wave server https://wave.google.com/ As far as things go right now, i believe you need to be logged into the wave preview session to be able to view public waves. This means you'll need an activated account for wave.google.com . -- “Experience is the name everyone gives to their mistakes.” ☘ Oscar Wilde _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Google Wave APIs] Re: Public waves?
On Mon, Oct 05, 2009 at 07:06:12AM -0700, Wooble wrote: public will vanish from your contacts list at random, too, ... Why does this happen? -- Brian May br...@microcomaustralia.com.au --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
