|
On 26/08/2017 14:56, Mathieu Bridon wrote: On Fri, 2017-08-25 at 19:13 +0100, Matthew Hodgson wrote:My proposal is that one could run a background daemon on Linux which brokered the connection to your Matrix server (and perhaps handled fun stuff like clientside history persistence, e2e encryption voodoo, WebRTC audio playback/capture etc) and then expose that as part of the OS to desktop apps - effectively as a next gen telepathy equivalent.Why bother with a Matrix server at all? Couldn't that local daemon effectively be the Matrix server? At the moment Matrix servers are discovered by DNS and effectively act like any old webservice. We're experimenting with the idea of p2p Matrix though, which would instead use a DHT for discovery - at which point yes, this daemon could act as a fully fledged Matrix server. This would take up a lot more resources (network traffic, consensus calculation, storage) than a daemon acting as a headless client however. And it's still debatable as to whether apps would want to talk to this daemon via the Matrix Client/Server HTTP API or via a more telepathy-style API (which could leave the daemon to handle the 'hard' stuff like e2e crypto, storing local history, etc). At which point from the client app's perspective it wouldn't care if it was talking to a headless client daemon, a server, or a different connection manager entirely. (Of course, native Matrix clients could just talk Matrix natively to their preferred server). M
-- Matthew Hodgson Matrix.org |