Bruno, Thanks so much for sharing your experience. No doubt there is someone who has succeeded with federation and uses it, but I cannot think of anyone offhand. The existing commercially oriented products don't use it, AFAIK. Especially if some form of federation powers peer-to-peer mobile sharing for Wave, then basic setup needs to be baked in. Think of email - it's a little geekish to input your SMTP and POP addresses, but in general that's all it takes for a user to connect to email - perhaps it needs to be at least as simple for default Wave federation.
But also there is the issue of one app per server, which seems to be fairly baked into Wave at the moment. This makes it an app-centric platform, rather than a data-centric platform as currently configured. As I suggest in the deck, if you enable multiple UIs to access a common Wave server, then to some degree you can overcome some of the problems with vendors not wanting to federate with their competition. If the platform can enable many UIs for a common wave, then the vendors are forced to compete to present and manipulate that data on the user's terms - and that my be better both for the users and for spurring more focused and useful apps. At least that's what I am trying to suggest in my deck. So in sum, let's make federation really work, both for people like you trying to set up Web servers, let's make it work on a more granular level in peer to peer, and let's enable waves to work with multiple UI clients, so that we don't have to have federation to have choice in UIs. Thanks, John On Wed, May 29, 2013 at 3:30 AM, Bruno Gonzalez <[email protected]> wrote: > On Tue, May 28, 2013 at 11:56 PM, Ali Lown <[email protected]> wrote: > > > > A slide deck outlining this "strawman" model of where Wave could head > may > > > be found at the following address: > > > > > > https://docs.google.com/presentation/d/1pNsrX26947QH89Ot3k62nlKKSRFLmVgBWxcIEne8VYI/edit?usp=sharing > > > > I would just like to remind people that Apache Wave has had working > > federation support in the code base since creation. (Nullifying some > > of the points in slides 3,4 and 16). > > > > The problem is not the lack of federation support in Apache Wave, > > rather the lack of a roll-out of its use between currently active Wave > > servers. (Which requires the server admins at both ends of a > > federation link to make configuration changes). > > Beyond reminding people of this feature, I am unsure how we can > > increase adoption of it. Suggestions welcome? > > > > > My take on this: long ago I tried to set up a WiaB server, and I wanted it > to support federation. The aftermath of the few hours I dedicated to WiaB > was a working wave server, but no federation. The main reason, in my case, > was the lack of step-by-step documentation regarding federation, since I'm > not familiar with all the stuff relative to certificates and wasn't able to > figure it out quickly. I have no idea how many other people have tried to > set up a wave server with federation, or what their reasons for failing > are, but there's my two cents :-) > > By the way, I recently purchased a static IP address for my shitty > shared-hosting server, so I could give it a try again and try to set up > WiaB there, but I'm limited in the amount of time I can dedicate to it, so > I cannot give any promises regarding federation support... Also I'm not > sure what other wave servers out there support federation? > > -- > Saludos, > Bruno González > > _______________________________________________ > Jabber: stenyak AT gmail.com > http://www.stenyak.com >
