if Threads starts supporting nodeinfo they will start showing up in the fediverse instance trackers automatically unless we block it proactively: looking at you the-federation.info and fedidb.org
if Threads starts supporting nodeinfo they will start showing up in the fediverse instance trackers automatically unless we block it proactively: looking at you the-federation.info and fedidb.org 10 comments
@dansup @liaizon I don't think we should block them as they would technically be part of the fediverse, even if we hate meta. It's a big step for ActivityPub, and hopefully soon with others like Tumblr, the numbers on fedidb would be enough to convince more social platforms to integrate. I do agree with the sentiment that sometimes I just want to look up things related to non-corporate fedi, so maybe a toggle to filter that data would be handy @dansup I don't think they should be fully blocked from the databases. An ideal solution would be to have a way to filter from the individually owned and operated instances (basically all of fedi right now) and the corporate ones (Meta right now, Tumblr and others in future). @dansup if they turned on federation tomorrow it would not be true in any historical sense of the word to say that the fediverse contains 100 million users. Its just not the same thing. I dont think there would be anything wrong with having a view that showed how many users they have but we need to be very careful to separate that number what we have built @liaizon your msg said: "if Threads starts supporting nodeinfo they will start showing up in the fediverse instance trackers automatically unless we *block it* proactively: looking at you the-federation.info and fedidb.org" → hence my comment |
@liaizon You think we should block them?
Maybe a separate category could work, curious about the reasoning behind this, I know it will throw off averages and stuff so I'm not against it