all repos — honk @ 2f6e8e50ab7728478a91f135cd0ae41866fd8d0c

my fork of honk

docs/manual.txt (view raw)

 1
 2Instructions for running of the honk.
 3
 4-- following
 5
 6In order to follow somebody, you need to enter one of two identifiers.
 7
 8The easiest is probably their handle, the thing that resembles an email.
 9@name@example.com for example.
10
11Alternatively, one may directly enter the actor ID, which is a URL that looks
12like https://example.com/users/name. Note that the commonly seen URL with
13@name in it is not their actor ID and won't work.
14
15Selecting just peeping won't actually follow them. (Incomplete feature.)
16
17-- zonking
18
19You can zonk anything you like (or dislike), either your own honk or
20those of others that you're tired of seeing. This reduces its visibility, but
21doesn't attempt to delete it, which is infeasible.
22It's more like disavow.
23
24-- privacy
25
26Honks are public. Welcome to the internet.
27
28Received messages are only visible when logged in, regardless of addressing.
29
30-- css
31
32Custom CSS may be provided by creating a views/local.css file.
33
34-- message
35
36A custom server message may be set adding a ('servermsg', 'message') entry to
37the config table using sqlite3.
38
39-- emus
40
41Custom emus may be provided by creating and populating the emus directory.
42emus may be referenced when composing a honk via colon wrapping. How pleasant.
43This :example: will be replaced by emus/example.png.