From 01c97f11790e49018d8256a2bb8ae50c4030067d Mon Sep 17 00:00:00 2001 From: Jason Volk Date: Tue, 18 Sep 2018 03:36:47 -0700 Subject: [PATCH] Update main README links and client README. --- README.md | 8 ++++++-- share/webapp/README.md | 30 +++--------------------------- 2 files changed, 9 insertions(+), 29 deletions(-) diff --git a/README.md b/README.md index 7f482d4c7..838952a2f 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,9 @@ # This — is The **Construct** - + + + #### Internet Relay Chat daemon: *Matrix Construct* @@ -28,7 +30,9 @@ real-time communication for free and open source software: a *federation of netw IRCd has been rewritten for the global federation of networks     - + + + **This is the Construct** — the first Matrix server written in C++. It is designed to be fast and highly scalable, and to be community developed by volunteer contributors over diff --git a/share/webapp/README.md b/share/webapp/README.md index 45f9535c6..4747fd2f3 100644 --- a/share/webapp/README.md +++ b/share/webapp/README.md @@ -1,32 +1,8 @@ -## IRCd (Charybdis) Client +## Construct Client + + This client provides a fully functioning Matrix chat experience in addition to driving the server administration functions of IRCd. This client should not de-prioritize the chat client features in favor of focusing on server admin: it is testbed for any new features and experimentation conducted with IRCd. - -The "Matrix" chat protocol is an extensible and recursively structured approach to the next -evolution of the Internet Relay Chat (IRC) protocol. Though not syntactically backwards-compatible -with the IRC protocol, it can be easily translated as a superset. Similar to IRC protocol's -origins, it wisely leverages technologies in vogue for its day to aid the virility of -implementations. - -As the 3rd major-version evolution of IRC, we refer to IRC^3 or "IRC cubed" or "Matrix protocol" -as all the same entity. - -Matrix protocol achieves what the last IRC protocol could not, among other things: a -consolidated internetworked federation of servers/networks that can all speak to each other. -Authority in the federation is partitioned by domain-names and uses the standard URL system. - -IRCv2 is deadlocked in part because of the ecosystem of servers and clients are old; they push -the limits of cross-platform compatibility to deliver the best graphical or terminal experience -from their day (and to this day!). The protocol has shallow structure; evolving it adds inelegant -complexity. There was no attempt at forward-compatibility; it is easily broken. The initiative to -propose and develop a new feature with widespread adoption is suppressed by these facts. - -While the first conception of the IRC protocol in 1988 made considerations for a person typing -at a local or remote-access textual terminal, matrix makes considerations for "the web." The -protocol stands on the shoulders of JSON content transferred via HTTP requests. This choice -permits the seamless implementation of clients developed with the best choice for developing -a client in this epoch: the javascript-actuated stylized-document object in a browser -- which -is customized dynamically from the server.