-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Matrix bridge for new comment notifications. #26
Comments
New comments view: https://{instance}/c/{community}?dataType=Comment&sort=New |
Oh... Just realised that github messed with my message. Will fix that now. |
I think that the task for this should run at a much lower frequency, maybe every 3 or 6 hours. The comments are much easier to get and if one post got traction then it would be better to have as much bundled as we can instead of having a notification every 30 minutes for a few hours straight. The idea is just to not miss the comments in lower activity communities unlike with posts where we want to react asap in case it breaks community rules before it gets traction and makes it harder to go against the flow. Or simply in case of spam. Personally I lean towards 6 hours or even 12 hours because I don't think it's that relevant to get up to 4 notifications for comments specifically. |
Adding to this, I think a notification for comments under bot posts would be useful (replies to posts posted by x account). |
OK, looks like there's an API for mentions and comment replies. In 1.0 there's a combined inbox feature |
For that one I think that instead of having a notification for each comment separately having it grouped and linking to community's new comments view would be much better. Something like:
5 new comments in [community] <link with comment view with new sort here> <date>
I also believe that some communities should be blacklisted altogether if they're active by default. Potentially accounts too like the directory bots for example. Ignoring bot accounts may be simpler though.
Thoughts?
The text was updated successfully, but these errors were encountered: