Add content licenses to manual

manual/manual.html

@@ -1051,6 +1051,26 @@ alt="Inbox viewed within a shell browser" />
 <figcaption aria-hidden="true">Inbox viewed within a shell
 browser</figcaption>
 </figure>
+<h1 id="content-licenses">Content licenses</h1>
+<p>ActivityPub posts are really just content on a website and so are
+subject to copyright rules. Historically, the copyright status of posts
+was always left as ambiguous but in Epicyon for the avoidance of
+disputes it is made explicit. Setting the scope of a post, such as being
+to followers only, is not sufficient to indicate how that post is
+intended to be used.</p>
+<p>Content licensing is at the instance level, and set by the
+administrator. Log in as the administrator and then go to <em>instance
+settings</em>. From there you can set the content license, which should
+be the URL for the full license text.</p>
+<p>When subsequently creating posts a small copyright icon will appear,
+which then links back to the license.</p>
+<p>The choice of content license is for the instance administrator to
+decide, but it is recommended that <a
+href="https://creativecommons.org/licenses/by-nc/4.0/legalcode">non-commercial
+creative commons licenses</a> may be enough to deter some of the worst
+abuses of <a
+href="https://en.wikipedia.org/wiki/Personal_data">personally
+identifiable information</a> by BigTech companies.</p>
 <h1 id="building-fediverse-communities">Building fediverse
 communities</h1>
 <p>The great thing about running a small instance is that you can do

manual/manual.md

@@ -749,6 +749,16 @@ Timelines will look something like the following.
 
 ![Inbox viewed within a shell browser](manual-lynx-inbox.png)
 
+# Content licenses
+
+ActivityPub posts are really just content on a website and so are subject to copyright rules. Historically, the copyright status of posts was always left as ambiguous but in Epicyon for the avoidance of disputes it is made explicit. Setting the scope of a post, such as being to followers only, is not sufficient to indicate how that post is intended to be used.
+
+Content licensing is at the instance level, and set by the administrator. Log in as the administrator and then go to *instance settings*. From there you can set the content license, which should be the URL for the full license text.
+
+When subsequently creating posts a small copyright icon will appear, which then links back to the license.
+
+The choice of content license is for the instance administrator to decide, but it is recommended that [non-commercial creative commons licenses](https://creativecommons.org/licenses/by-nc/4.0/legalcode) may be enough to deter some of the worst abuses of [personally identifiable information](https://en.wikipedia.org/wiki/Personal_data) by BigTech companies.
+
 # Building fediverse communities
 The great thing about running a small instance is that you can do things in whatever manner you prefer. What follows is a few guidelines which may help.
 

website/EN/v1_4_0.html

@@ -1201,10 +1201,11 @@
 	          <li>Support for auto-linking scientific paper references</li>
 	          <li>Edit button</li>
 	          <li>Improved calendar events</li>
-            <li>Added a user manual</li>
+            <li>Added a <a href="https://gitlab.com/bashrc2/epicyon/-/blob/main/manual/manual.md">user manual</a></li>
             <li>Hashtag maps for crowdsourced geolocations</li>
 	          <li>Option to expire old posts</li>
 	          <li>Better emoji support</li>
+	          <li>Included an updated version of the <a href="https://gitlab.com/bashrc2/epicyon/-/blob/main/specification/activitypub.md">ActivityPub specification</a></li>
 	          <li>Unicode fonts no longer bypass filters</li>
 	          <li>vCard support</li>
 	          <li>Improved podcast support</li>