Can you be more specific? quote the relevant text?
But that said, there’s an important nuance between “learnability” & usability. Generally, for things that expert users are using regularly, those users will take extra time to figure out how it works.
The watching vs. tracking debate is a more “expert” option for Discourse users, IMHO. Therefore, I wouldn’t prioritize making it as learnable (intuitive terms) over making it easy to use the various options (which I think it is now, TBH).
Smart thinking for reference on this issue:
The use of the word “notifications” in the footer text is my main concern here. However, the fact that the Preferences text does not match the category notification level selector text is also odd.
Footer text:
You will receive notifications because you are tracking this topic.
Preferences text:
You will automatically track all topics in these categories. A count of new posts will appear next to the topic.
Notification level selector (category):
You will automatically track all topics in these categories. You will be notified if someone mentions your @name or replies to you, and a count of new replies will be shown.
Notification level selector (topic):
A count of new replies will be shown for this topic. You will be notified if someone mentions your @name or replies to you.
So your complaint is about the footer text?
I’m so very very tired of arguing over one or two words. I feel like there are literally hundreds of other things I could be spending time on that would actually drive this project forward and that is not one of them.
Extremely frustrated right now. 
I think the reason why such a table doesn’t exist is that there are so many dimensions to take care of that a flow chart would probably be the only way to depict all possible scenarios. But I leave that to someone else. I have made an attempt at a table below. It focuses on what happens when two different events occur (a new topic is created and a new reply is created) based on the settings that apply to that event (i.e. category notification settings, which, in the case of replies, can be overwritten by topic settings). The table ignores other events (@-mentions, replies to own posts, likes, or personal messages, …)
I am not sure if the table is correct as it is, so I am making this post a wiki for anyone to correct or amend. Please explain your changes briefly underneath the table.
| user menu notification |
new replies count |
"new" indicator |
|||
|---|---|---|---|---|---|
| new topic | watching | yes | yes | n/a | yes |
| tracking | no | no | n/a | yes | |
| watching first post | yes | yes | n/a | yes | |
| normal | no | no | n/a | yes, if newness definition applies |
|
| muted | no | no | n/a | no (?) | |
| new reply | watching | yes | yes | yes | n/a |
| tracking | no | no | yes | n/a | |
| normal | no | no | no | n/a | |
| muted | no | no | no | n/a |

…
… …
Now I’m worried: 
Should I be “watching” for the second coming of Jesus Christ or should I be “tracking”.
Thank goodness for the certainty and assurance of good theology. 
Just so you know that this is not a serious reply in this topic.
When you look down and see one set of footprints, that is where Jesus was carrying you. Good luck tracking those footprints!
Oooh, I’ve seen that poster. A great follow-up! 
I beg to differ.
The only way I know my dad jokes achieved perfection is when there is complete silence in the team chat channel, folllowed by a slow explanation from me, followed by by a loud team groan.
虽然晚了几年,但我还是想建议你可以停止关注……我是说跟踪这个话题? ![]()
严肃地说:我之所以会看到这个,是因为我和我的学生们也觉得这个措辞令人困惑。
重要的是邮件通知是/否,因为它们可能非常烦人。
其次是菜单通知是/否,但这不那么烦人。
我的一点看法。
这是完全不同的通知推理方式,根本不在 Discourse 的基本设计中。我们有时会发送“跟踪”邮件,我们有时会发送“关注”邮件。邮件发送的推理在用户偏好设置中有所涵盖。
分离邮件发送会打开一个巨大的潘多拉魔盒。你的学生真的想要一种模式,即他们永远不会收到关于特定主题的邮件(但会在 UI 中收到通知),却会定期收到关于其他主题的邮件吗?
我赞赏该模型提供的灵活性。通过使用诸如“关注”、“跟踪”等基于意图的抽象,您在实现方面具有灵活性。
只是说对于普通用户来说,用户体验/命名令人困惑。
在我正在设置的下一个 Discourse 论坛中,我将尝试以一种截然不同的方式来利用 5 个跟踪级别的灵活性。如果您有兴趣,我可以对此进行一些扩展。
嗯。你的问题让我思考。
他们最好收到更少的邮件通知,而不是更多。因为否则他们很快就会把我的邮件当作垃圾邮件,再也收不到任何消息了。
在我们的例子中:我认为他们主要应该在以下情况下收到邮件:
- 老师发送的群组消息
- 直接发给他们的私信
- 当他们在某个话题中被直接回复时
然后,他们可以根据自己的喜好选择接收任何话题/类别的邮件。
但说实话,我认为这已经可以配置了。只是可能需要更直观的方式来让学生访问通知设置。
我不知道Sam是否有兴趣,但我有 ![]()