use safe markdown for comments to prevent xss

[iankelling.org] / README

diff --git a/README b/README
index 4cbefb7bfca732e07dbb4000678baa84aec05763..1ba27afd1e5168d2d9847771e6ca2489d3f874e7 100644 (file)
--- 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.
 
 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
 
 
 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
 
 
 * Inspirations