I haven't had time to contribute to Apache Wave in a very long time, so
I'm in no position to debate about its future, but my opinion is similar
to Thomas': removing federation from wave goals (even if federation is
not working at the moment, or is so hard to get to work that nobody uses
it anyway), would be removing one of the most important defining
features (in my view) of wave protocol.
On 2016-04-07 17:42, Thomas Wrobel wrote:
I'm not sure there's any point in wave without federation frankly.
I supported wave because I didn't want the net turning into "facebook
protocols" and "google protocols" etc. We need new emails. Protocols
that allow people on different servers to communicate, not protocols
trying to get everyone on the same companies server.
I still fear a future of incompatibility. Of people having to be on
server X because their friends are all on server X (and thus server X
has no incentive to ever get better). Email is getting increasingly
dated, and there's not much else federated out there even today. As
the web grows into real-space applications, there will be probably
even greater need for open communications standards.
While the comparison of email interface wise might have harmed wave
somewhat from a user expectation standpoint, I do think the same needs
are there - a new federated, open, protocol to deal with today's web.
- sigh -
--
http://lostagain.nl <-- our company site.
http://fanficmaker.com <-- our, really,really, bad story generator.
On 7 April 2016 at 17:25, Yuri Z <vega...@gmail.com> wrote:
Hi
Currently the federation is broken and requires a significant effort
to
fix. Moreover, it never worked perfectly and always was a kind of
Proof Of
Concept version. I doubt we can improve the current implementation to
be
something stable.
Therefore I suggest to remove from Wave source all code and
dependencies
related to Federation.
Thoughts?
--
Regards/Saludos,
Bruno Gonzalez
