The Buddycloud approach is to build as a set of loosely coupled service oriented components with bounded context. Because:
- developers should be able to work on their components without needing to understand how everything else works. (a developer hacking on the buddycloud-media-server shouldn't need to understand how the channel-server works). - upgrading components shouldn't mean a full stack restart - intelligence lives in XMPP components / treat the XMPP server as a "stanza routing engine" XMPP gives us this component architecture, component discovery and native federation. The usual argument (on FSW and other lists) goes something like "we should have one activity stream to rule them all. It should be federated. And <a long list of unique to their project requirements>...". These requirements treat the activity stream as a pure data-feed. And conveniently ignore the application logic that manages who/how/what different groups of users can publish/read/moderate-subscribers. There's a reason why there isn't a spec that unites all social projects: everyone has different use cases. It's like saying Twitter and Facebook should interoperate. So my proposal is to focus on the loosely coupled backend services that support social: media hosting, contact matching (hash(twtterID) = Jid), posts searching, location. (Which reminds me I should really finish up the XEPs for the media-server and friend-finder) S. On 12 February 2015 at 12:59, Goffi <[email protected]> wrote: > Hi, > > I have nothing against Buddycloud and I actually think it's a good project > (even if I still hope it will become compatible with XEP-0277 soon or > late), but saying « Buddycloud is far superior to anything you are going to > find or build yourself in and out of the XMPP world. Period. » is insulting > for other projects: we are working hard too, and we have done for years. > > I don't want to enter in a project war, I naively hope that most of free > software "social network" projects have more or less a common goal and can > collaborate between them (and we have talked about collaborating in the > last 2 summits). But I can't let somebody publicly say that without > answering. > > Goffi > > On 11/02/2015 15:23, Stephen Pendleton wrote: > >> Buddycloud is far superior to anything you are going to find or build >> yourself in and out of the XMPP world. Period. Also, Buddycloud is >> superior to the walled garden stuff like Yammer. >> >> I don't contribute to Buddycloud development, but I know those guys work >> hard on it, so for you to infer it has security issues is vaguely >> insulting. >> >> On Wed, Feb 11, 2015 at 3:59 AM, Goffi <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 11/02/2015 01:33, H8H wrote: >> >> On 09.02.2015 12:15, Goffi wrote: >> We are working on a "social network" in python, and looking for >> devs ! >> The project is well advanced: http://salut-a-toi.org (demo on >> http://www.libervia.org). >> >> Still waiting for the validation mail :-) >> >> >> Oh really ? That's weird. I've just tried and it did work, so maybe >> it's being greylisted or something like that. >> >> Anyway you don't need an email to validate the account, just enter >> the login and password you choosed, the email is not checked (you >> just need something wich look like an email). >> >> Folks, we should keep this thread up, that everyone can share >> updates on >> his projects and roadmaps. >> >> >> If you want to follow what's happening, the first place is XSF's >> standard@ mailing list, where we discuss the XMPP issues we need to >> solve. Then you can follow the differents blogs (mine is >> www.goffi.org <http://www.goffi.org>, and I also publish time to >> time on planet jabber and planet jabber fr). >> >> We are also on [email protected] <mailto:[email protected]> and >> [email protected] <mailto:[email protected]> (the >> later is a small room where we discuss our inter-projects issues). >> And of course the MUC room of the projects (for Salut à Toi it's >> [email protected] <mailto:[email protected]>). >> >> So the best way if you want to be up-to-date is to choose a project >> (it seems that you have a go for buddycloud), then go to their muc >> and follow their blogs. >> >> Cheers >> Goffi >> >> _________________________________________________ >> JDev mailing list >> Info: http://mail.jabber.org/__mailman/listinfo/jdev >> <http://mail.jabber.org/mailman/listinfo/jdev> >> Unsubscribe: [email protected] >> <mailto:[email protected]> >> _________________________________________________ >> >> >> >> >> _______________________________________________ >> JDev mailing list >> Info: http://mail.jabber.org/mailman/listinfo/jdev >> Unsubscribe: [email protected] >> _______________________________________________ >> >> > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ > -- Simon Tennant | CEO Buddycloud <http://buddycloud.com> | +49 17 8545 0880
_______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
