Looks like it, yeah (though peaks and troughs are to be expected). The next few days won’t show entirely accurate results, because the bot uses data provided by lemmyverse.net, and that’s site’s crawler has been failing

Well, there’s good news and bad news.

The good news is that Lemmy is now surrounding your spoilers with the expected Details and Summary tags, and moving the HR means PieFed is able to interpret the Markdown for both spoilers.

The bad news:
It turns out KBIN doesn’t understand Details/Summary tags (even though a browser on it own does, so that’s KBIN’s problem).
Neither PieFed, or KBIN, or MS Edge looking at raw HTML can properly deal with a list that starts at ‘0’.
Lemmy is no longer putting List tags around anything inside the spoilers. (so this post now looks worse on KBIN. Sorry about that KBIN users)

Firstly, sorry for any potential derailment. This is a comment about the Markdown used in your post (I wouldn’t normally mention it, but consider it fair game since this is a ‘Fediverse’ community).
The spec for lemmy’s spoiler format is colon-colon-colon-space-spoiler. If you miss out the space, then whilst other Lemmy instances can reconstitute the Markdown to see this post as intended, Lemmy itself doesn’t generate the correct HTML when sending it out over ActivityPub. This means that other Fediverse apps that just look at the HTML (e.g. Mastodon, KBIN) can’t render it properly.
Screenshot from kbin:

Also, if you add a horizontal rule without a blank line above it, Markdown generally interprets this as meaning that you want the text above it to be a heading. So anything that doesn’t have the full force of Lemmy’s Markdown processor that is currently trying to re-make the HTML from Markdown now has to deal with the ending triple colons having ‘h2’ tags around it.
Screenshot from piefed:

(apologies again for being off-topic)

Update: for LW, this behaviour stopped around about Friday 12th April. Not sure what changed, but at least the biggest instance isn’t doing it anymore.

I’ve been coerced into reporting it as bug in Lemmy itself - perhaps you could add your own observations here so I seem like less of a crank. Thanks.

We were typing at the same time, it seems. I’ve included more info in a comment above, showing that they were POST requests.

Also, the green terminal is outputting part of the body of for each request, to demonstrate. If they weren’t POST requests to /inbox, my server wouldn’t have even picked up them.

EDIT: by ‘server’ I mean the back-end one, the one nginx is reverse-proxying to.

They’ll all POST requests. I trimmed it out of the log for space, but the first 6 requests on the video looked like (nginx shows the data amount for GET, but not POST):

ip.address - - [07/Apr/2024:23:18:44 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"
ip.address- - [07/Apr/2024:23:18:44 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"
ip.address - - [07/Apr/2024:23:19:14 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"
ip.address - - [07/Apr/2024:23:19:14 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"
ip.address - - [07/Apr/2024:23:19:44 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"
ip.address - - [07/Apr/2024:23:19:44 +0000] "POST /inbox HTTP/1.1" 200 0 "-" "Lemmy/0.19.3; +https://lemmy.world"

If I was running Lemmy, every second line would say 400, from it rejecting it as a duplicate. In terms of bandwidth, every line represents a full JSON, so I guess it’s about 2K minimum for the standard cruft, plus however much for the actual contents of comment (the comment replying to this would’ve been 8K)

My server just took the requests and dumped the bodies out to a file, and then a script was outputting the object.id, object.type and object.actor into /tmp/demo.txt (which is another confirmation that they were POST requests, of course)

Yeah. It seems like the kind of community he’d post in. I think there was some drama between him and startrek.website, resulting in him or the admins deleting the account.

(same person on different account, just so I can preview what the table will look like)

Hmmm. This might not help you much. That community was launched on 2024-01-22, with a page full of posts, so by the time the crawler picked up on it, it was already at 501 subs, 23 posts.
It lost 15 posts on 2024-02-12 (Stamets?).
There’s data missing from 2024-02-26 - 2024-03-01 (this data is from the bot at !trendingcommunities@feddit.nl; I think those days are missing because I changed it from measuring Active Users Month (AUM) to Active Users Week (AUW)).
In terms of active users, the jump on 2024-03-04 is due to lemmy.world ‘upgrading’ to 0.19.3.

[data missing]

“active users” are defined by lemmy: posts + comments + votes

The bot is trying to catch upwards trend in the amount of active users. This tends to be communities that were dead or fairly dead, and then one or two posts got some engagement and spiked the number up.

In terms of absolute active numbers, there’s no need for a bot because lemmy can tell you that. The bigger communities tend to swing up and down in terms of activity (cancelling themselves out).

For example, tenforward@lemmy.world had 65 posts this week, but active users ended up pretty much where it was. The table below has 28 entries as the crawler at lemmyverse usually reports 4 times a day, so it’s for about 7 days:

Might be some rogue results for lemmy.world for a few days: for some communities there’s been a bit of lag (from using the old measurement for active growth to the new one, and/or for the crawler at lemmyverse to pick up on the change)

automod test

Yeah. Some weird community on lemmygrad that - like the ‘shit reactionaries say’ community there - is marked NSFW for some reason.

I don’t have my lemmynsfw login on me at me atm, so I can’t edit this post. But I’ll add ‘shit ultras say’ to the list of filters, so it won’t appear on these lists again.

I’ll automate this in the future. ‘now’ refers to when the crawler at lemmyverse got the info, so it trails a bit behind.

Raw numbers for Subscriber Growth (7 days ago to now)

101 firsthrust@lemmynsfw.com         
094 redhead@lemmynsfw.com         
082 amazingbum@lemmynsfw.com         
070 neonhairporn@lemmynsfw.com         
056 short_hair_babes@lemmynsfw.com         
055 pale@lemmynsfw.com         
054 eroticphoto@lemmynsfw.com         
049 public_flashing@lemmynsfw.com         
046 gooner_girls@lemmynsfw.com         
045 outdoor@lemmynsfw.com         
044 pronebutg@lemmynsfw.com         
044 petgirls@lemmynsfw.com         
043 nsfw@lemmynsfw.com         
043 clit@lemmynsfw.com         
042 booknymphs@lemmynsfw.com         
040 ebony@lemmynsfw.com         
037 groupsex@lemmynsfw.com         
036 research@lemmynsfw.com         
036 femabs@lemmynsfw.com         
036 euroteenmodels@lemmynsfw.com         
034 pialoof@lemmynsfw.com         
032 hentaigif@lemmynsfw.com         
022 eyecontact@lemmynsfw.com         
018 hotwomenincars@lemmynsfw.com         
008 lewderhentaicaptions@lemmynsfw.com         
003 hentai_irl@ani.social     

I’ll automate this in the future. ‘now’ refers to when the crawler at lemmyverse got the info, so it trails a bit behind.

Raw numbers for Active User Growth (7 days ago to now)

407 tinytitties@lemmynsfw.com         
336 asklemmynsfw@lemmynsfw.com         
236 desirablewomen@lemmynsfw.com         
227 xparadisio@lemmynsfw.com         
196 anklepanties@lemmynsfw.com         
191 ifyouhadtopickone@lemmynsfw.com         
188 nsfw_gifs@lemmynsfw.com         
171 juicyasians@lemmynsfw.com         
159 glasses@lemmynsfw.com         
153 yiff@lemmy.smeargle.fans       
146 rearpussy@lemmynsfw.com         
146 cameltoe@lemmynsfw.com         
126 lipsthatgrip@lemmynsfw.com         
115 ecchi@lemmynsfw.com         
111 plastt@lemmynsfw.com         
108 creampie@lemmynsfw.com         
107 hentai@lemmynsfw.com         
101 afrobull@lemmynsfw.com         
098 bodypaint@lemmynsfw.com         
095 beachfun@lemmynsfw.com         
094 masturbationhentai@lemmynsfw.com         
094 girlsmasturbating@lemmynsfw.com         
084 coffeegonewild@lemmynsfw.com         
081 fauxbait@lemmynsfw.com         
079 pegging@lemmynsfw.com         
077 frillysocks@lemmynsfw.com         
068 bustypetite@lemmynsfw.com         
067 deepthroat@lemmynsfw.com         
063 sensualbdsm@lemmynsfw.com         
059 hotandsexywives@lemmynsfw.com         
059 ftvgirls@lemmynsfw.com         
053 gonewild@lemmynsfw.com         
052 mommy@lemmynsfw.com         
050 fanslygirls@lemmynsfw.com         
049 bigasses@lemmynsfw.com         
048 misogyny_xxx@lemmynsfw.com         
048 gentlefemdom@lemmynsfw.com         
048 erotic_photography@lemmynsfw.com         
047 pornstars@lemmynsfw.com         
046 buttplug@lemmynsfw.com         
045 lewdanimegirls@lemmynsfw.com         
043 curvy@lemmynsfw.com         
040 nudedudes@lemmynsfw.com         
040 humiliation@lemmynsfw.com         
038 shibari@lemmynsfw.com         
037 cuminmouth@lemmynsfw.com         
036 blindfold@lemmynsfw.com         
035 asiancumsluts@lemmynsfw.com         
034 futanari@lemmynsfw.com         
031 massivecock@lemmynsfw.com         
031 fitgirls@lemmynsfw.com         
030 skinnytail@lemmynsfw.com         
028 angelawhite@lemmynsfw.com         
025 azurlaner34@lemmynsfw.com         
023 bondage@lemmynsfw.com         
021 blowjob@lemmynsfw.com         
020 domestic_discipline@lemmynsfw.com         
018 orgasm_denial@lemmynsfw.com         
017 wooden_horse@lemmynsfw.com         
017 facial@lemmynsfw.com         
015 ass@lemmynsfw.com         
011 tentaclehentai@lemmynsfw.com         
008 spanking@lemmynsfw.com         

Hi

Pls check how much traffic you’re now sending out for every activity - my server is recording that everything from lemmy.world is being 4 times (e.g. 1 Upvote is sent 4 times to every instance that has a subscriber. Those instances will reject 3 of them for being dupes, but it’s still a lot to be sending out).

lemmy.ca had a problem where they were sending everything 3 times, and it was because they were running 3 containers, and they all had the same index number, so maybe it’s that.

Thanks.

I could add something as a comment to the post?

As for ‘the yiff community of smeagle fans’ - I don’t know what any of those words mean, but it’s fed by a enthusiast bot, so that’s why there’s so many posts. The community seems to have calmed down a bit in terms of activity now though (this data comes from a crawler, so it’s always a bit behind)

I’ve been using users_active_month for Active Users but it doesn’t seem to really update often enough (e.g. !badrealestate@feddit.uk had some activity in the 3rd week of February, but the UAM stat didn’t change until 1st of March). I tried running the bot with users_active_day, but that’s bit too dynamic - there’d be days will very few entries on if I used that. So I’ve compromised on users_active_week … we’ll see how that works out.

Suggestions are very welcome (it’s still a work in progress).

The way it currently works is that raw percentage change is then mulitplied by the actual change and then divided by 100.
So, for small community:
10 => 22
(22-10)/10 * 100 = 120% change
22-10 = 12 actual change
(120*12)/100 = 14.4% change

For a big community:
10000 => 10380
(10380-10000)/10000 * 100 = 3.8% change
10380-10000 = 380 actual change
(3.8*380)/100 = 14.44% change

This weights the changes by community sizes, so - for these examples - a big community growing by 380 is the same as a small community growing by 12, meaning that the final list is hopefully a mix of both.