New "flags" option in the [markdown] section to customize
Misaka's Markdown HTML rendering.
By default, no flags are set.
```
[markup]
flags = skip-html, escape, hard-wrap
```
Update CHANGES.rst and add the section to the sample
isso.conf and isso-dev.conf
* Minor text improvements to faq.rst
* Fixed minor mistake to faq.rst
* Minor grammar fixes to troubleshooting.rst
* Minor grammar improvements to quickstart.rst
* Minor text changes to install.rst
* Improved text in multiple-sites.rst
* Misspelled word
* Minor text changes
Automatically approve comments by an email address if that address has
had a comment approved within the last 6 months. No ownership verification
is done on the entered email address. This means that if someone is able
to guess correctly the email address used by a previously approved author,
they will be able to have their new comment auto-approved.
There is a header describing `data-isso-reply-notifications` but it is not in the initial data attributes examples. I assume the initial list is meant to be exhaustive? I overlooked this setting on my initial read through the docs because it wasn't there, so I thought it would be helpful to add.
Merging @pellenilsson reply notification PR
* Added reply notification for commenter
* Removed debug info
* Bugfix
* Add notification column to database if needed
* Make SMTP connections thread safe
* Include link to comment in email notifications
* Implement opt-out for email notifications
* Fix faulty check for parent comment
* Support notifications also for replies
* Don't send notification when someone responds to his/her own comment
* Make unsubscribe work with notifications for replies
* Correct hash in 'unsubscribe' API example
* Introduce public-endpoint setting
* Fix whitespace issue
* Postpone notifications to users until comment has been approved by moderator
* New setting general.reply-notifications
* Add client-side configuration setting reply-notifications
* Documentation for reply notifications
On server-side, this can be enabled by providing a base URL to use to
build the full URL. Limit also becomes configurable. On client-side,
we need to add a switch to know whatever or not the additional link
can be displayed.
Jelmer Vernooij