X-Git-Url: https://iankelling.org/git/?p=iankelling.org;a=blobdiff_plain;f=README;h=fafdc6463065d3cc40701fb63e0047b09330de27;hp=017260f995a921ece6ab5513f77b85ef26ffa528;hb=34165b546bf7469aeb0e5bd6fdf3df6debdbbe3d;hpb=d0a5b73d2a275bfff5957961f2360df8966bee22

diff --git a/README b/README
index 017260f..fafdc64 100644
--- a/README
+++ b/README
@@ -3,6 +3,8 @@ Content and automated setup of iankelling.org
 
 * Setup
 
+I use a submodule, so git clone --recursive.
+
 setup.sh sets up apache and gitweb
 build.rb does static site generation
 
@@ -14,6 +16,8 @@ https://iankelling.org/git/?p=distro-functions;a=summary
 And some programs need to be in PATH:
 https://iankelling.org/git/?p=basic-https-conf;a=summary
 https://sallymae.club/git/?p=acme-tiny-wrapper;a=summary
+chost from
+https://iankelling.org/git/?p=fai;a=summary
 
 This repo does not include the repos under /git.  In my own version, under /git are links to the .git dirs of the respective repos under the
 hardcoded directory in setup.sh: gitroot=/a/bin/githtml. These
@@ -22,27 +26,30 @@ 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
+* Other sites that are in some way interesting:
 
 http://blog.zorinaq.com/release-of-hablog-and-new-design/?
 https://mjg59.dreamwidth.org/
 http://bettermotherfuckingwebsite.com
 https://eduardoboucas.com/blog/2015/05/11/rethinking-the-commenting-system-for-my-jekyll-site.html
+https://chris-lamb.co.uk/posts/concorde
 
 * License
 
@@ -51,6 +58,3 @@ GPLv2 or later unless stated otherwise. I'd use gplv3 or agpl, but it's
 simpler to use the same license as the gitweb javascript.
 
 The elisp is GPLv3 because emacs is.
-
-The opensans font is Apache2 licensed, from google fonts,
-the license is included in the LICENSE file.