There you go @[email protected], [email protected] has finally appeared!
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).
Edited to remove hexbear@hexbear and add it to the filtered communities (and remove main@hexbear from filtered communities, which I'd mistakenly thought was their meta one).
The only available values are the ones that a) are provided by Lemmy's API, and b) picked on by the crawler at https://lemmyverse.net/. I don't think that includes visitor counts.
There's no point in a bot that posts any absolute values, as they're available from the platform itself. The idea with the bot is to track growth, and if there's no growth, well, there's no growth. I'll see if the bot can post less often for NSFW stuff, like once a week, as a daily post isn't usually producing much of anything worthwhile.
The 'trending communities bot' relies on another bot, at lemmyverse.net. That bot is a bit fragile, and hasn't worked for a week: see https://data.lemmyverse.net/
If you follow the GitHub link, you can see the process failing. I'll message the bot's author at some point, unless it automatically rights itself (it often does).
view more: next ›
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.