Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
That could get noisy if it were the default behavior. But maybe we should consider, instead, an option where you can choose to be notified of new activity on a specific post. We already have an o...
Answer
#1: Initial revision
by
Monica Cellio
·
2023-10-15T03:24:08Z (about 1 year ago)
That could get noisy if it were the default behavior. But maybe we should consider, instead, an option where you can choose to be notified of new activity on a specific post. We already have an option to follow new comment threads on a post; should we generalize that to following new activity, which would include new comment threads, edits, votes, and, for questions, new answers? (This wouldn't include new comments in threads; for that, you can follow the threads separately, or not.) Would that be too noisy? I don't think we want a bunch of individual controls for following edits, new answers, votes, and new threads separately, but maybe these shouldn't all be lumped together. Are comment threads different and should remain separate? Is there some other way to logically slice and dice activity? Can we let people sign up for the notifications they want without over-complicating the user interface?