>I have to point out, none of these solutions are actually federated - >and thus unsuitable for anyone wishing to make a open network where >anyone can run a server.
WFP and WIAB was the highest! priority for pyofwave.info, we could say - the PyOfWave was the only besides WIAB which were aimed for WFP from the start. However, we'v seen that for real evolution in federation, taking the real existence and working state of considerably many - others OT, wishfully Federated systems and given that WIAB team - focused ATM on infrastructure and transaction of GWave affords. to the moment we have started XCCC like a XMPP-Concurent-Confederation-Consortium for - not only to respect the large amount independent work that made for post-gwave and other OT systems but, also, to create the solutions to federate with non-OT, still XMPP, distributed, wishfully federated, more - to invent or refine the possibility of Wave-alike systems to become a participants and contributors to W3C FSW www.federatedsocialweb.net So - superior is what we are for, but we(at least POW) don't want to say - alternatives, the best of GWave IMO was that creation of initiative to unite OT under a social network, not particularly Java or others. Obviously in other than initiative - GWave with WFP has failed. POW have in mind Apache WIAB work, as only floss s/c that use WFP, from what we know now, if there are other non WIAB floss initiatives who use WFP, their experience would be very appreciated in creation of protocols or conceptions that will help the real floss social networks federation to come reality, starting, in our case - from the most difficult part - OT systems. Arguably - supporting all(most) diversity of floss social systems and contributing to floss FSW is our intentions. The main "problem" that we need help on every objective of our work and WIAB has more committers than all our XCCC systems has as developers :) On other view - the whole fact that these - other Wave(OT) social systems could be effectively developed with 1-3 contributors on board - show the excellence of our path. Maybe we will unite like PyOfWave+ShareJS+lightwave may(i hope) in making the compatible codebase/persistence model/else - platform, maybe we'll just try our best in using suitable protocols and distributive/federation workflows, whatever we would be able to make together, now - we(PyOfWave) - work on it for contributing to big FSW network not for WFP network. My, personal, point that if we won't be able to make a sustainable model for saving and total reusing of data (world-produced knowledge heritage, name it) securely, distributively, privately etc. generated in new FSW social systems for, well, 20 years at least - the better to not done it at all, my vision is that Wave(as long as it is conception to replace most other e-social systems) First goal should be - building a real semantic web(by ideology) system where - finally - time of users would be respected. By that - Wave all-in-one conception, along with any FSW systems that will leverage that(data respect-full) ideology, would be worth of global attention and every-day using - instead of FB, G+ or any other.
