The new FediDB is much better.

You can more easily view data and graphs without leaving the page you're on.

Can't wait to ship this

FediDB will soon become open source and self-hostable, and I look forward to contributions from our community as this has proven to be an essential resource.

I want to thank all of my supporters for giving me the ability to work on projects like these, I strive to do better and I think you guys will like the new FediDB.

A new FediDB era, with an open source fresh coat of paint, is soon upon us

Worrying fediverse trend https://3dcandy.social/2025/03/worrying-fediverse-trend/ #3dcsocial #boost #fedidb

FediDB respecting robots.txt has resulted in appr. 2M Fediverse accounts no longer being counted.

Prior to this change, #FediDB counted 12,923,233 accounts. Now it counts 10,868,233 accounts.

Now let me be blunt: respecting robots.txt is a good thing. But now when we look at #Fediverse accounts, it must clearly be seen with the acknowledgement that these only count services that haven’t opted out of tracking.

So when people compare user counts of #Bluesky vs. the Fediverse, remember that Bluesky has the luxury of a more complete count because they host all accounts there. In contrast, the Fediverse is actually decentralized, and a good many services simply do not want to be tracked – and are therefore not counted.

https://fedidb.org/

@fediversenews

#FediDB respecting robots.txt has really changed how stats are tabulated.

Prior to this change, there were 997 #Pleroma servers that were counted. Now the count has been reduced to 582.

With #WordPress, the difference is more stark. Prior to the change, there was over 9,000 WordPress servers counted. Now the count is at 3,578 servers.

To be sure, I’m not complaining – privacy is important. But it is to say that #ActivityPub user counts should have a big asterisk: many servers have opted out of being crawled. This means they are not being counted.

FediDB says there are 12,923,059 accounts across the #Fediverse. But this is actually drastically higher.

Hello Everyone,

After having a lot messages from people yesterday about why we should not have a block system we are going to refactoring our reports system into a more positive system into the future.

Instead of reporting a negative thing someone has done we might instead add a positive someone done instead.

This will help make the Fediverse more positive instead of negative.

I've been hard at work making the users section look that little bit more pleasing for Fedicate.

I will be looking further into automating the process to update minor things such as profile pictures and other things on the database but for now the manual way is plenty fine.

Thank you for everyone that has submitted Instances & Software that should be added to Fedicate. Keep up the good work and if you haven't already check it out on https://fedicate.org

#Fedicate #FediDB #Fediverse #FediverseDatabase #FediverseHelp

FediDB Community Advisor, a new service we're building for fedi admins to subscribe to moderation advisories from other server admins.

We're building this into Pixelfed and Loops, but any fediverse software will be able to use this!

We use a clever combination of double blind lookups and http signatures, using a pubsub feed.

More details soon.

Fedi Devs can send an email to hello at pixelfed dot org for early access.

Oh, more fun #fedidrama for anyone who cares.

Last night, @dansup (creator of #Pixelfed #Loops #FediDB and more...) began bashing @dumpsterqueer (creator of #GoToSocial) for "faking nodeinfo stats" on #GoToSocial servers.

He had at least three posts about it (screenshots from archive.ph snapshot attached) before deleting them. Two of the three posts were, unsurprisingly if you've kept up with Dan recently, pretty insensitive. Also a bit ironic, as Dan is known to boast from time to time about how much he lifts up other fediverse developers.

Another user pointed out they found an update in the GTS repo that added an option to randomize instance user stats to throw off bots from detecting exactly how many users were on an instance, if the GTS server admin chose to enable it. Apparently a few did, thus prompting Dan's posts when his fedidb.org site started picking up crazy user numbers on these GTS instances.

I don't know if Dan decided to delete his posts after finding this out, or if cooler heads prevailed in the end, but either way his posts are now gone. Just like the entry for GTS on the FediDB (https://fedidb.org/software/gotosocial).

At the time I started writing this, the other major fedi server catalog site #FediverseObserver still had GTS servers listed but had instance user numbers all set to 0. However, looking at it again now, they appear to have delisted GTS servers as well.

Link to archive.ph showing Dan's full timeline from last night: http://archive.today/XFfbg

Another fun day in the #fediverse!

#Fedipact è nuovamente su #fedidb: https://fedidb.org/current-events/anti-meta-fedi-pact

Already got our FediDB entry:

https://fedidb.org/network/instance/pixelix.social

I appreciate all the support, and just wanted to remind you all that I've been preparing for this moment for years.

I tend to excel under stressful conditions, while maintaining a healthy balance by taking every other night off from coding.

I won't waste this opportunity, and remain focused on @pixelfed during this historic moment!

Admins, users and even press are free to mention me, I'm here to serve you!

Remember that

@alwirtes BTW the more I look over these, and consider 2025, the more thankful I am for #FediDB whitout which we would be flying blind in terms of Fediverse growth data. Thanks @dansup for all your work on that!

Hey @dansup could you enable more stats for the fedidb page of mbin? https://fedidb.org/software/mbin
Like the funkwhale or lemmy one:
https://fedidb.org/software/funkwhale

I bet @melroy would enjoy that too