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]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 could 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.
  
  
  [b]Private Message Encryption and Privacy Concerns[/b]
  
  In the Red Matrix, public messages are not encrypted prior to leaving the originating server, they are also stored in the database in clear text.
  
  Messages marked [b]private[/b], however, 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.  
  
  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.  
  
  [b]TLS/SSL[/b]
  
  
negative.code: 
  [b]Channel Settings[/b]
  
  When a channel is created, a role is chosen which applies a number of pre-configured security and privacy settings. These are chosen for best practives to maintain privacy at the requested levels.  
  
  If you choose a "custom" privacy role, 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. There are also a number of other privacy settings you may edit.  
  
  [img]https://friendicared.net/photo/0f5be8da282858edd645b0a1a6626491.png[/img]
  
  The options are:
  
   - Nobody except yourself.
   - Only those you specifically allow.
   - Anybody in your address book.
   - Anybody on this website.
   - Anybody in this network.
   - Anybody authenticated.
   - Anybody on the Internet.
  
  
  [b]Public and Private Forums[/b]
  
  Forums are typically channels which may be open to participation from multiple authors. There are currently two mechanisms to post to forums: 1) "wall-to-wall" posts and 2) via forum @mention tags. Forums can be created by anybody and used for any purpose. The directory contains an option to search for public forums. Private forums can only be posted to and often only seen by members.
  
  
  [b]Account Cloning[/b]
  