Following https://tarte.nuage-libre.fr/c/fediverse/p/194717/we-need-more-users I decided to explore data a little bit more. I’m not the biggest fan of growth-as-as-target so I wanted to see how much the people were participating in the discussion.
The data
I took the data from the API explorer in https://api.fediverse.observer/ with this query:
query {
monthlystats {
date_checked
softwarename
total_posts
total_users
total_comments
}
}
Then parsed the json with this https://jqlang.org/ filter:
jq '.data.monthlystats | map(select(.total_users > 0 and (.softwarename == "lemmy" or .softwarename == "mbin" or .softwarename == "kbin" or .softwarename == "piefed"))) | group_by(.date_checked) | map( {date_checked: .[0].date_checked, total_users: ([.[] | .total_users] | add), total_posts: ([.[] | .total_posts] | add), total_comments: ([.[] | .total_comments] | add)}) | map({date_checked, posts: .total_posts/.total_users, comments: .total_comments/.total_users}) | sort_by(.date_checked) | map([.date_checked, (.posts | tostring), (.comments | tostring)]) | .[] | @csv'
(As you see I filtered for the threadiverse. I also did the same with all software, I’ll put the graph for that in comments)
Then did a good old’ chart
What to think of it
I don’t know. Users’ activity is on the rise and I find it nice


Maybe its a question of organization. Perhaps we shouldn’t have generic instances just instances around topics. That way niches can form without being too fractured and if said topic goes away it does not take several other coms with it.
I’d rather see better discovery tools and better community/account migration tools. Id be worried about topic-specific instances potentially backfiring by concentrating too much influence for a given set of subjects on the “preferred” instances
Good discovery tools are essential on a federated platform. An important part of twitter, facebook, and reddit success is/was that that they were the place for their particular style of content. You had a pretty good chance of being able to discover your old high school friends, because they were on the one platform. Then the (early) algorithm started discovering for you all the obscure content similar to your history.
Discovery has to work differently in a federated system. You can search for communities on Lemmy, but if your instance doesn’t already have someone subscribed to a community, then you’re not going to find it.
i think communities should have links to “related communities” in their sidebar sothat people can find similar communities more easily.
There could even be a “recommended” posts listing, besides the “subscribed”/“local”/“all” as it is today. it would show you posts from linked communities from communities that you already subscribed to too.
This defeats the purpose of the platform being distributed. For example if all political threads are on one instance it would be a ripe target for the authoritarian regimes popping up right now. I know there are dominant instances, but at least if one drops, people can migrate.
One issue is I think Lemmy’s UX means there’s less friction with local communities than remote communities (not sure why) which is why usually the lemmy.world version of communities typically wins without a lot of effort to steer people
Moderation reports are currently not federated (well they are in PieFed, but not in Lemmy) - at some point that will be added, but for all this time after the Rexodus this has been true. This lack of federation has hindered the growth of the Threadiverse.
Lemmy v1.0 has suffered too much scope creep, this update is way late while PieFed runs circles around Lemmy
Worse, I find that Lemmy typically (vastly) under-delivers what was promised even. Like for many years people were promised the capability to do personal “instance blocking”, and for a long time after the Rexodus there were calls to avoid defederating places like lemmy.ml or lemmygrad.ml or even hexbear.net, because that feature was “coming soon™”.
Then when that change did finally come, it only muted communities on that instance yet still left users to be able to reply in other communities, plus they could still vote on and thereby influence your content (hexbear is KNOWN for its brigading tactics). And then a subsequent bugfix opened it up still further to allow such “blocked” users the capability to send you a private DM, even pinging you with notifications - which on Lemmy (highly unlike PieFed) there is no way to stop that, even for WEEKs and WEEKs after you stop engaging… your consent to selectively stop such incoming pings does not matter, realistically (technically you could block every single person from an instance, one-by-one… but even there, you would have to bot that or do it the extremely tedious manual way, as the software provides no tools to aid with that). PieFed has offered the ability to block all users from an instance for over a year now.
The only counter-argument to the above is that software - especially FOSS (although Lemmy devs even get paid?!?) - takes time to develop. Which makes things like the bugs and inefficiencies that remain in Lemmy for years and years all the more disheartening. And then here comes PieFed, running around Lemmy in circles, it is almost no comparison at all.
And then I’m sure that I do not need to list out the rather LONG list of features that PieFed offers that aids community discovery - it’s quite amazing to see actually:-). PieFed is a game-changer for the Threadiverse, and might just keep it alive whereas it would otherwise have either died off or at least remained in obscurity forever known as a mere linux (& politics) forum. As things keep moving forward though, I think one day it could rival BlueSky, at least in terms of features offered, though whether a non-profit FOSS could ever overcome the strong network effect will remain to be seen… For that I think we would need a modmail, definitely notification upon content removal, perhaps better searching capability, maybe better modlog access, but not much else? (& 3rd party apps catching up to offer its features but that is not PieFed’s work anymore, now that so much has been exposed in the APIs)