On Tue, Oct 6, 2009 at 1:43 PM, Brian May <[email protected]>wrote:
> > Ok, good. I just wanted to make sure I was answering the right question > ;-). > > Having a seperate domain for googlewave.com means in the future they could > do > something fancy like have mail sent to [email protected] > appear in a wave, maybe one that has [email protected] 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 > [email protected]). > > Maybe this is the reason the chose to use two seperate domains? > Maybe. Personally I would prefer it to either work for all gmail.com mail automatically, or work as a filter in Gmail (a magic label where everything added to it becomes a wave would be awesome.) Either option seems better than having two domains for the same person. When Wave goes to apps, after all, it's going to be the same domain for the wave, mail and IM accounts over there. When I considered that, it seemed like having a different address just for wave was a bit lop-sided. After all, cool apps forwarding email to IM are already possible, but our IM addresses are still @gmail.com. TX --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
