Communities only feature in one or the other. Active User Growth is prioritised over Subscriber Growth, but 196's AU growth dropped today (it went from 0 to 4k to 7k over the week, but it's on about 6.5k now)
There's nothing like that that's preventing it being listed.
The community was started 2025-01-19 17:37:24 - less than 4 days ago as I'm writing this. The bot gets it's data from a crawler, so there's a bit of lag, but not much - it's got about 3 days of data on it.
It needs 7 days, because it works by taking a rolling average of the previous 7 days. You'd see some crazy results if it started publishing results earlier. Doubly so because that community hasn't really grown organically, and has benefitted a lot from Fediverse drama.
I can see 'NodeBB/4.x' in my NGINX log, when this forum Announced this post, and when it's retrieved my user details.
It's just that though, not the +website that everything else seems to have.
Users per day is a bit too volatile - it's showing 2/day atm - so the bot uses Users per Week. Also, the data is from a crawler, so there's a bit of lag, and it can end up picking up on activity that's already been and gone.
nearly there
A few more to reach thread cut off
Apologies to anyone browsing by 'New Comments', but I'm using this old post for a bit of cheeky testing in production.
Paging myself: @[email protected]
Paging another local user: @[email protected]
Paging a remote user on a different instance: @[email protected]
Paging a remote user on this instance: @[email protected]
Paging the OP of this post: @[email protected]
This was linked to in a comment from the source of this post: https://mastodon.social/@Hbomberguy/146524
It'll feature naturally in a bit (the bot tries to measure trends over the previous 7 days, and that community was only created a few days ago).
view more: next ›
This bot runs on a SBC that sits under my telly, and the SD-Card in it has decided to go read-only. I'm a bit skint atm, so it might be a while before it updates again.