- From: Michiel de Jong <michiel@unhosted.org>
- Date: Thu, 5 Jul 2012 10:56:53 +0300
- To: Jan Wildeboer <jwildebo@redhat.com>
- Cc: Niels Ole Salscheider <niels_ole@salscheider-online.de>, "public-fedsocweb@w3.org" <public-fedsocweb@w3.org>
either that, or just put erlang into browsers :) On Wed, Jul 4, 2012 at 7:24 PM, Jan Wildeboer <jwildebo@redhat.com> wrote: > We need XMPP server implemented in JavaScript. So it can run client or server side with node.js. > > I think every single part of the stack should be JS. With a dynamic layer that can seamlessly run code either client or server. > > That is my ideal solution for the freedom box, BTW. > > A pure JS only stack can run on very cheap hardware. Add more languages and you raise the price. > > -- > Jan H Wildeboer | > EMEA Open Source Affairs | Office: +49 (0)89 205071-207 > Red Hat GmbH | Mobile: +49 (0)174 33 23 249 > Technopark II, Haus C | Fax: +49 (0)89 205071-111 > Werner-von-Siemens-Ring 11 -15 | > 85630 Grasbrunn | > _____________________________________________________________________ > > Reg. Adresse: Red Hat GmbH, > Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15 > 85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243 > Geschaeftsfuehrer: Mark Hegarty, Charlie Peters, Michael Cunningham, > Charles Cachera > > > Am 04.07.2012 um 18:05 schrieb Niels Ole Salscheider <niels_ole@salscheider-online.de>: > >> Hello, >> >>>> email (hotmail, gmail etc.). >>> >>> ok, so there the integration is seamless, i agree. so maybe we should >>> use smtp as the server-to-server protocol for the federation of >>> private messages. i guess that could work. Would have to deal with >>> spam, but otoh, you would instantly integrate with a very large user >>> base. Would it be an option to add in- and out-going smtp to >>> StatusNet, BuddyCloud, Diaspora, Friendika, etcetera? if yes/no, why? >> >> Why do you want to use smtp? Buddycloud already uses XMPP as federation >> protocol and I think it is a more obvious choice. >> In fact, I really like that idea: XMPP is already a widely used protocol for >> chat and provides federation. Why don't we just add functionality to store >> additional information on the XMPP server (e. g. address book, calendar, >> relations to other people, public keys, your vcard, ...) and to use Activity >> Streams over XMPP ("Inbox")? >> >> Like in the mentioned example where you can edit web page A from web page B, >> you could use your account from any web page that provides the necessary >> functionality - or from a desktop / mobile application if you prefer not to >> have your web browser running all the time just to be available for chat. >> >> Of course, the stored files on the XMPP server can be made accessible by webdav >> / http, too. This way, you can easily make the content of some of these >> available on your personal web page. >> >> This way, your Jabber id can be used to identify you. All your personal >> communication (expect of email?) could be handled by the XMPP server with web >> pages and desktop applications providing access to the data. >> >> Regards, >> >> Ole > >
Received on Thursday, 5 July 2012 07:57:22 UTC