From 2767bc0373c127880710601aefd4b71215fe3efc Mon Sep 17 00:00:00 2001 From: Ian Kelling Date: Tue, 30 Aug 2016 19:17:16 -0700 Subject: [PATCH] better readme --- README | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/README b/README index 4cbefb7..1ba27af 100644 --- a/README +++ b/README @@ -24,20 +24,22 @@ directories are managed separately, mostly by rsyncing them. Only the latest version of resume is kept in the resume branch which gets rebased on master. -./build.rb does have any dependencies, but it's not a generalized site -generator, it has some content files specific to my site that it expects. +./build.rb is not a generalized site generator, it has some content +files specific to my site that it expects. Dates in the blog directory can be generated with date +%F * Comments -New comments are stored in a sqlite database. Ones that are not -moderated for spam etc, are stored to disk for checkin on the next run -of build.rb. get-comments, set-comments, and iank-mod.el are for -moderating new comments. With one emacs command, you get a buffer of the -new comments, with keybinds to mark them for publishing, moderatation, -banning, and execute changes. +New comments are stored in a sqlite database. There is a system for +moderating, rate limiting, and handling comments based on previously +seen ips. See _site/cgi/comment. Ones that are not moderated for spam +etc, are stored to disk for checkin on the next run of build.rb. +get-comments, set-comments, and iank-mod.el are for moderating new +comments. With one emacs command, you get a buffer of the new comments, +with keybinds to mark them for publishing, moderatation, banning, and +execute changes. * Inspirations -- 2.30.2