From 9ab4ca9f2caa0c1a72c28f0bf33dbaf8c282d4de Mon Sep 17 00:00:00 2001 From: Lucian Mogosanu Date: Sat, 23 Mar 2019 14:08:16 +0200 Subject: [PATCH] drafts, 08a: Massage and moar text --- drafts/08a-feedbot-i.markdown | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/drafts/08a-feedbot-i.markdown b/drafts/08a-feedbot-i.markdown index e8a5f20..a956ffe 100644 --- a/drafts/08a-feedbot-i.markdown +++ b/drafts/08a-feedbot-i.markdown @@ -152,7 +152,7 @@ then sit back and relax. The disadvantage of doing it this way is that for two of the three parts, I'm pushing patches downstream of [ircbot][ircbot] that don't - use any ircbot. But let's imagine for a moment that I did it the + use any ircbot\*. But let's imagine for a moment that I did it the other way around -- now the reader can stand up a nice IRC bot implementing some commands that do what, more precisely? They call empty functions? They mock [the IRC interface][manual]? @@ -163,14 +163,22 @@ then sit back and relax. looks at new content and consumes it; and finally, after part three you have the whole thing. + \-\-\- + \* As an aside: notice how Feedbot imports the + [Feedparse][feedparse] code *ad litteram*? The separate V tree still + exists if you want to use it in your own thing, but otherwise that + item's been completely glued to [Feedbot][feedbot], and thus to + [Botworks][botworks]. This is no news, the same happened before with + [Eucrypt and MPI][eucrypt-mpi]. + [^2]: For the record: ~~~~ $ wc -l *.lisp - 301 feedbot.lisp + 307 feedbot.lisp 28 feedbot-utils.lisp 26 package.lisp - 355 total + 361 total $ grep '^ *;' *.lisp | wc -l 104 ~~~~ @@ -216,6 +224,8 @@ then sit back and relax. [trilemabot]: /posts/y05/078-trilemabot-ii.html [ircbot]: http://trinque.org/2016/08/10/ircbot-genesis/ [manual]: /posts/y05/081-feedbot-manual.html +[feedparse]: /posts/y05/087-feedparse.html +[eucrypt-mpi]: http://btcbase.org/log/2017-12-14#1751589 [feedbot-checker.vpatch]: TODO [feedbot-checker.vpatch.spyked.sig]: TODO [ffa-comments]: http://btcbase.org/log/2019-01-29#1890573 -- 1.7.10.4