mwv
(Michael Wood-Vasey)
February 23, 2022, 7:09pm
#1
Please turn off the “It’s been a while…” type marking of posts. It’s unfriendly and discouraging. E.g., on
In June 2021, the Vera C. Rubin Observatory announced an opportunity for members of the US and Chilean science community to join the Rubin Observatory Rubin Observatory System Integration, Test, and Commissioning (SIT-Com) team and contribute to an efficient and successful transition to Operations.
In October 2021, 18 groups submitted full Letters of Interest in response to the Announcement of Opportunity for Community Engagement in Rubin Observatory Commissioning (SITCOMTN-010 ).
In January 20…
in between the title and the key part of posts Community inserts:
“It’s been a while since we’ve seen bechtol — their last post was 5 months ago.”
[This happens in the full post, not the preview that gets inserted immediately above here in this current post.]
This message seems to imply that bechtol
has done something wrong and doesn’t add any useful information to the post.
jsick
(Jonathan Sick)
February 23, 2022, 8:02pm
#2
I’ll see what I can do. Thanks!
I agree with this request, thanks @mwv !
@jsick looks like a function that can be changed in the theme?
To encourage kindness towards users who are posting for the first time or may not have posted in a while we’ve created a new feature that calls special attention to these new/returning users. These banners are visible to other users, but not the...
Reading time: 7 mins 🕑
Likes: 298 ❤
jsick
(Jonathan Sick)
February 23, 2022, 8:15pm
#5
For now, I’ve just changed the returning period to 15 years. This Discourse feature is great in a lot of forums, but you’re right that it doesn’t work so well for Rubin at the moment.
It seems there’s some caching that may prevent the change from being visible on existing posts immediately. If it doesn’t clear in a day or two I’ll release a new theme update.
1 Like
mwv
(Michael Wood-Vasey)
March 1, 2022, 5:42pm
#7
The “It’s been a while…” message is still visible on the example post for this thread. @jsick could you take another look on how to clear this?