Just checked out the repo, if your ambitions are to eventually make this distributed. You could make the payout-hook into a callable with some kind of standardized output format that the server understands. Then allow a substacker to config a pointer to the endpoint.
ex: stacker.news would send a POST w/ a body such as
{'substack' : '/s/mysubstack', 'commenter' : '/u/jeff', 'comment' : '1234', 'tip' : '100'}
...and then my own server could send back:
[{'payto' : '/u/jeff', 'amt' : '50'}, {'payto' : '/s/erickuhn19', 'amt' : '20'}, {'payto' : '/u/anonporridge', 'amt' : '30'}]
...this could be open sourced, or closed source. People could audit both the history, and "test" the endpoint themselves with a hypothetical POST-body.
POSTw/ a body such as{'substack' : '/s/mysubstack', 'commenter' : '/u/jeff', 'comment' : '1234', 'tip' : '100'}...and then my own server could send back:[{'payto' : '/u/jeff', 'amt' : '50'}, {'payto' : '/s/erickuhn19', 'amt' : '20'}, {'payto' : '/u/anonporridge', 'amt' : '30'}]