Hmm no the anonymization code path would need to remove it anonymization time. Unless this is super super easy I would ignore it for now. So tiny. Also this is still correct in terms of the historical record, that is indeed the first time that user posted, so I am not even convinced this would be a useful thing to do.
I’m not able to reproduce this, seems to be fixed since this commit:
https://github.com/discourse/discourse/commit/476d0050ab80b2dfcaee6368c529f5094f14d79a
Isn’t there a similar feature where admins can leave banner notes above suspicious posts? Who can view the “admin warning” banners?
From community perspective is veeeeery useful Thanks for that
Just a quick comment… Post notice for first-time user is great, but I wonder why is it shown in PM? If the purpose is to get wider audience to welcome user, it should only be displayed in public topics… Posts in PM should be ignored when evaluating first post for a user if possible (haven’t seen the code so maybe it is impractical for implementation).
See @awesomerobot’s OP.
Everyone sees the post notice except for the new or returning user. If you wish to hide the notices globally or just in certain topics, please start at the first post and read down. Additional posts explain how to do this.
I don’t think you have understood my point.
I love displaying post notices because they help engagement.
The problem is that if first user’s post is in PM, first-time post notice is displayed there (and only recipient sees it).
Much better would be to ignore PMs for this purpose and display first-time post notice in first public post. Then it gets to much wider audience and first time poster gets welcome from many members.
The point is that some people think that even in a pm it’s useful to know if someone hasn’t posted in a long time, but if you think those messages are inappropriate for PMs then you can add css to hide them.
EDIT:
Oh! Sorry. So if they send a PM that counts as their first post in a long time, so their next public post isn’t counted as a first post in a long time. Sorry. I missed that too.
I see. It seems a bit like an edge case, but if I’m guessing at how the code works then it should be a fairly small tweak to not look at PMs when doing that how-long-it’s-been check.
Understand now.
Thanks… if the change is not much hassle, then it would be really great!
For me it is not the edge case because I try to approach every member with personal welcome PM
No, this won’t be happening, the current behavior is very intentional. Your other option is CSS modifications, which you can easily make yourself as @pfaffman noted.
Is it possible to send email to such users who post for the first time?? Like there’s this notice of a user posting for a first time. Is it possible that we can send him email for his first post?
You could send a PM (which would email them if they’re not onsite). What are you actually trying to achieve though?
Should this at least be changed for tutorial PM?
Not many new users start the tutorial as the very first thing (actually, not many do at all), but those who do have the new user notice posted inside a tutorial, where no one will ever see it.
That is an excellent point, we should prevent it in that case, I agree.
It’s not only the tutorials. Private messages in general shouldn’t be candidates to display this notice.
Example:
Our new forum is still very small and (following Discourse’s advice somewhere) we are welcoming every new user with a personal message. It is not unusual that the first post of a new user will be a reply to the lovely message we send them. And their reply shows the “This is the first time…” notice. This is means that whenever they comment publicly for the first time, no notice will identify them as new contributors.
Maybe edit the welcome message with a notice, “Please do not reply to this message. No one will see this.”
Hi Jeff,
Are there any plans for the new user notices not appearing in PMs. Will this be going forward?
Thanks
This appears to be split in to new user notice tl
and returning user notice tl
now?
Yes, thanks for mentioning it. I’ve updated the original post.