Well aren't private reply blips sent on a brand new wavelet? It would
seem that a robot would simply need to send a private blip with the
poker hand to each player and then use a community blip for betting,
etc. Are there currently API restrictions for private blips(I haven't
needed the function
Anything sent via state changes to the wave is visible to everyone. You
could do either of the following:
1. Use a gadget that communicates directly with your app to discuss the
"sensitive" aspects of your gadget/app (which cards the user was given), and
the server-side app would then be the excl
The case I was thinking about in my previous post was for robots,
Gadegets may actually be able to sandbox themselves enough, you would
need to have your own server that managed all the state, in which case
Wave isn't really doing much for you...
On Oct 24, 1:49 pm, Wilfried wrote:
> I understan
It's probably possible, but I wouldn't say it's secure.
As far as I know, all the state is sent on a changed event, someone
could just write a robot to watch everything that was happening.
On Oct 24, 1:49 pm, Wilfried wrote:
> I understand that the approach of Google Wave is to collaborate on t
