Does anyone know why nodeinfo's localPosts value might go backwards?
Does anyone know why nodeinfo's localPosts value might go backwards?
Does anyone know why nodeinfo's localPosts value might go backwards?
I've noticed it happen with both hachyderm.io and noagendasocial.com but I haven't been tracking it for long so it might happen to others (and not just mastodon). It doesn't appear to be a field rollover. Also I don't know if it happens all at once or if it is incremental. I've just noticed a drop between two queries a number of hours apart. @feditips @asklemmy @nova @adam@noagendasocial.com
If it's a small drop, people could just be deleting posts, or have self-expiring posts.
@markrprior@ohai.social @asklemmy@lemmy.ml @nova@hachyderm.io
@danjones000 @asklemmy @nova I’ve seen some drop a significant amount, losing 1000 from 3000, on some instances. The small drops could be deletion and I hadn’t considered expiry. I don’t think either of these should influence that counter though as that would make it next to useless for stats gathering.
From a quick look at the code in particular this, I would guess the cache being emptied and not populated yet.
On another note, I'm unsure what it counts. Do Announce activities count as a status?