Dmitry Verkhoturov

The reason is just separation of frontend and backend: there is a separate endpoint on the backend to verify an email but it's called from the frontend, the same way...

After #573 only frontend part left to be done (separate page to handle token submission to backend and then redirect a user back to site). In order to enable link...

Things I thought of for PR template: - [ ] Readme updated if these changes add new functionality or change existing one - [ ] Parameters section in the doc...

I would agree on the issue template as I've never seen anything useful: experienced reporters will write everything you expect to know in the first message, and you'll need to...

The information which was discussed somewhere but was not written down yet: this is a tricky issue because of security precautions, as we don't want to auto-deploy just everything we...

@esvyridov feel free to, but please create your own PR for that.

Frontend behaviour currently is not helpful for someone trying to set up Remark42 for the first time. I would insist on showing some proper message about the lack of providers...

The backend doesn't fail in such a scenario as it's a valid case to run it in such a scenario. However, the front is broken in that case and doesn't...

As we won't get rid of our API anyway, I think it's worth trying to implement that on a separate endpoint as an experiment. I have a lot of concerns...

> I know there is the "Subscribe by email", however I believe that is something completely different (ie: a user wants notifications for all messages regardless who posted to what...