Email or username:

Password:

Forgot your password?
dansup's posts Post Back to profile
dansup

I've reached out to Meta/Threads devs regarding Nodeinfo and stats numbers for FediDB.org, unfortunately their legal dept rejected this.

I will use estimated numbers with the hope they will see this and have justification for reporting accurate stats.

Even though I have my own reservations regarding Meta (and how they've treated Pixelfed), putting my ego aside for the benefit of the fediverse is required when running an essential fedi service like FediDB.

#fediverse #activitypub

30 March at 8:02 | Open on mastodon.social
12 comments
Chris 🦑

@dansup god, I feel this so much. The battle ego vs believe. Totally against everything Meta is standing for vs an open fed web.

30 March at 8:14 | Open on mastodon.social
Luka Rubinjoni
Darnell Clayton :verified:

@dansup Yeah, I noticed early on about Threads misleading stats. I wish they would separate Federated accounts from total in-network stats, similar to what Flipboard has done (props to @mike for being transparent & doing this!).

I also noticed that while Zuck & Mosseri are on the Fediverse, the main Threads account is not which is odd.

30 March at 8:25 | Open on one.darnell.one
Martin Be

@dansup You know why they never ever will reveal those numbers? Because the real numbers will clearly expose their actions (data harvesting) done not only in front of but also and especially behind the curtains. They are greedy, but they are not stupid.

30 March at 8:34 | Open on mastodon.social
César Pallares :damnified:

@dansup I'm sorry...what they have been doing to #pixelfed???

30 March at 11:47 | Open on metalhead.club
dansup

@copdeb Well, its a long story, but basically a few bugs led people to not be able to post with Pixelfed mentioned for a while, it turned out to be a bug, and there were other things but yeah.

At the moment, Meta has been nothing but helpful regarding our interactions, so I have hope that they are really dedicated to the fediverse mission.

30 March at 11:53 | Open on mastodon.social
César Pallares :damnified:
FinchHaven

@dansup

"but basically a few bugs led people to not be able to post with Pixelfed mentioned for a while, it turned out to be a bug, and there were other things but yeah"

"a few bugs"

"there were other things"

Interesting how quickly you adopt the Meta party line on this

Meta was black-holing links to Pixelfed, they got caught and they got called-out, and Meta immediately blamed it on unspecified "bugs"

As mega-corporations do

It's becoming more and more clear which hand(s) are feeding you, and which hand(s) you're increasingly unwilling to criticize

cc @copdeb

@dansup

"but basically a few bugs led people to not be able to post with Pixelfed mentioned for a while, it turned out to be a bug, and there were other things but yeah"

"a few bugs"

"there were other things"

Interesting how quickly you adopt the Meta party line on this

Meta was black-holing links to Pixelfed, they got caught and they got called-out, and Meta immediately blamed it on unspecified "bugs"

30 March at 12:12 | Open on sfba.social
Wysteria

@dansup The stats on FediDB haven't been accurate for a while, a couple of legitimately run instances are banned, despite comfortably belonging in the top 10 largest instances by user count and MAU.

30 March at 12:01 | Open on mastodon.social
dansup

@wysteriary They are accurate, however we limit some instances from stats due to abuse

30 March at 12:04 | Open on mastodon.social
Wysteria

@dansup If by abuse you mean spam instances and fake nodeinfo data then that makes sense, inorganic traffic for its own sake shouldn't be accounted for. But the traffic on a banned instance like baraag.net for example is entirely organic and seeing it listed among a sea of ngrok.io instances just makes FediDB reporting unhelpful.

30 March at 12:15 | Open on mastodon.social
Maho Pacheco 🦝🍻
Go Up