tileradotorg/synapse
1
0
Fork 0
forked from MirrorHub/synapse
Code Pull requests Activity

Merge pull request #801 from ruma/readme-history-storage

Browse source 
Alter phrasing to clarify where info is stored.
This commit is contained in:
Matthew Hodgson 2016-05-29 10:37:04 +01:00
commit 42a9ea37e4
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
README.rst
View file

@ -58,12 +58,13 @@ the spec in the context of a codebase and let you run your own homeserver and
generally help bootstrap the ecosystem. generally help bootstrap the ecosystem.
In Matrix, every user runs one or more Matrix clients, which connect through to In Matrix, every user runs one or more Matrix clients, which connect through to
a Matrix homeserver which stores all their personal chat history and user a Matrix homeserver. The homeserver stores all their personal chat history and
account information - much as a mail client connects through to an IMAP/SMTP user account information - much as a mail client connects through to an
server. Just like email, you can either run your own Matrix homeserver and IMAP/SMTP server. Just like email, you can either run your own Matrix
control and own your own communications and history or use one hosted by homeserver and control and own your own communications and history or use one
someone else (e.g. matrix.org) - there is no single point of control or hosted by someone else (e.g. matrix.org) - there is no single point of control
mandatory service provider in Matrix, unlike WhatsApp, Facebook, Hangouts, etc. or mandatory service provider in Matrix, unlike WhatsApp, Facebook, Hangouts,
etc.
Synapse ships with two basic demo Matrix clients: webclient (a basic group chat Synapse ships with two basic demo Matrix clients: webclient (a basic group chat
web client demo implemented in AngularJS) and cmdclient (a basic Python web client demo implemented in AngularJS) and cmdclient (a basic Python