anchor.diff:  
   [b]Account Deletion[/b]
   
  -Accounts can be immediately deleted by clicking on a link. That's it.  All associated content is immediately deleted from the matrix (this includes posts and any other content produced by the deleted profile).
  +Accounts can be immediately deleted by clicking on a link. That's it.  All associated content is then deleted from the matrix (this includes posts and any other content produced by the deleted profile). Depending on the number of connections you have, the process of deleting remote content could take some time but it is scheduled to happen as quickly as is practical.
   
   [b][size=20]Content Creation[/size][/b]
   
   [b]Writing Posts[/b]
   
  -Red supports a number of different ways of adding content, from a graphical text editor, to various types of markup and pure HTML.
  +Red supports a number of different ways of adding rich-text content. The default is a custom variant of BBcode, tailored for use in Redmatrix. You may also enable the use of Markdown if you find that easier to work with. A visual editor may also be used. The traditional visual editor for Redmatrix had some serious issues and has since been removed. We are currently looking for a replacement. 
   
  -Red bundles the TinyMCE rich text editor, which can be turned on under &quot;Settings.&quot;
  -For user who prefer not to use TinyMCE, content can be entered by typing BBCode markup.
  -Furthermore, when creating &quot;Websites&quot; or using &quot;Comanche&quot; and its PCL[FINISH], content can be entered in HTML, Markdown and plain text.
  +When creating &quot;Websites&quot;, content may be entered in HTML, Markdown, BBcode, and/or plain text.
   
   [b]Deletion of content[/b]
  -Any content created in the Red Matrix remains under the control of the user (or channel) that originally created.  At any time, a user can delete a message, or a range of messages.  The deletion process ensures that the content is deleted, regardless of whether it was posted on a channel's primary (home) hub, or on another hub, where the channel was remotely authenticated via Zot.
  +Any content created in the Red Matrix remains under the control of the member (or channel) that originally created it.  At any time, a member can delete a message, or a range of messages.  The deletion process ensures that the content is deleted, regardless of whether it was posted on a channel's primary (home) hub, or on another hub, where the channel was remotely authenticated via Zot.
   
   [b]Media[/b]
   Similar to any other modern blogging system, social network, or a micro-blogging service, Red supports the uploading of files, embedding of videos, linking web pages.
   
  -[b]Previewing[/b] 
  -Post can be previewed prior to sending.
  +[b]Previewing/Editing[/b] 
  +Post can be previewed prior to sending and edited after sending.
  +
  +[b]Extending Redmatrix[/b]
  +
  +Redmatrix can be extended in a number of ways, through site customisation, personal customisation, option setting, themes, and addons/plugins. 
  +
  +[b]API[/b]
  +
  +An API is available for use by third-party services. This is based originally on the early Twitter API (for which hundreds of third-party tools exist). It is currently being extended to provide access to facilities and abilities which are specific to Redmatrix. Access may be provided by login/password or OAuth and client registration of OAuth applications is provided.
  +
  + 
   
   #include doc/macros/main_footer.bb;
  
positive.code: 
  [b]Channel Settings[/b]
  
  In Red, each channel allows fine-grained permissions to be set for various aspects of communication.  For example, under the &quot;Security and Privacy Settings&quot; heading, each aspect on the left side of the page, has six (6) possible viewing/access options, that can be selected by clicking on the dropdown menu.
  
  [img]https://friendicared.net/photo/0f5be8da282858edd645b0a1a6626491.png[/img]
  
  The six options are:
  
   - Nobody except yourself.
   - Only those you specifically allow.
   - Anybody in your address book.
   - Anybody on this website.
   - Anybody in this network.
   - Anybody on the Internet.
  
  
  [b]Account Cloning[/b]
  
negative.code: 
  [b]Access Control Lists[/b]
  
  When sharing content with someone in their contact list, users have the option of restricting who sees the content.  By clicking on the padlock underneath the sharing box, one may choose desired recipients of the post, by clicking on their names.
  
  Once sent, the message will be viewable only by the sender and the selected recipients.  In other words, the message will not appear on any public walls.
  
  Access Control Lists may be applied to content and posts, photos, events, webpages, chatrooms and files. 
  
  [b]Single Sign-on[/b]
  
  Access Control Lists work for all channels in the matrix due to our unique single sign-on technology. Most internal links provide an identity token which can be verified on other Redmatrix sites and used to control access to private resources. You login once to your home hub. After that, authentication to all Redmatrix resources is "magic".
  
  
  [b]WebDAV enabled File Storage[/b]
  
  Files may be uploaded to your personal storage area using your operating system utilities (drag and drop in most cases). You may protect these files with Access Control Lists to any combination of Redmatrix members (including some third party network members) or make them public.
  
  [b]Photo Albums[/b]
  
  Store photos in albums. These may be protected by Access Control Lists.
  
  [b]Events Calendar[/b]
  
  Create and manage events, which may also be protected with Access Control Lists. Events can be exported to other software using the industry standard vcalendar/iCal format and shared in posts with others. Birthday events are automatically added from your friends and converted to your correct timezone so that you will know precisely when the birthday occurs - no matter where you are located in the world in relation to the birthday person. 
  
  [b]Chatrooms[/b]
  
  You may create any number of personal chatrooms and allow access via Access Control Lists. These are typically more secure than XMPP, IRC, and other Instant Messaging transports, though we also allow using these other services via plugins.       
  
  [b]Webpage Building[/b]
  
  Redmatrix has many "Content Management" creation tools for building webpages, including layout editing, menus, blocks, widgets, and page/content regions. All of these may be access controlled so that the resulting pages are private to their intended audience. 
  
  [b]Apps[/b]
  
  Apps may be built and distributed by members. These are different from traditional "vendor lockin" apps because they are controlled completely by the author - who can provide access control on the destination app pages and charge accordingly for this access. Most apps in Redmatrix are free and can be created easily by those with no programming skills. 
  
  [b]Layout[/b]
  
  Page layout is based on a description language called Comanche. Redmatrix is itself written in Comanche layouts which you can change. This allows a level of customisation you won't typically find in so-called "multi-user environments".
  
  [b]Bookmarks[/b]
  
  Share and save/manage bookmarks from links provided in conversations.    
   
   
  [b]Private Message Encryption and Privacy Concerns[/b]
  
  Messages marked [b]private[/b] are encrypted with AES-CBC 256-bit symmetric cipher, which is then protected (encrypted in turn) by public key cryptography, based on 4096-bit RSA keys, associated with the channel that is sending the message.  
  
  These private messages are also stored in an encrypted form on remote systems. 
  
  Each Red channel has it's own unique set of private and associated public RSA 4096-bit keys, generated when the channels is first created.
  
  Additionally, messages may be created utilising "end-to-end encryption" which cannot be read by Redmatrix operators or ISPs or anybody who does not know the passcode. 
  
  Public messages are generally not encrypted in transit or in storage.  
  
  Private messages may be retracted (unsent) although there is no guarantee the recipient hasn't read it yet.
  
  Posts and messages may be created with an expiration date, at which time they will be deleted/removed on the recipient's site.  
  
  
  [b]Service Federation[/b]
  
  In addition to addon "cross-post connectors" to a variety of alternate networks, there is native support for importation of content from RSS/Atom feeds and using this to create special channels. Also, an experimental but working implementation of the Diaspora protocol allows communication with people on the Friendica and Diaspora decentralised social networks. This is currently marked experimental because these networks do not have the same level of privacy and encryption features and abilities as Redmatrix and may present privacy risks.
  
  There is also experimental support for OpenID authentication which may be used in Access Control Lists. This is a work in progress. 
  
  Channels may have permissions to become "derivative channels" where two or more existing channels combine to create a new topical channel. 
  
  [b]Collections[/b]
  
  "Collections" is our implementation of privacy groups, which is similar to Google "Circles" and Diaspora "Aspects". This allows you to filter your incoming stream by collections or groups, and automatically set the outbound Access Control List to only those in the Collection when you post. You may over-ride this at any time. 
  
  
  [b]Directory Services[/b]
  
  We provide easy access to a directory of members and provide decentralised tools capable of providing friend "suggestions". The directories are normal Redmatrix sites which have chosen to accept the directory server role. This requires more resources than most typical sites so is not the default. Directories are synchronised and mirrored so that they all contain up-to-date information on the entire network (subject to normal propagation delays).  
   
  
  [b]TLS/SSL[/b]
  
  