all repos — honk @ b03f34e2923c212dec7ec0419475271575613fdf

my fork of honk

spelling fixes from rczlonka
Ted Unangst tedu@tedunangst.com
Mon, 15 Apr 2019 17:52:39 -0400
commit

b03f34e2923c212dec7ec0419475271575613fdf

parent

405e1c153dcf38cd85a1df0b611f0c3afb2355a9

2 files changed, 3 insertions(+), 3 deletions(-)

jump to
M docs/ping.txtdocs/ping.txt

@@ -75,8 +75,8 @@ Servers which do not understand the Ping activity will hopefully ignore it.

-- usage -It is unspecified how one initiaties a ping, but it is expected to be a manual -operation performed by a system adminstrator. This will generate traffic, +It is unspecified how one initiates a ping, but it is expected to be a manual +operation performed by a system administrator. This will generate traffic, which may then be logged. The admin reads the logs and solves the problem. Specific problem solving instructions are not provided here.
M docs/spec.txtdocs/spec.txt

@@ -57,7 +57,7 @@ Such explanation would be less necessary were the tables not misused for

multiple purposes. Will probably split them apart again soon. Note that some logical seeming joins won't work. The honker column of honks -does not have a correspondng entry in the honkers table, since we frequently +does not have a corresponding entry in the honkers table, since we frequently receive messages from people we don't follow. Should we track everybody whose identity crosses our path? This seems unnecessary. The honkers table is more like a mapping of active relationships, not a directory of all peoples.