contains confidential information that cannot
be released, which in turn may kill the community efforts.
--
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
make things so much better.
Finally some good news!
--
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-...@googlegroups.com.
To unsubscribe from
On 10 February 2010 19:05, Trejkaz trej...@gmail.com wrote:
That's what I answered too. Privacy is another (although highly
related) matter.
Ooops, sorry, my bad. Looks like I am asleep at the keyboard...
--
Brian May br...@microcomaustralia.com.au
--
You received this message because you
proves to be more
popular then expected. At the moment my understanding is that the
hosting server has a high workload for every client connected, and it
isn't possible to offload this workload to another more capable
server.
--
Brian May br...@microcomaustralia.com.au
--
You received this message
to show the wave to her room mate and nobody need ever
know.
--
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-...@googlegroups.com.
To unsubscribe from
with email.
--
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-...@googlegroups.com.
To unsubscribe from this group, send email to
google-wave-api
On Thu, Oct 22, 2009 at 11:50:30AM -0700, Carlos3188 wrote:
I thought the sandbox ended when the limited preview was launched but
No, the sandbox is still around.
--
Brian May br...@microcomaustralia.com.au
--~--~-~--~~~---~--~~
You received this message
, it
is possible somebody has changed the title.
--
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
buggy. For example, somebody I sent an
invitation to, I can see her name picture after I reload Google Wave for
about 30 seconds, then both the name and picture vanish. If I reload the page I
can see them again for another 30 seconds (approx).
--
Brian May br...@microcomaustralia.com.au
--
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
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
properly before upgrading the main
server.
--
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
solve the entire security problem.
A potential problem with Wave, at the moment, is that users could be tricked
into thinking that a spammer is their friend if the spammer sets their user
name and icon to match. A difficult problem, I can't think of a good solution
here.
--
Brian May br
On Tue, Oct 06, 2009 at 10:03:57AM +1100, Brian May wrote:
On Sun, Oct 04, 2009 at 09:38:49AM -0700, jz light wrote:
I would like to try out wave and start a open source project to
replace outlook.
Looked at Evolution, Firefox, Zimbra, etc?
Errr, I didn't type that. I blame... Errr
that has usern...@googlewave.com as the only
(default) participant.
Meanwhile gmail would continue to work as before (or if you really want you
might be able to have that automatically forward to usern...@googlewave.com).
Maybe this is the reason the chose to use two seperate domains?
--
Brian May
, the URL is not a good substitute for the old debug menu :-(
--
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
://services.google.com/fb/forms/wavesignup/
--
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
mode).
It does not appear possible to edit or delete a blip that has no text in in. The
delete menu is greyed out and the edit option does nothing.
Right now this wave is crashing a lot, especially if I try to delete a blip
containing text; experimentation continues...
--
Brian May br
/meetingtime.html?month=9day=15year=2009p1=152p2=127p3=-1p4=-1
From this I see the downtime as
14th 22:00 - 15th 06:00 Las Vegas
15th 05:00 - 15th 13:00 UTC
15th 15:00 - 15th 23:00 Melbourne
So I guess that means the changes haven't yet occurred. Assuming I got the date
correct.
--
Brian May br
/meetingtime.html?month=9day=7year=2009p1=137p2=152p3=-1p4=-1
--
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
20 matches
Mail list logo
