snac.1 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332
  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. Other fields immediately below the big text one allow some control
  56. about the post to be sent:
  57. .Bl -tag -offset indent
  58. .It Sensitive content
  59. If you set this checkbox, your post will be marked with a
  60. content warning. The immediately following, optional text box
  61. allows you to write a description about why your content is
  62. so sensitive.
  63. .It Only for mentioned people
  64. If you set this checkbox, your text will not be public, but only
  65. sent to those people you mention in the post body.
  66. .It Reply to (URL)
  67. If you fill this optional text field with the URL of another one's
  68. post, your text will be considered as a reply to it, not a
  69. standalone one.
  70. .El
  71. .Pp
  72. More options are hidden under a toggle control. They are the
  73. following:
  74. .Bl -tag -offset indent
  75. .It Follow (by URL or user@host)
  76. Fill the input area with a user 'actor' URL or a user@host
  77. Fediverse identifier to follow.
  78. .It Boost (by URL)
  79. Fill the input area with the URL of a Fediverse note to be
  80. boosted.
  81. .It User setup...
  82. This option opens the user setup dialog.
  83. .El
  84. .Pp
  85. The user setup dialog allows some user information to be
  86. changed, specifically:
  87. .Bl -tag -offset indent
  88. .It User name
  89. Your user name, or not really that. People like to include
  90. emojis, flags and strange symbols for some reason.
  91. .It Avatar URL
  92. The URL of a picture to be used as your avatar in timelines
  93. around the world.
  94. .It Bio
  95. Enter here a bunch of self-indulgent blurb about yourself.
  96. The same markup options available for text notes apply here.
  97. .It Always show sensitive content
  98. By default,
  99. .Nm
  100. hides content marked as sensitive by their publishers.
  101. If you check this option, sensitive content is always shown.
  102. .It Email address for notifications
  103. If this field is not empty, an email message will be sent
  104. to this address whenever a post written by you is liked,
  105. boosted or replied to.
  106. .It Telegram notifications
  107. To enable notifications via Telegram, fill the two provided
  108. fields (Bot API key and Chat id). You need to create both
  109. a Telegram channel and a bot for this; the process is rather
  110. cumbersome but it's documented everywhere. The Bot API key
  111. is a long string of alphanumeric characters and the chat id
  112. is a big, negative number.
  113. .It ntfy notifications
  114. To enable notifications via ntfy (both self-hosted or
  115. standard ntfy.sh server), fill the two provided
  116. fields (ntfy server/topic and, if protected, the token).
  117. You need to refer to the https://ntfy.sh web site for
  118. more information on this process.
  119. .It Maximum days to keep posts
  120. This numeric value specifies the number of days to pass before
  121. posts (yours and others') will be purged. This value overrides
  122. what the administrator defined in the global server settings
  123. only if it's lesser (i.e. you cannot keep posts for longer
  124. than what the admin desires). A value of 0 (the default) means
  125. that the global server settings will apply to the posts in your
  126. timeline.
  127. .It Drop direct messages from people you don't follow
  128. Just what it says in the tin. This is to mitigate spammers
  129. coming from Fediverse instances with lax / open registration
  130. processes. Please take note that this also avoids possibly
  131. legitimate people trying to contact you.
  132. .It Password
  133. Write the same string in these two fields to change your
  134. password. Don't write anything if you don't want to do this.
  135. .El
  136. .Pp
  137. The rest of the page contains your timeline in reverse
  138. chronological order (i.e., newest interactions first).
  139. .Nm
  140. shows the conversations as nested trees, unlike other Fediverse
  141. software; everytime you contribute something to a conversation,
  142. the full thread is bumped up, so new interactions are shown
  143. always at the top of the page while the forgotten ones languish
  144. at the bottom.
  145. .Pp
  146. Private notes (a.k.a. direct messages) are also shown in
  147. the timeline as normal messages, but marked with a cute lock
  148. to mark them as non-public. Replies to direct messages are
  149. also private and cannot be liked nor boosted.
  150. .Pp
  151. For each entry in the timeline, a set of reasonable actions
  152. in the form of buttons will be shown. These can be:
  153. .Bl -tag -offset indent
  154. .It Reply
  155. Unveils a text area to write your intelligent and acute comment
  156. to an uninformed fellow. This note is sent to the original
  157. author as well as to your followers. The note can include
  158. mentions in the @user@format; these people will also become
  159. recipients of the message. If you reply to a boost or like,
  160. you are really replying to the note, not to the admirer of it.
  161. .It Like
  162. Click this if you admire this post. The poster and your
  163. followers will be informed.
  164. .It Boost
  165. Click this if you want to propagate this post to all your
  166. followers. The original author will also be informed.
  167. .It Follow
  168. Click here if you want to start receiving all the shenanigans
  169. the original author of the post will write in the future.
  170. .It Unfollow
  171. Click here if you are fed up of this fellow's activities.
  172. .It Delete
  173. Click here to send this post to the bin. If it's an activity
  174. written by you, the appropriate message is sent to the rest
  175. of involved parts telling them that you no longer want your
  176. thing in their servers (not all implementations really obey
  177. this kind of requirements, though).
  178. .It MUTE
  179. This is the most important button in
  180. .Nm
  181. and the Fediverse in general. Click it if you don't want
  182. to read crap from this user again in the forseeable future.
  183. .It Hide
  184. If a conversation is getting long and annoying but not enough
  185. to MUTE its author forever, click this button to avoid seeing
  186. the post and its children anymore.
  187. .It Edit
  188. Posts written by you on
  189. .Nm
  190. version 2.19 and later can be edited and resent to their
  191. recipients.
  192. .El
  193. .Ss Command-line options
  194. The command-line tool provide the following commands:
  195. .Bl -tag -offset indent
  196. .It Cm init Op basedir
  197. Initializes the data storage. This is an interactive command; necessary
  198. information will be prompted for. The
  199. .Ar basedir
  200. directory must not exist.
  201. .It Cm upgrade Ar basedir
  202. Upgrades the data storage after installing a new version.
  203. Only necessary if
  204. .Nm
  205. complains and demands it.
  206. .It Cm httpd Ar basedir
  207. Starts the daemon.
  208. .It Cm purge Ar basedir
  209. Purges old data from the timeline of all users.
  210. .It Cm adduser Ar basedir Op uid
  211. Adds a new user to the server. This is an interactive command;
  212. necessary information will be prompted for.
  213. .It Cm resetpwd Ar basedir Ar uid
  214. Resets a user's password to a new, random one.
  215. .It Cm queue Ar basedir Ar uid
  216. Processes the output queue of the specied user, sending all
  217. enqueued messages and re-enqueing the failing ones. This command
  218. must not be executed if the server is running.
  219. .It Cm follow Ar basedir Ar uid Ar actor
  220. Sends a Follow message for the specified actor URL.
  221. .It Cm request Ar basedir Ar uid Ar url
  222. Requests an object and dumps it to stdout. This is a very low
  223. level command that is not very useful to you.
  224. .It Cm note Ar basedir Ar uid Ar text Op file file ...
  225. Enqueues a Create + Note message to all followers. If the
  226. .Ar text
  227. argument is -e, the external editor defined by the EDITOR
  228. environment variable will be invoked to prepare a message; if
  229. it's - (a lonely hyphen), the post content will be read from stdin.
  230. The rest of command line arguments are treated as media files to be
  231. attached to the post.
  232. .It Cm block Ar basedir Ar instance_url
  233. Blocks a full instance, given its URL or domain name. All subsequent
  234. incoming activities with identifiers from that instance will be immediately
  235. blocked without further inspection.
  236. .It Cm unblock Ar basedir Ar instance_url
  237. Unblocks a previously blocked instance.
  238. .It Cm verify_links Ar basedir Ar uid
  239. Verifies all links stored as metadata for the given user. This verification
  240. is done by downloading the link content and searching for a link back to
  241. the
  242. .Nm
  243. user url that also contains a rel="me" attribute. These links are specially
  244. marked as verified in the user's public timeline and also via the Mastodon API.
  245. .It Cm state Ar basedir
  246. Dumps the current state of the server and its threads. For example:
  247. .Bd -literal -offset indent
  248. server: comam.es (snac/2.45-dev)
  249. uptime: 0:03:09:52
  250. job fifo size (cur): 45
  251. job fifo size (peak): 1532
  252. thread #0 state: input
  253. thread #1 state: input
  254. thread #2 state: waiting
  255. thread #3 state: waiting
  256. thread #4 state: output
  257. thread #5 state: output
  258. thread #6 state: output
  259. thread #7 state: waiting
  260. .Ed
  261. .Pp
  262. The job fifo size values show the current and peak sizes of the
  263. in-memory job queue. The thread state can be: waiting (idle waiting
  264. for a job to be assigned), input or output (processing I/O packets)
  265. or stopped (not running, only to be seen while starting or stopping
  266. the server).
  267. .El
  268. .Ss Migrating an account from Mastodon
  269. See
  270. .Xr snac 8
  271. for details.
  272. .Ss Using Mastodon-compatible apps
  273. Since version 2.27,
  274. .Nm
  275. includes support for the Mastodon API, so you can use Mastodon-compatible
  276. mobile and desktop applications to access your account. Given a correctly
  277. configured server, the usage of these programs should be straightforward.
  278. Please take note that they will show your timeline in a 'Mastodon fashion'
  279. (i.e., as a plain list of posts), so you will lose the fancy, nested thread
  280. post display with the most active threads at the top that the web interface of
  281. .Nm
  282. provides.
  283. .Ss Implementing post bots
  284. .Nm
  285. makes very easy to post messages in a non-interactive manner. This example
  286. posts a string:
  287. .Bd -literal -offset indent
  288. uptime | snac note $SNAC_BASEDIR $SNAC_USER -
  289. .Ed
  290. .Pp
  291. You can setup a line like this from a
  292. .Xr crontab 5
  293. or similar. Take note that you need a) command-line access to the same machine
  294. that hosts the
  295. .Nm
  296. instance, and b) write permissions to the storage directories and files.
  297. .Pp
  298. You can also post non-interactively using the Mastodon API and a command-line
  299. http tool like
  300. .Xr curl 1
  301. or similar. This has the advantage that you can do it remotely from any host,
  302. anywhere; the only thing you need is an API Token. This is an example:
  303. .Bd -literal -offset indent
  304. curl -X POST https://$SNAC_HOST/api/v1/statuses \\
  305. --header "Authorization: Bearer ${TOKEN}" -d "status=$(uptime)"
  306. .Ed
  307. .Pp
  308. You can obtain an API Token by connecting to the following URL:
  309. .Bd -literal -offset indent
  310. https://$SNAC_HOST/oauth/x-snac-get-token
  311. .Ed
  312. .Pp
  313. .Sh ENVIRONMENT
  314. .Bl -tag -width Ds
  315. .It Ev DEBUG
  316. Overrides the debugging level from the server 'dbglevel' configuration
  317. variable. Set it to an integer value. The higher, the deeper in meaningless
  318. verbiage you'll find yourself into.
  319. .It Ev EDITOR
  320. The user-preferred interactive text editor to prepare messages.
  321. .El
  322. .Sh SEE ALSO
  323. .Xr snac 5 ,
  324. .Xr snac 8
  325. .Sh AUTHORS
  326. .An grunfink Lk https://comam.es/snac/grunfink @grunfink@comam.es
  327. .Sh LICENSE
  328. See the LICENSE file for details.
  329. .Sh CAVEATS
  330. Use the Fediverse sparingly. Don't fear the MUTE button.
  331. .Sh BUGS
  332. Probably plenty. Some issues may be even documented in the TODO.md file.