8000 Self reply and notifications for disallowed comments · Issue #446 · isso-comments/isso · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Self reply and notifications for disallowed comments #446
Open
@wastedepository

Description

@wastedepository

I have a couple feature requests related to the spam protection rules.

Currently, there is no notification given to the user when they attempt to Submit a post but the post is rejected due to spam protection rules. These rules might apply due to the values of the ratelimit, direct-reply, and reply-to-self server settings. When a post is rejected, I would expect Isso to produce a prompt saying "Sorry, you have exceeded the maximum number of allows posts per minute" or "You cannot respond to your own posts while they are still editable", or some other appropriate message. But Isso doesn't provide any feedback on why the user is not allowed to make a post. Is it possible to add this kind of feedback?

There is one particularly problematic situation, related to the reply-to-self setting. The way it works now, say user A posts a direct reply to the thread, and user B replies to user A. If reply-to-self=true, user A is then blocked from replying to user B until 15 minutes (max-age) after user A's initial post was made. The reason for this is that comments in Isso are only 2 layers deep: there are "direct reply" comments, and replies to "direct replies", and that is all. As a result, A's response to B is considered a response to A's original comment, and violates the reply-to-self spam protection. The ideal solution for this would be to subvert the reply-to-self rules in case the user is replying to another comment that is a reply to the original user's comment. A more complicated alternative would be allowing an infinite number of layers of replies-to-replies (example: reddit's commenting system), rather than just 2 layers. As a temporary solution, an anti-spam notification to tell the user what is going on would still be a partial solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0