Yes, I second that. My preference would be that a future version of Thunderbird has wave support and would just handle wave accounts as easily as it handles IMAP accounts.

Cheers, Eric

On 2010-02-10 7:13 AM, Carol Haney wrote:
I agree - email and wave should be one service. It is a misstep to keep them separate.

On Wed, Feb 10, 2010 at 6:50 AM, kayode odeyemi <[email protected] <mailto:[email protected]>> wrote:

    IMHO, I think it's just an extension to Gmail. An option to make
    Gmail better and have some social interaction integration.

    Wave is a different project on it's own. But I support the opinion
    about integrating Gmail into Wave. Reason is because there's
    hardly no conversation without email these days.

    2010/2/10 Raphaël Pinson <[email protected]
    <mailto:[email protected]>>

        I try to keep in mind that Wave is first and foremost a
        protocol, while Buzz is a social media plugin for Gmail (or so
        it seems).

        I believe the Wave protocol could well be the backbone for
        Buzz actually, so it's not a matter of Wave vs. Buzz (as in,
        the interface, which doesn't really matter so much in Wave).



        Raphaël


        On Wed, Feb 10, 2010 at 3:42 AM, Jonas Huckestein
        <[email protected] <mailto:[email protected]>> wrote:

            I think Wave and Buzz are completely different things. The
            wave hype
            has worn off because it is a development version and most
            people don't
            understand that.

            It is my impression that Wave targets email and in particular
            enterprise platforms such as MS exchange/sharepoint.

            Buzz on the other hand is going for twitter/facebook.

            Just my $0.02

            Cheers, Jonas

            On Feb 9, 5:26 pm, dougx <[email protected]
            <mailto:[email protected]>> wrote:
            > I very _very_ much doubt that buzz is going to
            free-as-in-beer the
            > same way wave promises to be.
            >
            > That's a pretty major difference.
            >
            > There are a few things there that look a bit familiar
            though, for
            >
            example:http://code.google.com/apis/buzz/documentation/#coming-soon
            > "Over the next several months Google Buzz will introduce
            an API for
            > developers, including full/read write support for posts
            with the Atom
            > Publishing Protocol, rich activity notification with
            Activity Streams,
            > delegated authorization with OAuth, federated comments
            and activities
            > with Salmon, distributed profile and contact information
            with
            > WebFinger, and much, much more."
            >
            > ...but if you look at the details, it's not really very
            wave-like;
            > certainly I don't see anything about conflict resolution for
            > collaborative editing; it's just a comment sharing tool.
            >
            > ~
            > Doug.
            >
            > On Feb 10, 3:33 am, Daniel França
            <[email protected] <mailto:[email protected]>>
            wrote:
            >
            > > I was watching the video introducing Google
            
Buzzhttp://googleblog.blogspot.com/2010/02/introducing-google-buzz.html?u.
            
<http://googleblog.blogspot.com/2010/02/introducing-google-buzz.html?u.>..
            >
            > > It has some Wave like features, doesn't?  It looks
            like if the recent low
            > > entusiasm about Wave can migrate efforts to this new
            tool? Or am I
            > > completely wrong?

            --
            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]
            <mailto:[email protected]>.
            To unsubscribe from this group, send email to
            [email protected]
            <mailto:google-wave-api%[email protected]>.
            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
        [email protected]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:google-wave-api%[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/google-wave-api?hl=en.




-- Odeyemi 'Kayode O.

    Application Developer & Systems Engineer (Sun Certified Professional),
    Drupal Developer

    Tel: +2348053063373
    P.O.Box 682, Ita-elewa, Ikorodu,
    Lagos, Nigeria, West-Africa.

    Website: http://www.sinati.com
    Socialize with me: http://profile.to/charyorde,
    http://twitter.com/charyorde

-- 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]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:google-wave-api%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/google-wave-api?hl=en.




--
Carol Sue Haney
--
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.

--
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.

Reply via email to