Continuing the discussion from Hide Staff Notices from non-Staff:
(…discussion of Whispers, custom CSS, etc. ensues…)
My UX suggestion:
Continuing the discussion from Hide Staff Notices from non-Staff:
(…discussion of Whispers, custom CSS, etc. ensues…)
My UX suggestion:
This gets even more confused if you hold both the “Staff Notice” on posts and the “User Notes” on users in your head at the same time.
Users with trust level 4 can also add post-notices. So “staff” is not entirely accurate either. Maybe “(public) post notice” like the tag here at Meta would help. Then it’s also easier to find the Documentation topic
Do you mean TL4 can add Staff Notices? As I understand “post-notices”, those are the auto-generated new-user & returning-user messages. Even more confusion
Wait what? A post notice is created automatically, right? There’s no one who “adds” them?
So we have
I think staff and post notices are kind of the same feature. You can edit a “new user” post notice by clicking “change staff notice” and tl4 are also able to do that.
Also discussions about staff notices are tagged with post-notices
Whaaaaaaaaaaaaaaaat I never knew that. I have always thought these were distinct features.
I guess this topic proves that the terminology is indeed confusing…
That’s why I suggested “post notice” for all of them. Then we have the automatic “first-time” and “returning” user notices and the manual notices by TL4 and staff.
Yeah, let’s call them “call-outs” at the same time…
“similar to” implies they’re not the same, but the new user first post call out notice is simply an automatically created staff notice.
Just noting that this semantic confusion has popped up here before: