Dmitry Verkhoturov

@akellbl4 since auth packages support checking the user with status code 200, let's switch to using it on the frontend side? It wouldn't hurt, and the 401 unauthorised error in...

I'll disable removing the `twitter-tweet` class on the backend as it seems to be a requirement.

I've added a class to the whitelist. What is left now is to enable adding the Twitter styling out of the box and retweet and likes info via Twitter JS...

Nobody has reported such issues yet. JetBrains has a big user base for their comments and has email auth enabled in their Remark42 comments, but I have yet to hear...

It works in the latest stable version, resolving.

I see that the issues mentioned here are fixed, resolving this issue. Feel free to comment if I'm wrong.

The situation seems to be resolved, and current issues with using another domain are described in [the documentation](https://remark42.com/docs/manuals/separate-domain/) (and all related to auth). Resolving this issue, feel free to comment...

Two years later, I see that people often create issues about discussion topics. @umputun I propose adding a non-printable comment to the issue template, which would clarify when a person...

We have yet to receive new reports after the v1.5 release, resolving this issue. Please comment if I'm wrong and you still see it.

We should not fix it on our side if the library doesn't support it: we then open a can of worms by trying to support the undocumented hotkey feature for...