snac.1 6.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189
  1. .Dd $Mdocdate$
  2. .Dt SNAC 1
  3. .Os
  4. .Sh NAME
  5. .Nm snac
  6. .Nd A simple, minimalistic ActivityPub instance
  7. .Sh SYNOPSIS
  8. .Nm
  9. .Cm command
  10. .Ar basedir
  11. .Op Ar option ...
  12. .Sh DESCRIPTION
  13. The
  14. .Nm
  15. daemon processes messages from other servers in the Fediverse
  16. using the ActivityPub protocol.
  17. .Pp
  18. This is the user manual and expects an already running
  19. .Nm
  20. installation. For the administration manual, see
  21. .Xr snac 8 .
  22. For file and data formats, see
  23. .Xr snac 5 .
  24. .Ss Web Interface
  25. The web interface provided by
  26. .Nm
  27. is split in two data streams: the public timeline and the
  28. private timeline. There are no other feeds like the server-scoped
  29. or the federated firehoses provided by other similar ActivityPub
  30. implementations like Mastodon or Pleroma.
  31. .Pp
  32. The public timeline, also called the local timeline, is what an
  33. external visitor sees about the activity of a
  34. .Nm
  35. user: that is, only the list of public notes, boosts and likes
  36. the user generates or participates into. This is, obviously,
  37. read-only, and not very remarkable, unless the user publishes
  38. messages of staggering genious. A set of history links, grouped
  39. by month, will also be available at the bottom of the page.
  40. .Pp
  41. The private timeline, or simply the timeline, is the private,
  42. password-protected area of a
  43. .Nm
  44. server where the user really interacts with the rest of the
  45. Fediverse.
  46. .Pp
  47. The top area of the timeline provides a big text area to write
  48. notes for the public (i.e. for the user followers). As this is
  49. the second most important activity on the Fediverse, this is
  50. located in the most prominent area of the user page. You can
  51. enter plain text, @user@host mentions and other things. See the
  52. .Xr snac 5
  53. manual for more information on the allowed markup.
  54. .Pp
  55. More options are hidden under a toggle control. They are the
  56. following:
  57. .Bl -tag -offset indent
  58. .It Follow (by URL or user@host)
  59. Fill the input area with a user 'actor' URL or a user@host
  60. Fediverse identifier to follow.
  61. .It Boost (by URL)
  62. Fill the input area with the URL of a Fediverse note to be
  63. boosted.
  64. .It User setup...
  65. This option opens the user setup dialog.
  66. .El
  67. .Pp
  68. The user setup dialog allows some user information to be
  69. changed, specifically:
  70. .Bl -tag -offset indent
  71. .It User name
  72. Your user name, or not really that. People like to include
  73. emojis, flags and strange symbols for some reason.
  74. .It Avatar URL
  75. The URL of a picture to be used as your avatar in timelines
  76. around the world.
  77. .It Bio
  78. Enter here a bunch of self-indulgent blurb about yourself.
  79. The same markup options available for text notes apply here.
  80. .It Password
  81. Write the same string in these two fields to change your
  82. password. Don't write anything if you don't want to do this.
  83. .El
  84. .Pp
  85. The rest of the page contains your timeline in reverse
  86. chronological order (i.e., newest interactions first).
  87. .Nm
  88. shows the conversations as nested trees, unlike other Fediverse
  89. software; everytime something new is added to a conversation,
  90. the full thread is bumped up, so new interactions are shown
  91. always at the top of the page while the forgotten ones languish
  92. at the bottom.
  93. .Pp
  94. Private notes (a.k.a. direct messages) are also shown in
  95. the timeline as normal messages, but marked with a cute lock
  96. to mark them as non-public. Replies to direct messages are
  97. also private and cannot be liked nor boosted.
  98. .Pp
  99. For each entry in the timeline, a set of reasonable actions
  100. in the form of buttons will be shown. These can be:
  101. .Bl -tag -offset indent
  102. .It Reply
  103. Unveils a text area to write your intelligent and acute comment
  104. to an uninformed fellow. This note is sent to the original
  105. author as well as to your followers. The note can include
  106. mentions in the @user@format; these people will also become
  107. recipients of the message. If you reply to a boost or like,
  108. you are really replying to the note, not to the admirer of it.
  109. .It Like
  110. Click this if you admire this post. The poster and your
  111. followers will be informed.
  112. .It Boost
  113. Click this if you want to propagate this post to all your
  114. followers. The original author will also be informed.
  115. .It Follow
  116. Click here if you want to start receiving all the shenanigans
  117. the original author of the post will write in the future.
  118. .It Unfollow
  119. Click here if you are fed up of this fellow's activities.
  120. .It Delete
  121. Click here to send this post to the bin. If it's an activity
  122. written by you, the appropriate message is sent to the rest
  123. of involved parts telling them that you no longer want your
  124. thing in their servers (not all implementations really obey
  125. this kind of requirements, though).
  126. .It MUTE
  127. This is the most important button in
  128. .Nm
  129. and the Fediverse in general. Click it if you don't want
  130. to read crap from this user again in the forseeable future.
  131. .El
  132. .Ss Command-line options
  133. The command-line tool provide the following commands:
  134. .Bl -tag -offset indent
  135. .It Cm init Op basedir
  136. Initializes the database. This is an interactive command; necessary
  137. information will be prompted for. The
  138. .Ar basedir
  139. directory must not exist.
  140. .It Cm purge Ar basedir
  141. Purges old data from the timeline of all users.
  142. .It Cm adduser Ar basedir Op uid
  143. Adds a new user to the server. This is an interactive command;
  144. necessary information will be prompted for. Also, a copy of
  145. the server
  146. .Pa style.css
  147. is installed in the user's
  148. .Pa static/
  149. directory.
  150. .It Cm httpd Ar basedir
  151. Starts the daemon.
  152. .It Cm queue Ar basedir Ar uid
  153. Processes the output queue of the specied user, sending all
  154. enqueued messages and re-enqueing the failing ones. This command
  155. must not be executed if the server is running.
  156. .It Cm passwd Ar basedir Ar uid
  157. Changes the password for a user (interactive).
  158. .It Cm follow Ar basedir Ar uid Ar actor
  159. Sends a Follow message for the specified actor URL.
  160. .It Cm request Ar basedir Ar uid Ar url
  161. Requests an object and dumps it to stdout. This is a very low
  162. level command that is not very useful to you.
  163. .It Cm note Ar basedir Ar uid Ar text
  164. Enqueues a Create + Note message to all followers. If the
  165. .Ar text
  166. argument is - (a lonely hyphen), the external editor defined
  167. by the EDITOR environment variable will be invoked to prepare
  168. a message.
  169. .El
  170. .Sh ENVIRONMENT
  171. .Bl -tag -width Ds
  172. .It Ev DEBUG
  173. Overrides the debugging level from the server 'dbglevel' configuration
  174. variable. Set it to an integer value. The higher, the deeper in meaningless
  175. verbiage you'll find yourself into.
  176. .It Ev EDITOR
  177. The user-preferred interactive text editor to prepare messages.
  178. .El
  179. .Sh SEE ALSO
  180. .Xr snac 5 ,
  181. .Xr snac 8
  182. .Sh AUTHORS
  183. .An grunfink
  184. .Sh LICENSE
  185. See the LICENSE file for details.
  186. .Sh CAVEATS
  187. Use the Fediverse sparingly. Don't fear the mute button.
  188. .Sh BUGS
  189. Plenty. Some issues may be documented in the TODO.md file.