Congratulations on your system! > Must be manually curated and posted Well sure but you can make that semi-automated using a TUI/WebUI to filter out obvious s

Congratulations on your system! > Must be manually curated and posted Well sure but you can make that semi-automated using a TUI/WebUI to filter out obvious spam then review comments individually before pushing a batch to your publishing pipeline. For example, by importing the maildir entries into your SSG directory, or by forwarding the selected comments to a localhost address not reachable from the outside where the maildir will be automatically picked up by a script. > No notifications for me i don't have notifications of email but that's a feature not a bug. i could set up some easily on my smartphone. and you could do the same, or you could use something like sendxmpp to keep you updated on a chat account. > No “built-in” reply functionality Why not? Just assign every article a uniqueID, and every approved message a uniqueID based on a hash of publishing date and commenter email and use a mailto URI for the reply link where subject = "articleID-commentID" and body = explanation to not change the message title and about privacy policy. That's how email-based bugtracking systems like debbugs work to keep track of relations between messages. You could even make opt-in for receiving (approved) replies via email maybe by adding "Can't wait to hear from you!" at the end of the body... I can't find the source right now but if you ask cmccabe from rawtext.club (can also be found on other tildeverse IRC chans) he's got a nice/flexible email treatment pipeline using simple scripts that could be very well adapted to this usecase. Demo? Send "pepperoni" subject to frisbee+pizza@rawtext.club ;-) ;-)