Congratulations Yuri!!
Chris Cox ∙ Co-founder
  415.681.3665 ∙ [email protected] <mailto:[email protected]>
  <http://www.twitter.com/beamstream>
<http://www.linkedin.com/inviteFromProfile?from=profile&key=1228301&firstNam
e=Chris&[email protected]>
<file://localhost/skype/%20crizzcoxx>

From:  Yuri Z <[email protected]>
Reply-To:  <[email protected]>
Date:  Wed, 2 Mar 2011 14:41:04 +0200
To:  <[email protected]>
Subject:  Re: offtopic: You guys know why Google has not close their wave
servers?

> I guess it won't be 100% because Google Wave is partially dependent on
> Google infrastructure which cannot be ported.  On the other hand, WIAB might
> have features that were never implemented in Google Wave. For example WIAB
> has Inline-blip counter feature. WIAB is still a work in progress and
> features are added almost daily, so it's a bit impractical to maintain a
> list of "missing features". In general, the most important missing features
> for now (IMO) are:
> 1. Full text search.
> 2. Public waves and groups.
> 3. Roles for wave access (All, Read Only ect..)
> 4. User profiles.
> 
> If you think that missing features should be documented - please create
> issues at: http://code.google.com/p/wave-protocol/issues (at the moment the
> issues didn't move yet to Apache Jira).
> Yuri
> 
> 2011/3/2 Michael Burman <[email protected]>
> 
>>  Hi,
>> 
>>  Is there a reason why "100% functionality" shouldn't be the target (well,
>>  of
>>  course more, but at least adding all the current features at some point)?
>>  Are these even documented to the issues so some interested party could take
>>  such an issue and create it at some point (even if current committers might
>>  see something irrelevant or non important at current state) ? Something
>>  like
>>  "wishlist" as JIRA version. At least it would guarantee that some features
>>  wouldn't be forgotten when eventually Google's Wave service would go down.
>> 
>>   - Micke
>> 
>>  On Sat, Jan 22, 2011 at 9:39 PM, Matt Richards <[email protected]>
>>  wrote:
>> 
>>>  > The idea is to eventually have WiaB become the suitable replacement.
>>>  > While it will not have 100% functionality that Google's Wave had, the aim
>>>  > is
>>>  > to have it functional enough to be usable.
>>>  >
>>>  > On Sat, Jan 22, 2011 at 12:36 PM, Yuri Z <[email protected]> wrote:
>>>  >
>>>>  > > A suitable replacement - imho - it would be a free Wiab instance >>>>
hosted
>>>  > by
>>>>  > > someone (or even several federating providers). Google did open almost
>>>  > all
>>>>  > > relevant code and is also working on providing wave export utility so
>>>>  > > anyone
>>>>  > > would be able to export all his waves from Google Wave into any Wiab
>>>>  > > server.
>>>>  > > However, if you ask me, Wiab is not really close to production ready
>>>>  > > quality
>>>>  > > - some critical features still missing and there are probably a bunch
>>  of
>>>>  > > bugs that need to be fixed. So, my guess is that Google Wave would
stay
>>>  > up
>>>>  > > at least for one more year.
>>>>  > >
>>>>  > > 2011/1/22 Juan Chulilla <[email protected]>
>>>>  > >
>>>>>  > > > -----BEGIN PGP SIGNED MESSAGE-----
>>>>>  > > > Hash: SHA1
>>>>>  > > >
>>>>>  > > > Thank you, Yuri. I should have quote that help page, because it
>>>>>  > > > motivated my question. What I find more interesting is this:
>>>>>  > > >
>>>>>>  > > > > We wanted to let you know that we will keep
>>>>>> wave.google.comrunning
>>>>>>  > > > > past December 31, 2010 until a suitable replacement to host all
>>  your
>>>>>>  > > > > waves is available
>>>>>  > > >
>>>>>  > > > What dou you think that "a suitable replacement" means exactly?
While
>>>>>  > > > Google don't opensource all Wave code, is it not possible to host
>>  waves
>>>>>  > > > entirely, right?
>>>>>  > > >
>>>>>  > > > TIA
>>>>>  > > >
>>>>>  > > > Juan
>>>>>  > > >
>>>>>  > > > El 21/01/2011 23:49, Yuri Z escribió:
>>>>>>  > > > > You can learn more here -
>>>>>>  > > > > http://www.google.com/support/wave/bin/answer.py?answer=1083134
>>>>>>  > > > >
>>>>>>  > > > > 2011/1/21 Juan Chulilla <[email protected]>
>>>>>>  > > > >
>>>>>>  > > > > D-Day was December 31th. What happened exactly? Maybe they are
not
>>>>  > > going
>>>>>>  > > > > to close them?
>>>>>>  > > > >
>>>>>>  > > > > Maybe in this state wave is not a menace to gmail or docs
anymore
>>  :S.
>>>>>>  > > > > Anyway, I don't want to risk real job in a Wave that can be
closed
>>>  > any
>>>>>  > > > day.
>>>>>>  > > > >
>>>>>>  > > > > Best regards,
>>>>>>  > > > >
>>>>>>  > > > > Juan
>>>>>>  > > > >
>>>>>>>  > > > >>
>>>>>  > > >
>>>>>  > > > - --
>>>>>  > > > +++++
>>>>>  > > >
>>>>>  > > > Dr. Juan Luis Chulilla Cano
>>>>>  > > > Director, Online and Offline, S.L.
>>>>>  > > > Telf.:  91 1277356
>>>>>  > > >         650 461435
>>>>>  > > > Calle de la Paz, 8 - 28012 Madrid
>>>>>  > > >
>>>>>  > > > www.onlineandoffline.net
>>>>>  > > > -----BEGIN PGP SIGNATURE-----
>>>>>  > > > Version: GnuPG v2.0.16 (MingW32)
>>>>>  > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>>  > > >
>>>>>  > > > iEYEARECAAYFAk07HgkACgkQQtxNUwO9+XjHWACfV/2w10pR2ypYrMFrs3Bj+Az9
>>>>>  > > > WvAAn0KLFSaOIQueKyzZaj5sG1IMeVl6
>>>>>  > > > =v2JY
>>>>>  > > > -----END PGP SIGNATURE-----
>>>>>  > > >
>>>>  > >
>>>  >
>>>  >
>>>  >
>>>  > --
>>>  > --Matt
>>>  >
>> 
> 


Reply via email to