dirk
/
honk
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

the schema is a little better than before

This commit is contained in:
Ted Unangst 2019-04-19 22:58:49 -04:00
parent 0e78b38ea0
commit 41675d331d
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/spec.txt
View File

@ -47,15 +47,17 @@ out okay though.
The honkers table is used to manage follows and followers. The flavor column The honkers table is used to manage follows and followers. The flavor column
describes what. 'sub' is a follow. We have subscribed to their newsletter. describes what. 'sub' is a follow. We have subscribed to their newsletter.
'dub' is a follower. They get dubbed whenever we honk. We also use this table 'dub' is a follower. They get dubbed whenever we honk.
to store public keys for anyone we interact with. This is regrettable.
The xonkers table stores info about external accounts that we may interact
with. Their keys, their inboxes, etc.
The zonkers table stores things we do not wish to see, per the wherefore
column. zonkers are bad people, zurls are bad hosts, zonvoys are bad threads.
The xid column generally corresponds to ActivityPub id. For local honks, it The xid column generally corresponds to ActivityPub id. For local honks, it
will be a short string, not a complete URL. will be a short string, not a complete URL.
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 Note that some logical seeming joins won't work. The honker column of honks
does not have a corresponding 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 receive messages from people we don't follow. Should we track everybody whose