Fediverse

27910 readers

1 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago

MODERATORS

[email protected]

Lemmyverse historical data? (data.lemmyverse.net)

submitted 7 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

I am interested in checking out the historical growth of a particular community. Lemmy Explorer crawls for data about the Lemmyverse every 24 hours or something, and that data is made available on their website. But I can only find where to download the latest data. Is there somewhere that I can find historical data? Does Lemmy Explorer archive these anywhere, or does it just overwrite the previous data each time it crawls?

you are viewing a single comment's thread
view the rest of the comments

[–] testAccount 1 points 7 months ago (1 children)

Mostly because Lemmy has a hard time keeping up with the federation

https://github.com/LemmyNet/lemmy/issues/4529

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Oh, right. The chat on GitHub is over my head, but I would have thought that solving the problem of instances sending every activity 2 or 3 times would help with that, since even rejecting something as a duplicate must eat up some time.

[–] testAccount 1 points 7 months ago

Yes but now it must wait for acknowledgement of a request (activity), before sending the next one. If one request takes 333ms means you can do max 3 requests per second. Now big instances like lemmy.world have activity above that so instances too far will perpetual lag behind