# Received 'regular' badge from Discourse

**URL:** <https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282>\
**Category:** Meta\
**Tags:** discourse\
**Created:** [27 May 2024 05:40 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282 "2024-05-27T05:40:34Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [27 May 2024 05:40 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/1 "2024-05-27T05:40:34Z")

</div>

Hi folks,,

I received this badge from Discourse:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/a/fae00709d1280168d02de4ad9478819603c26dff.png)

I might be completely mistaken (!!), but I think I received such a badge years ago already...

If that would be the case, does this mean perhaps that Discourse takes away our badges as soon as we have a period of lower activty? Which would be mathematically correct, but quite ungrateful imho. In that case Discourse would become an _asocial media platform_...

My right-hand man ChatGpt tells me that this is not the case:

> once a badge is granted, it is not typically removed from a user’s profile

But it wouldn't be the first time that he fooled me ...

Thanks from a novice community member 😋  
Bart

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [27 May 2024 06:33 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/2 "2024-05-27T06:33:36Z")

</div>

My Regular got stripped from me the other week.

Personally I find it silly, especially when I have been given it a couple of times.

It’s like being punished, for being busy, that you can’t help the community as much as you have clearly been identified too!

Anyway, I find it annoying - and actually off putting  
And I agree - it is ungrateful for those that hang here often, but become busy for a period.

Like I say - it puts me off.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [27 May 2024 07:44 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/3 "2024-05-27T07:44:35Z")

</div>

Parameter can be changed 🙂

Personally, I knew I was going to lose it because I had a big month-long rush. But as Marcus said, we can be busy personally and still be present when we are mentioned, for example.

> **[How many TL3 users do you have? Do the TL3 requirements really make sense?](https://meta.discourse.org/t/how-many-tl3-users-do-you-have-do-the-tl3-requirements-really-make-sense/255503/23)**
>
> Our site is 10+ years old and recently imported to Discourse. There are a lot of inactive account and many people who exclusively lurk which is why TL1 is so high Non-default settings: (Default 10) (Default 12) Maybe the extra duration...

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [27 May 2024 07:56 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/4 "2024-05-27T07:56:27Z")

</div>

For me "badges" fall somewhere between patronising like a primary school gold star and creepy like adverts based on my location and search history.  
Except I can turn those off.

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [27 May 2024 09:00 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/5 "2024-05-27T09:00:41Z")

</div>

@BartButenaers - Discourse Trust Level 3 (also known as 'Regular') for users, is established on a rolling 100 day period, so if you dip below the necessary requirements, the badge (level) is reduced from 'Regular' to 'Member'.

So to get to trust level 3, in the last 100 days…

- Must have visited at least **50%** of days
- Must have replied to at least **10** different non-PM topics
- Of topics created in the last 100 days, must have viewed **25%** (capped at 500)
- Of posts created in the last 100 days, must have read **25%** (capped at 20k)
- Must have received **20** likes, and given **30** likes.\*
- Must not have received more than 5 spam or offensive flags (with unique posts and unique users for each, confirmed by a moderator)
- Must not have been suspended or silenced in the last 6 months

Discourse say;  
_"All of the above criteria must be true to achieve trust level 3. Furthermore, unlike other trust levels, you can lose trust level 3 status . If you dip below these requirements in the last 100 days, you will be demoted back to Member. However, in order to avoid constant promotion/demotion situations, there is a 2-week grace period immediately after gaining Trust Level 3 during which you will not be demoted."_

> **[Understanding Discourse Trust Levels](https://blog.discourse.org/2018/06/understanding-discourse-trust-levels/#trust-level-3--regular)**
>
> The user trust system is a fundamental cornerstone of Discourse. Trust levels are a way of…

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [27 May 2024 10:05 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/6 "2024-05-27T10:05:58Z")

</div>

I suggest extending this limit (100 days) because it is quite short if we have a little period of inactivity.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [27 May 2024 10:15 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/7 "2024-05-27T10:15:59Z")

</div>

I've now set it to 200 days minimum... so hopefully won't be so "aggressive".  
Also if anyone feels they have been unfairly dinged let me know and I can manually bump and lock their level.

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [27 May 2024 10:23 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/8 "2024-05-27T10:23:21Z")

</div>

Thanks all for illuminating me!

So thank god it is a pure math issue from some algorithm.  
And not a community driven decision targetted to me personally 🤣

P.S. My belly tells me that I will get more response now on my previous sentence, compared to when I ask volunteers to test a new node 😋

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [27 May 2024 11:01 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/9 "2024-05-27T11:01:54Z")

</div>

> [@BartButenaers](#):
>
> So thank god it is a pure math issue

Not just pure maths, I thought @marcus-j-davies might of been removed for the spamming in the lounge. JK

> [@](#):
>
> Must not have received more than 5 spam

But then read it must be confirmed by Moderator.

> [@](#):
>
> (with unique posts and unique users for each, confirmed by a moderator)

> [@BartButenaers](#):
>
> My belly tells me that I will get more response now on my previous sentence, compared to when I ask volunteers to test a new node

OK Bartradamus

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [27 May 2024 11:05 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/10 "2024-05-27T11:05:37Z")

</div>

> [@E1cid](#):
>
> Not just pure maths, I thought @marcus-j-davies might of been removed for the spamming in the lounge. JK

Looks like I better catchup on missed opportunities 😉

---

<div class="post-metadata">

**Author:** ![Sean-McG](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sean-mcg/32/54677_2.png) [@Sean-McG](https://discourse.nodered.org/u/Sean-McG)\
**Post date:** [28 May 2024 01:14 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/11 "2024-05-28T01:14:39Z")

</div>

> [@Paul-Reed](#):
>
> Of posts created in the last 100 days, must have read **25%** (capped at 20k)

20K cap seems a bit high ?

For example it (feels like) 50% of messages are related to dashboard 2 at the moment, which I don't currently have time to experiment with, so I'm unlikely to read them all.

---

<div class="post-metadata">

**Author:** ![kevinGodell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kevingodell/32/27040_2.png) [@kevinGodell](https://discourse.nodered.org/u/kevinGodell)\
**Post date:** [28 May 2024 02:46 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/12 "2024-05-28T02:46:25Z")

</div>

@BartButenaers, I am awarding you with a very special badge.  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/5/e55c4b276c46d53f4e2d232b892f382f468bac88.jpeg)

---

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [28 May 2024 08:02 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/13 "2024-05-28T08:02:14Z")

</div>

> [@Sean-McG](#):
>
> 20K cap seems a bit high ?

Maybe, but the Node-RED forum has generated 9,720 posts in the past 100 days, and the current 'Level 3' requirement is to read 25% (which is discourse's default setting).  
So 9,720 X 25% = 2430, divided by 100 days = a minimum average of 25 posts to be read per day.

If you scan through a single topic, you can quickly reach that figure.

> [@Sean-McG](#):
>
> 50% of messages are related to dashboard 2 at the moment, which I don't currently have time to experiment with, so I'm unlikely to read them all.

However, in the past 100 days, you have read 5,483 posts , which is almost double the requirement!

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 May 2024 08:14 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/14 "2024-05-28T08:14:38Z")

</div>

I've reduced the view/read percentage to 10% for Level 3.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 August 2024 08:15 UTC](https://discourse.nodered.org/t/received-regular-badge-from-discourse/88282/15 "2024-08-26T08:15:06Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
