Wave And Gmail Account
9 views
Skip to first unread message
Diego Sarmentero
May 30, 2009, 12:05:46 PM5/30/09
to Google Wave API
Hi! I saw the presentation and i think that Wave is awesome!
The idea of think how it would be if the email had been created today
is brilliant!
But i have one doubt...
We are all asking for a Wave account now, but in the future, when Wave
will be released, Are we going to be able to join Wave with our Gmail
Account and mantain all of the e-mails that we have or we are going to
start with an empty account??
We can enabled POP to send the mails from one account to the new
one... but the process to migrate all the Google Services (as Code,
Calendar, Blogger, Picasa, etc) that we use required a lot of time...
That was my only doubt... maybe the answer is simple: "you can use
your Gmail account into Wave", but i didnt know...
Thanks!
Bye!
The idea of think how it would be if the email had been created today
is brilliant!
But i have one doubt...
We are all asking for a Wave account now, but in the future, when Wave
will be released, Are we going to be able to join Wave with our Gmail
Account and mantain all of the e-mails that we have or we are going to
start with an empty account??
We can enabled POP to send the mails from one account to the new
one... but the process to migrate all the Google Services (as Code,
Calendar, Blogger, Picasa, etc) that we use required a lot of time...
That was my only doubt... maybe the answer is simple: "you can use
your Gmail account into Wave", but i didnt know...
Thanks!
Bye!
Austin Chau
May 30, 2009, 2:22:51 PM5/30/09
to google-...@googlegroups.com
Hi Diego,
Thank you for your support for Wave!
What we've shown you is an early developer release, and we're still exploring how to extend and integrate with other services. So please stay tuned and continue to help us to improve Wave :)
Austin
Thank you for your support for Wave!
What we've shown you is an early developer release, and we're still exploring how to extend and integrate with other services. So please stay tuned and continue to help us to improve Wave :)
Austin
Nick
May 30, 2009, 4:24:53 PM5/30/09
to Google Wave API
It also seems than adapting Gmail to use/accept/convert old
'classical' conversations into waves will help with a general
transition to waves and away from email. Email seemed more like a toy
than anything else 20 years ago because so few people used it. You
could only use it to communicate with a small number of people and it
was a novelty each time. It was only after we reached a point when
enough people had access to it that it became a common place and truly
convenient. With so many people on Gmail it seems possible to reach
that tipping point much more quickly by giving them access to it
without their need to actively go and get it. Thereby incouraging
other email/internet/browser clients to incorporate it.
Nick
'classical' conversations into waves will help with a general
transition to waves and away from email. Email seemed more like a toy
than anything else 20 years ago because so few people used it. You
could only use it to communicate with a small number of people and it
was a novelty each time. It was only after we reached a point when
enough people had access to it that it became a common place and truly
convenient. With so many people on Gmail it seems possible to reach
that tipping point much more quickly by giving them access to it
without their need to actively go and get it. Thereby incouraging
other email/internet/browser clients to incorporate it.
Nick
Bastian Hoyer
May 30, 2009, 5:52:56 PM5/30/09
to Google Wave API
I don't think that it's possible to convert classical emails into
working waves. Many peoples email address won't be their wave adress..
it would be possible for you to use wave as your email client.. but if
you get an mail into wave and reply you would still send an email
back... and none of the cool wave functions would work... And you
would get all that email spam into wave... I don't want that. If wave
is that cool people will use it without the need to mix it with email.
I know gmail has many users.. but most companies I know use exchange/
blackberry and I don't think that will change in the near future.
working waves. Many peoples email address won't be their wave adress..
it would be possible for you to use wave as your email client.. but if
you get an mail into wave and reply you would still send an email
back... and none of the cool wave functions would work... And you
would get all that email spam into wave... I don't want that. If wave
is that cool people will use it without the need to mix it with email.
I know gmail has many users.. but most companies I know use exchange/
blackberry and I don't think that will change in the near future.
Scot Mcphee
May 30, 2009, 6:12:11 PM5/30/09
to google-...@googlegroups.com
I disagree with that. So much of my life in is email, specifically,
gmail. I either put it in my iphone's calendar right then and there,
or you send me an email (and I put the item into iCal.app if it's
related to a date or appt), or I send you an email, or it doesn't
exist past the next 20 seconds. Having all of that stuff in Wave would
be tremendously useful to me, I think. So much business decision
making is done via email, for example, I'm never in the office.
Bob Oliver Bigellow XLII
May 30, 2009, 7:18:14 PM5/30/09
to Google Wave API
My plan, as a developer, would be to do something along these lines:
Implement a robot which will send formatted emails to members of a
wave who do not have access to waves. In other words, to have the
ability to associate a non-wave/email-only contact to a wave. Once
this is done, the robot sends out emails to those contacts
periodically (perhaps when a full reply is posted to the wave,
etc...) Within this email will also be a link inviting the user to
join the wave (instead of dealing only with email updates.)
Furthermore, if that user replies to their email, the robot will
somehow take that reply and insert the contents back into the wave in
an appropriate fashion.
This will help to create a bridge between email systems and wave
systems. Hopefully, the email users will see the folly of their ways
and will eventually join the wave wagon. For those that don't,
they'll just continue to get email updates. I wonder, though, if this
is something that Google has already taken into consideration and will
already have some functionality like this out of the gates.
Implement a robot which will send formatted emails to members of a
wave who do not have access to waves. In other words, to have the
ability to associate a non-wave/email-only contact to a wave. Once
this is done, the robot sends out emails to those contacts
periodically (perhaps when a full reply is posted to the wave,
etc...) Within this email will also be a link inviting the user to
join the wave (instead of dealing only with email updates.)
Furthermore, if that user replies to their email, the robot will
somehow take that reply and insert the contents back into the wave in
an appropriate fashion.
This will help to create a bridge between email systems and wave
systems. Hopefully, the email users will see the folly of their ways
and will eventually join the wave wagon. For those that don't,
they'll just continue to get email updates. I wonder, though, if this
is something that Google has already taken into consideration and will
already have some functionality like this out of the gates.
SCIBOTIC
May 30, 2009, 7:22:52 PM5/30/09
to Google Wave API
Don't forget that you can write robots to interact with waves, you
could just write a bot to designate a folder for email, feed incoming
messages from your pop account as new waves and watch for any new
replies or waves the user creates as a new message to send via. smtp.
The only thing you'd need to do is maintain and parse "subject",
"from" and "to" fields in the waves created.
It'd probably be rather simple to get basic functionality going,
although ideally you'd have to add extra logic for filtering, extra
folders and other features our email clients have spoiled us with.
could just write a bot to designate a folder for email, feed incoming
messages from your pop account as new waves and watch for any new
replies or waves the user creates as a new message to send via. smtp.
The only thing you'd need to do is maintain and parse "subject",
"from" and "to" fields in the waves created.
It'd probably be rather simple to get basic functionality going,
although ideally you'd have to add extra logic for filtering, extra
folders and other features our email clients have spoiled us with.
Bastian Hoyer
May 30, 2009, 7:24:20 PM5/30/09
to Google Wave API
I don't think that will work well. If you use wave features like
changing text, splitting up other posts and writing replys within the
document, answer to those replys, start private wavelets, thats all
stuff you can't put into an email.
Another thing you have to consider is that participating a wave is not
the same as getting an email ... if you get kicked out of the wave you
also loose access to the whole thread... That's probably bad in some
situations ;)
changing text, splitting up other posts and writing replys within the
document, answer to those replys, start private wavelets, thats all
stuff you can't put into an email.
Another thing you have to consider is that participating a wave is not
the same as getting an email ... if you get kicked out of the wave you
also loose access to the whole thread... That's probably bad in some
situations ;)
SCIBOTIC
May 30, 2009, 7:26:01 PM5/30/09
to Google Wave API
On May 31, 9:24 am, Bastian Hoyer <daf...@gmail.com> wrote:
> I don't think that will work well. If you use wave features like
> changing text, splitting up other posts and writing replys within the
> document, answer to those replys, start private wavelets, thats all
> stuff you can't put into an email.
I have reasons to think otherwise. There would have to be compromised
> I don't think that will work well. If you use wave features like
> changing text, splitting up other posts and writing replys within the
> document, answer to those replys, start private wavelets, thats all
> stuff you can't put into an email.
but the basic functionality will be there.
On May 31, 9:24 am, Bastian Hoyer <daf...@gmail.com>
Bob Oliver Bigellow XLII
May 30, 2009, 7:54:23 PM5/30/09
to Google Wave API
Keep in mind that forming an integration between email and Waves is
not necessarily meant to keep email around forever, or give no
incentive for someone to switch to Waves. It would just be something
to bridge the gap.
So, let's say you have a complicated Wave with posts inserted inline,
replies, answers to replies, etc, etc... a bot would only need to
determine the overall content of the wave (perhaps the equivalent of
an HTML export of the wave data)... then send this to the non-wave-
user's email address. It would then have a reminder that they would
be much better off signing up for a Wave account somewhere but, if
they still insist on having an analog TV... erm, I mean a VCR... erm,
I mean sticking with email and forgoing all of the features of Waves,
then all they can do is REPLY... and their reply is dumped into the
end of the wave in a very messy fashion. Or else, the bot can
determine which revision the wave was at when the email was sent to
them that they are replying to, then insert their reply at the
appropriate level.
Side private conversations are a non-issue, as the only thing which
would be emailed to that user would be the information that only that
user should have access to. Their reply would be at the level of the
full Wave, for all of those users to see. If someone starts a wavelet
that includes the email-only user, it could send them an email with
that side-discussion... then replies would be inserted back into that
wavelet, keeping the discussion private to those within that wavelet.
Nobody is saying it would be easy... or that it wouldn't be ugly at
times... or that it wouldn't have its drawbacks... but it would bridge
the gap, and would encourage email-only people to make the switch when
they see what they're missing out on.
It's no different than when you use Google Docs to create a form. One
of the options is to email the form to someone while embedding the
form (survey) itself within the email. This is great for some email
clients... but most email clients just render the form in plain text.
Certainly, it's mostly useless. But it at least gives the email user
a way to preview what the survey is all about, letting them decide
whether or not to click on the link which will take them to the HTML
form to fill out. The Wave to Email integration could be similar.
Keep the email-only user "in the loop"... but always provide a link
that, when clicked on, will take them directly to that Wave within a
web-based Wave dashboard... whether it be Google's or someone else's.
not necessarily meant to keep email around forever, or give no
incentive for someone to switch to Waves. It would just be something
to bridge the gap.
So, let's say you have a complicated Wave with posts inserted inline,
replies, answers to replies, etc, etc... a bot would only need to
determine the overall content of the wave (perhaps the equivalent of
an HTML export of the wave data)... then send this to the non-wave-
user's email address. It would then have a reminder that they would
be much better off signing up for a Wave account somewhere but, if
they still insist on having an analog TV... erm, I mean a VCR... erm,
I mean sticking with email and forgoing all of the features of Waves,
then all they can do is REPLY... and their reply is dumped into the
end of the wave in a very messy fashion. Or else, the bot can
determine which revision the wave was at when the email was sent to
them that they are replying to, then insert their reply at the
appropriate level.
Side private conversations are a non-issue, as the only thing which
would be emailed to that user would be the information that only that
user should have access to. Their reply would be at the level of the
full Wave, for all of those users to see. If someone starts a wavelet
that includes the email-only user, it could send them an email with
that side-discussion... then replies would be inserted back into that
wavelet, keeping the discussion private to those within that wavelet.
Nobody is saying it would be easy... or that it wouldn't be ugly at
times... or that it wouldn't have its drawbacks... but it would bridge
the gap, and would encourage email-only people to make the switch when
they see what they're missing out on.
It's no different than when you use Google Docs to create a form. One
of the options is to email the form to someone while embedding the
form (survey) itself within the email. This is great for some email
clients... but most email clients just render the form in plain text.
Certainly, it's mostly useless. But it at least gives the email user
a way to preview what the survey is all about, letting them decide
whether or not to click on the link which will take them to the HTML
form to fill out. The Wave to Email integration could be similar.
Keep the email-only user "in the loop"... but always provide a link
that, when clicked on, will take them directly to that Wave within a
web-based Wave dashboard... whether it be Google's or someone else's.
Bastian Hoyer
May 30, 2009, 7:57:13 PM5/30/09
to Google Wave API
Well.. my point is that I think wave won't replace email completly. I
can remember the time before there where IM when I wrote many short
emails to friends and co workers. Then we got icq and suddenly there
were a better choice for many messages. I think wave might have the
same impact as im had... and it probably can completely replace other
IM services, but I think in the future I still will decide if I write
a mail or start a wave. Many Situations where I'd use Mail now will
work better with a wave but there will still be Situations where I'd
use mail, e.g. for things like newsletters, password reminders, status
mails from the raid controller or other situations where I'd not
expect feedback.
This thread was about converting or changing gmail into waves to get
(force?) more people to use it to get it faster accepted, but I don't
think thats necessary... I think it's more important that there will
be other big companies providing wave accounts and integrating it into
many products then the users will come from themselfes
(Written with android form so please ignore typos)
can remember the time before there where IM when I wrote many short
emails to friends and co workers. Then we got icq and suddenly there
were a better choice for many messages. I think wave might have the
same impact as im had... and it probably can completely replace other
IM services, but I think in the future I still will decide if I write
a mail or start a wave. Many Situations where I'd use Mail now will
work better with a wave but there will still be Situations where I'd
use mail, e.g. for things like newsletters, password reminders, status
mails from the raid controller or other situations where I'd not
expect feedback.
This thread was about converting or changing gmail into waves to get
(force?) more people to use it to get it faster accepted, but I don't
think thats necessary... I think it's more important that there will
be other big companies providing wave accounts and integrating it into
many products then the users will come from themselfes
(Written with android form so please ignore typos)
Diego Sarmentero
May 30, 2009, 8:32:58 PM5/30/09
to google-...@googlegroups.com
I found really interesting so many things that were discussed here, but what i meant to say when i started talking about: "wave and gmail account" is that we have a username to log into a google account and use services as blogger, picasa, google code, etc. But now appear Wave and i personally think that is a great step for communication and the capability to integrate all the different services in one place like we saw in the demostration when they use the Robots for Blogger or Twitter or anything you want to create is something that it was really necessary today, but my doubt was about all the existing services and emails that i already have.
It would be great to be able to migrate (or integrate) your gmail account to Wave, otherwise, the problem persist, you will have to check constantly your Wave account and your older Google account to use the same services but associated to different profiles.
All the emails and different things that everyone does in google services means Data that a person want to mantein while they are able to use new technologies or tools like Wave.
--
Desgraciadamente Nuestra Tecnología Ha Superado Nuestra Humanidad.
-Albert Einstein-
It would be great to be able to migrate (or integrate) your gmail account to Wave, otherwise, the problem persist, you will have to check constantly your Wave account and your older Google account to use the same services but associated to different profiles.
All the emails and different things that everyone does in google services means Data that a person want to mantein while they are able to use new technologies or tools like Wave.
--
Desgraciadamente Nuestra Tecnología Ha Superado Nuestra Humanidad.
-Albert Einstein-
Bob Oliver Bigellow XLII
May 30, 2009, 11:02:37 PM5/30/09
to Google Wave API
I'm sure that, knowing Google, there will be a way to use your one
"Google Account" (read: Gmail account) as your Wave account. I just
expect this to always be the case.
On May 30, 5:32 pm, Diego Sarmentero <diego.sarment...@gmail.com>
wrote:
"Google Account" (read: Gmail account) as your Wave account. I just
expect this to always be the case.
On May 30, 5:32 pm, Diego Sarmentero <diego.sarment...@gmail.com>
wrote:
sirdarkstar
May 31, 2009, 12:02:13 AM5/31/09
to Google Wave API
I see no reason that either Google (or possibly even an enterprising
developer) could not write a gmail/wave gateway. If you can gateway
with twitter and blogger and !bug tracking systems! surely you can
gateway with an email system since the degenerate use-case of Wave is
email-like interactions. Your gmail contact list could even get
imported as an external user list into Wave (like how they showed this
working for twitter users).
In fact, without features like this I suspect Wave will languish for
a long time. But imagine if I could login to Wave and read my hotmail
account, and my yahoo account, and my gmail account AND my work
account, and IM on ICQ+AIM +YIM+Jabber, and twitter and blog and RSS
feeds and.... all from one integrated interface (/geekgasm). It
would be almost a no-brainer to use, and once all your friends are
using it, you no longer need that hotmail account, or yahoo account,
or IM account (at least not nearly as much) because you would be
"riding the wave" directly with all those friends using a much richer
feature set than any of those "legacy" systems.
It won't happen overnight of course. email has been around for 40
years for a reason. But if they can gateway to the major info-
streams as smoothly as it looks like they might be able to then I
think this is a no-brainer for hitting one out of the park (assuming
they truly do open-source it like the email protocols were).
My two fears are #1 that they will not fully open-source it, and #2
that M$ will find a way to hose-it-up so that we end up with two wavy
universes that are out of phase (kind of like outlook email formats, M
$-proprietary HTML, M$ Java, M$ TCP/IP, and every single thing else
they have ever touched).
developer) could not write a gmail/wave gateway. If you can gateway
with twitter and blogger and !bug tracking systems! surely you can
gateway with an email system since the degenerate use-case of Wave is
email-like interactions. Your gmail contact list could even get
imported as an external user list into Wave (like how they showed this
working for twitter users).
In fact, without features like this I suspect Wave will languish for
a long time. But imagine if I could login to Wave and read my hotmail
account, and my yahoo account, and my gmail account AND my work
account, and IM on ICQ+AIM +YIM+Jabber, and twitter and blog and RSS
feeds and.... all from one integrated interface (/geekgasm). It
would be almost a no-brainer to use, and once all your friends are
using it, you no longer need that hotmail account, or yahoo account,
or IM account (at least not nearly as much) because you would be
"riding the wave" directly with all those friends using a much richer
feature set than any of those "legacy" systems.
It won't happen overnight of course. email has been around for 40
years for a reason. But if they can gateway to the major info-
streams as smoothly as it looks like they might be able to then I
think this is a no-brainer for hitting one out of the park (assuming
they truly do open-source it like the email protocols were).
My two fears are #1 that they will not fully open-source it, and #2
that M$ will find a way to hose-it-up so that we end up with two wavy
universes that are out of phase (kind of like outlook email formats, M
$-proprietary HTML, M$ Java, M$ TCP/IP, and every single thing else
they have ever touched).
Bastian Hoyer
May 31, 2009, 4:19:29 AM5/31/09
to Google Wave API
I just wanted to make clear that I agree that wave should get
integrated into the google account and it probably will and i think
that i read in the q&a session that it also will use google contacts.
I just think that it just should not try to replace the google mail
interface :)
I guess microsoft and others could try to create their oen wave system
perhaps based on msn but i don't think they will get something ready
fast enough. At least when their is a working server that is usable
and hostable in companie networks the race would be over.
It still could happen the exchange and outlook support wave and use
their own extensions but i think thats unlikely
integrated into the google account and it probably will and i think
that i read in the q&a session that it also will use google contacts.
I just think that it just should not try to replace the google mail
interface :)
I guess microsoft and others could try to create their oen wave system
perhaps based on msn but i don't think they will get something ready
fast enough. At least when their is a working server that is usable
and hostable in companie networks the race would be over.
It still could happen the exchange and outlook support wave and use
their own extensions but i think thats unlikely
Leonard Badi
May 31, 2009, 5:05:13 AM5/31/09
to google-...@googlegroups.com
You are right about what most companies use. I am thinking about having a container (database) in which all your legacy(
) email accounts data, waves and legacy IMs can all be saved. Then, write a robot that will convert a specific email message or chat into wavelet if you want your wave participants to take part into that discussion. You can reply from Wave and the robot would convert that specific wavelet back into legacy email and send it back to the originator as normal email or even forward it to other new mail accounts holders. If you don't want the originator to see the thread from Wave with all participants contributions, just prevent him to see it, otherwise, the robot will expand the history of that thread with the reply on top and send it to the originator. In that way, you can build a sort of bridge between legacy apps and Wave. I am thinking of building a desktop wave server and client for that purpose. As a matter of fact, I have got something that can be easily tweaked to that purpose. Any comment?
) email accounts data, waves and legacy IMs can all be saved. Then, write a robot that will convert a specific email message or chat into wavelet if you want your wave participants to take part into that discussion. You can reply from Wave and the robot would convert that specific wavelet back into legacy email and send it back to the originator as normal email or even forward it to other new mail accounts holders. If you don't want the originator to see the thread from Wave with all participants contributions, just prevent him to see it, otherwise, the robot will expand the history of that thread with the reply on top and send it to the originator. In that way, you can build a sort of bridge between legacy apps and Wave. I am thinking of building a desktop wave server and client for that purpose. As a matter of fact, I have got something that can be easily tweaked to that purpose. Any comment?Leonard Badi
May 31, 2009, 5:13:01 AM5/31/09
to google-...@googlegroups.com
Yes, it is bad to loose the whole thread when you get kicked of the wave. How about a client with the ability to save a copy of every wavelet you are involved in and that you deem important to you. Just a back up anyway?
Scot Mcphee
May 31, 2009, 7:11:14 AM5/31/09
to google-...@googlegroups.com
On 31/05/2009, at 09:57 , Bastian Hoyer wrote:
>
> mails from the raid controller or other situations where I'd not
> expect feedback.
you could write a bot that tracked the data centre's uptime by putting
machine status and other sorts of computer and network monitoring into
waves.
scot
marstein
May 31, 2009, 5:27:52 PM5/31/09
to Google Wave API
I think sirdarkstar hits it on the head. There will be a robot that
connects to your email system(s) and imports threads. In your replies
from the wave you can then invite email recipients onto the wave.
One could probably also write a robot, that sucks a wave into offline
storage for backup purposes. When you get kicked off the wave later
you still have the saved backup.
connects to your email system(s) and imports threads. In your replies
from the wave you can then invite email recipients onto the wave.
One could probably also write a robot, that sucks a wave into offline
storage for backup purposes. When you get kicked off the wave later
you still have the saved backup.
Jorge Vargas
May 31, 2009, 6:12:26 PM5/31/09
to google-...@googlegroups.com
I'm sorry to say this but if you agree this is needed, you totally
missed the point of the wave idea.
missed the point of the wave idea.
jimmeh
May 31, 2009, 7:26:24 PM5/31/09
to Google Wave API
Excellent idea, id love to see it implemented, i definately agree
something like this needs to be created to start moving email users
over. Lets hope the genpop / non-techies pick up Wave like the techies
no doubt will. I think the hardest task is educating the non-tech's
into the possibilities, as devs we can all see whats possible, and how
revolutionary this could be.
On May 31, 12:18 am, Bob Oliver Bigellow XLII <iam...@gmail.com>
wrote:
something like this needs to be created to start moving email users
over. Lets hope the genpop / non-techies pick up Wave like the techies
no doubt will. I think the hardest task is educating the non-tech's
into the possibilities, as devs we can all see whats possible, and how
revolutionary this could be.
On May 31, 12:18 am, Bob Oliver Bigellow XLII <iam...@gmail.com>
wrote:
Dave Todd
May 31, 2009, 8:16:49 PM5/31/09
to Google Wave API
Hi Austin,
What I, and probably many people are worried about, is whether we will
be able to maintain out user names, which we have had for a long time,
or will we have to get new ones? I was a early adopter of gmail and as
such have a email address that doesn't have any numbers behind it. I
would prefer to keep it that way when using the wave system. Do you
think we will be allowed to log in to wave with our current gmail
account info?
Thanks and take care,
Dave
On May 30, 11:22 am, Austin Chau <austin.c...@gmail.com> wrote:
> Hi Diego,
>
> Thank you for your support for Wave!
>
> What we've shown you is an early developer release, and we're still
> exploring how to extend and integrate with other services. So please stay
> tuned and continue to help us to improve Wave :)
>
> Austin
>
> On Sat, May 30, 2009 at 9:05 AM, Diego Sarmentero <
>
What I, and probably many people are worried about, is whether we will
be able to maintain out user names, which we have had for a long time,
or will we have to get new ones? I was a early adopter of gmail and as
such have a email address that doesn't have any numbers behind it. I
would prefer to keep it that way when using the wave system. Do you
think we will be allowed to log in to wave with our current gmail
account info?
Thanks and take care,
Dave
On May 30, 11:22 am, Austin Chau <austin.c...@gmail.com> wrote:
> Hi Diego,
>
> Thank you for your support for Wave!
>
> What we've shown you is an early developer release, and we're still
> exploring how to extend and integrate with other services. So please stay
> tuned and continue to help us to improve Wave :)
>
> Austin
>
> On Sat, May 30, 2009 at 9:05 AM, Diego Sarmentero <
>
Jorge Vargas
May 31, 2009, 9:09:27 PM5/31/09
to google-...@googlegroups.com
On Sun, May 31, 2009 at 8:16 PM, Dave Todd <dave...@gmail.com> wrote:
>
> Hi Austin,
>
> What I, and probably many people are worried about, is whether we will
> be able to maintain out user names, which we have had for a long time,
> or will we have to get new ones? I was a early adopter of gmail and as
> such have a email address that doesn't have any numbers behind it. I
> would prefer to keep it that way when using the wave system. Do you
> think we will be allowed to log in to wave with our current gmail
> account info?
The fact that you are here means you are an early adopter, I don't
>
> Hi Austin,
>
> What I, and probably many people are worried about, is whether we will
> be able to maintain out user names, which we have had for a long time,
> or will we have to get new ones? I was a early adopter of gmail and as
> such have a email address that doesn't have any numbers behind it. I
> would prefer to keep it that way when using the wave system. Do you
> think we will be allowed to log in to wave with our current gmail
> account info?
think they are many dave todd's around the world. you should be worry
if your name is more generic :)
On a lighter note you keep talking about wave being a google thing
with google accounts it's not going to be google only. You should
start worrying about your domain name or your iname instead. Those are
the identity's of the future on the web.
Damian Guppy
Jun 1, 2009, 12:23:48 AM6/1/09
to google-...@googlegroups.com
the login page for the sandbox gives a hint that it will be tied into your google account, so i would assume the username would stay the same.
Chris122380
Jun 2, 2009, 12:31:13 PM6/2/09
to Google Wave API
gmail is already alot like wave. Remember the beginning of the keynote
address talked about gmail using conversations or what normal e-mail
calls replies. You would just use replies as a new comment to a wave.
For a e-mail user it would be a reply to a e-mail. A comment in the
center of a e-mail would just be a new e-mail with a comment in the
center. Non wave users wouldn't be able to edit or share wave content
at the same time as wave users can. Thats when a invite e-mail for
wave would be sent to the regaler e-mail user.
I am not currently using wave as they have not yet made it public. I
would like it if Google would replace gmail with wave or add it as a
gmail labs app so when logging into gmail it would be wave, or they
could have it as a separate app like docs with access to your gmail
contacts. Remember Google contacts has recently been broken off of
gmail http://www.google.com/contacts.
address talked about gmail using conversations or what normal e-mail
calls replies. You would just use replies as a new comment to a wave.
For a e-mail user it would be a reply to a e-mail. A comment in the
center of a e-mail would just be a new e-mail with a comment in the
center. Non wave users wouldn't be able to edit or share wave content
at the same time as wave users can. Thats when a invite e-mail for
wave would be sent to the regaler e-mail user.
I am not currently using wave as they have not yet made it public. I
would like it if Google would replace gmail with wave or add it as a
gmail labs app so when logging into gmail it would be wave, or they
could have it as a separate app like docs with access to your gmail
contacts. Remember Google contacts has recently been broken off of
gmail http://www.google.com/contacts.
Dima
Jun 2, 2009, 2:01:11 PM6/2/09
to Google Wave API
>Many Situations where I'd use Mail now will
>work better with a wave but there will still be Situations where I'd
>use mail, e.g. for things like newsletters, password reminders, status
>mails from the raid controller or other situations where I'd not
>expect feedback.
Not sure why would you use email for newsletters or reminder via
>work better with a wave but there will still be Situations where I'd
>use mail, e.g. for things like newsletters, password reminders, status
>mails from the raid controller or other situations where I'd not
>expect feedback.
email? Wave is perfect for this. IMHO Wave has good potential to
replace email 100% - main risk is adoption by non-Google friendly
companies and how corporate will accept this. From what I could gather
- corporate will want to take good look at Wave. It gives so much
advantage - security, better record retention, cost savings, better
functionality.
IN my view, Wave is more generic communication tool covering all
existing methods plus more. I just can't find a scenario when I'd
rather use IM or email, having Wave and having all my contacts in Wave
(which is yes - a problem at this point).
Vidar Hokstad
Jun 3, 2009, 5:29:13 AM6/3/09
to Google Wave API
On May 31, 12:24 am, Bastian Hoyer <daf...@gmail.com> wrote:
> I don't think that will work well. If you use wave features like
> changing text, splitting up other posts and writing replys within the
> document, answer to those replys, start private wavelets, thats all
> stuff you can't put into an email.
mails on a regular basis. (hey, I'm doing some of it right now, by
answering inline instead of top-posting.
> Another thing you have to consider is that participating a wave is not
> the same as getting an email ... if you get kicked out of the wave you
> also loose access to the whole thread... That's probably bad in some
> situations ;)
some way. Personally at least that's something I'd *need* if I were to
even consider Wave as an alternative to e-mail.
Though I don't, really. There's lots of things I'd like to use wave
for, and it may supplant *some* of my e-mail usage, but I very much
doubt it will replace it. Just look at the typical corporate e-mail
usage: Even where IM is widespread, you *still* get a lot of one-line
e-mails asking questions that can be answered with a one-line reply.
Social conventions very quickly place constraints on how a tool gets
used in specific instances - IM is seen as "too immediate" in many
social contexts (and even most IM networks dropped or never added the
"see every character as it's typed" feature because it was seen as
"too immediate" even for IM), and I suspect Wave will as well. I'd be
more inclined to think that Wave could kill of IM usage in many
contexts.
*The* biggest distinction is that you don't want your e-mail changing
on you, and you do often want to know that you are reading a "finished
product" even if that is a snapshot of someones position that may
change. There's a time and a place for collaboratively editing
something, and there's a time and place for sitting down and slowly
perusing a specific version of something (in most companies a large
percentage of the printer usage even consists of printing out draft
versions to read and comment).
To kill e-mail you need to be able to "take a snapshot" that is
"internally consistent (i.e. all participants have indicated they're
happy-at-the-moment with the state) and be able to file and get back
to that. Anything less and you're nowhere close to capturing one of
the most important modes of communication that e-mail is used for in a
corporate setting. Even if you capture that there are many other modes
of communication and social conventions to navigate...
Vidar
Vidar Hokstad
Jun 3, 2009, 5:48:28 AM6/3/09
to Google Wave API
On May 31, 12:57 am, Bastian Hoyer <daf...@gmail.com> wrote:
> Well.. my point is that I think wave won't replace email completly. I
> can remember the time before there where IM when I wrote many short
> emails to friends and co workers. Then we got icq and suddenly there
> were a better choice for many messages.
Despite that a significant percentage of my e-mails in all my
> Well.. my point is that I think wave won't replace email completly. I
> can remember the time before there where IM when I wrote many short
> emails to friends and co workers. Then we got icq and suddenly there
> were a better choice for many messages.
workplaces since IM became commonplace have been one-liners such as
"want to go to the pub for lunch?" and "when you have time look
at ....". Social conventions and impressions dictate a great deal of
what tools we use. If wave gets seen as "immediate", then it by
default becomes socially inappropriate for a lot of short messages.
> This thread was about converting or changing gmail into waves to get
> (force?) more people to use it to get it faster accepted, but I don't
> think thats necessary... I think it's more important that there will
> be other big companies providing wave accounts and integrating it into
> many products then the users will come from themselfes
A "start a wave from this e-mail" button in Gmail would be great. As
would a robot that could explicitly be added on behalf of a
participant that either prefer to get things as e-mails or doesn't
have wave. Both of those adds possibilities without pushing too hard.
I could see "taking the discussion to wave" if an e-mail thread gets
too much back and forth, for example, and possibly then wanting to
take it back to email at some stage (end of the day - people might not
want to have to deal with playback to see what's unfolding while
they're away from their client etc.)
Making the transition back and forth easy would be a killer
differentiating feature over IM where you can talk *about* the e-mail
conversation, but you don't have the actual text right there in the
same window to work on, and taking the discussion back involves
cutting and pasting and contextualizing that is tricky.
Vidar
Bastian Hoyer
Jun 3, 2009, 6:22:34 AM6/3/09
to google-...@googlegroups.com
I think another important thing would be some kind of optional
encryption that happens in the users client... I know with some xmpp
servers it's possible to log packets that contain certain keywords and
there might be stuff you want to send only encrypted.
A public key system would be nice where you could automaticly encrypt
to all members of the wavelet like gpg would be fine. Maybe this could
be also done via a browser plugin like firegpg which hooks nicely into
gmail as well.
encryption that happens in the users client... I know with some xmpp
servers it's possible to log packets that contain certain keywords and
there might be stuff you want to send only encrypted.
A public key system would be nice where you could automaticly encrypt
to all members of the wavelet like gpg would be fine. Maybe this could
be also done via a browser plugin like firegpg which hooks nicely into
gmail as well.
Joseph Gentle
Jun 3, 2009, 8:52:19 AM6/3/09
to google-...@googlegroups.com
Encryption is required in every wave client<->server and server<->server connection.
Layering end-to-end encryption on top of that would only help if you trusted the remote user(s) but not the server they used. It would make minor changes to the wave's contents very difficult to deal with. (The client would need to re-encrypt the whole wavelet and resend it every time you type another character).
To be honest, I think full end to end encryption doesn't buy you much with wave considering every link is encrypted already. If you don't trust your server, you would be better off getting a new wave account with someone you do trust (or hosting a wave server of your own).
-J
Bastian Hoyer
Jun 3, 2009, 9:07:29 AM6/3/09
to google-...@googlegroups.com
It doesn't have much to do wheter I trust my server or not. If wave is
planed as a successor to email it should at least give the same
security level as email. I know my email access is https secured and
everybody I know uses ssl but nevertheless I encrypt/sign important
mails containing access codes and stuff like that.
planed as a successor to email it should at least give the same
security level as email. I know my email access is https secured and
everybody I know uses ssl but nevertheless I encrypt/sign important
mails containing access codes and stuff like that.
Of course it wouldn't make sense to use encryption if you have enabled
the character by character transmission but if you disable that it
should be no problem to encrypt the individual documents contained in
the wavelets if you contact your lawyer or banker or send account
information to customers or stuff like that.
Reply all
Reply to author
Forward
0 new messages