indymedia
/
epicyon
mirror of https://gitlab.com/bashrc2/epicyon
7
4
Fork 1
Code Issues 14 Releases Wiki Activity

Describe refreshing the timeline in Lynx

main
Bob Mottram 2024-12-19 13:07:36 +00:00
parent 240be8afe0
commit b0f8ec0699
3 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
manual/manual.epub
View File

Binary file not shown.

3
manual/manual.html
View File

@ -1173,6 +1173,9 @@ alt="Inbox viewed within a shell browser" />
<figcaption aria-hidden="true">Inbox viewed within a shell <figcaption aria-hidden="true">Inbox viewed within a shell
browser</figcaption> browser</figcaption>
</figure> </figure>
<p>The typical way of refreshing the timeline is to go to the top,
select <strong>Inbox</strong> from the menu, then use
<strong>CTRL-R</strong> to reload.</p>
<h1 id="content-licenses">Content licenses</h1> <h1 id="content-licenses">Content licenses</h1>
<p>ActivityPub posts are really just content on a website and so are <p>ActivityPub posts are really just content on a website and so are
subject to copyright rules. Historically, the copyright status of posts subject to copyright rules. Historically, the copyright status of posts

2
manual/manual.md
View File

@ -829,6 +829,8 @@ Timelines will look something like the following.
![Inbox viewed within a shell browser](manual-lynx-inbox.png) ![Inbox viewed within a shell browser](manual-lynx-inbox.png)
The typical way of refreshing the timeline is to go to the top, select **Inbox** from the menu, then use **CTRL-R** to reload.
# Content licenses # 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. 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.