20
edits
Line 187: | Line 187: | ||
Currently, only some clients (iChat, Gajim) support server-less chatting, a feature which is very interesting to be able to discover and communicate with people on a local network, without the need to be connected to the internet. The reason behind the slow adoption of this protocol is probably that it breaks with the very fundamental way Jabber is designed (client-server architecture), and as such is a significant amount of work for an existing client to adapt its codebase. The aim of this project is to bring server-less messaging to every XMPP client, by implementing it outside of the client. | Currently, only some clients (iChat, Gajim) support server-less chatting, a feature which is very interesting to be able to discover and communicate with people on a local network, without the need to be connected to the internet. The reason behind the slow adoption of this protocol is probably that it breaks with the very fundamental way Jabber is designed (client-server architecture), and as such is a significant amount of work for an existing client to adapt its codebase. The aim of this project is to bring server-less messaging to every XMPP client, by implementing it outside of the client. | ||
The goal of this project is to implement a lightweight Jabber daemon that acts as a regular jabber server on the client side, but uses [http://www.jabber.org/ | The goal of this project is to implement a lightweight Jabber daemon that acts as a regular jabber server on the client side, but uses [http://www.jabber.org/xeps/xep-0174.html Link Local Messaging] on the server side. By connecting your favorite client to this daemon running on your own machine, you enable server-less messaging for this client. The project should be written in a cross-platform way to reach a large population of clients. Language can be chosen, as long as there is a decent library available to do zeroconf networking (examples include Python and C++). |
edits