’'’QOTO is one of the least block and most federated server in the fediverse. I wanted to share some of the data we have to know thats the case.’’’
Recently I had a discussion with @olamundo and @design_RG RG about if QOTO is blocked by many others servers and how to figure out if it is a problem.
The first thing to keep in mind is the only way you will ever find a server that no one blocks is if the server is new and no one knows about it yet. That means your messages wont make it into the Federated Timeline. So we want a server that is both established, and has a minimal number of blocks.
While there is no way to get a list of all servers that block your server there are several ways you can measure how well connected your server is which is an indication of your servers reputation in the greater fediverse.
the first and most telling measure is the peer count. The peer count are the number of servers that are aware of your server and federates with it. In other words it is the number of servers where your posts will show in their federated timeline, meaning they dont block you and at least one of their users follows one of our users.
The QOTO peer count is ~9,200 give or take 100. You can find this information in the following two places (each approximately agreeing with the other):
We can see how that rates us compared to other servers in the fediverse by pulling up the full list of servers above and sorting by peers. we see that out of ~4000 server QOTO ranks 24th most peers
The other way we can check is with a different measure called ‘'’insularity’’’. What this measures is how often people actually communicate across server lines with 100% meaning all communication is internal between users on a single server. So the closer to 0% we are the more servers we have communication with.
QOTO has an insularity of 17.2% which again is listed at the above link. There is no good way to rank this value, but if you look at all the other popular servers you will quickly see we have one of the best insurality values as well beating out even M.S.
@freemo @olamundo @design_RG I don’t think having a lower insularity than M.S is actually a meaningful comparison, as their user count is more than forty times greater than QOTO’s. It seems reasonable to expect that large instances will score higher measures of insularity, even given the same behaviour as small instances.
Quick aside: insularity is defined as the ratio of mentions of local users to mentions of all users.
Consider a Fediverse where all the users are instance-agnostic in their communications; that is, the likelihood any pair of users communicate is independent of whether or not they are on the same instance. Now imagine the limiting case, with just two servers, one a single-user instance and one a giant instance with everyone else. The small instance will have near-zero insularity (the only mentions of local users will be if the user names himself for some reason) and the large instance will have near-100% insularity (the only mentions not of local users will be conversations involving this one particular user). The insularity scores differ wildly, even though the users have the same behaviour - they’re just a function of where you draw boundaries to group users.
It seems like there ought to be a way to normalise this, something like (local mentions * all users) / (all mentions * local users), but quantifying the “all users” part seems hard. How would you qualify a user as potentially mentionable, how would you treat dormant accounts, etc. - such questions would affect the outcome. Absent such a normalisation, I think insularity scores should really only be compared between instances with similar numbers of active users.
@khird I think there is a subtle importance regarding what we measure… Are we trying to measure how popular our users are? Or are we trying to measure how many servers block us and what portion of the fediverse we federate with.
I was trying to measure how much of the fediverse we federate with more so than simple popularity. The point was to measure instance blocks and how common they may happen to be.
As such im not sure there would be a need to normalize the peer count. Sure M.S is expected to have more peers because they have more users. While that does say something, perhaps about how interesting we are as you say. If we really just care about how many servers are ferederating with us our prevalence for being blocked I’d say the raw peer count makes sense as was stated without any additional work to adjust for server size.
Insularity though I do agree with you, that needs to be normalized somehow to be useful.
@khird It is certainly a factor that plays a role here. But that would probably only be an effect seen on smaller servers in relation to us, consider…
If a instance is sufficiently large then it is garunteed that at least one user on the instance would want to follow one of our users, especially since we are a large instance. If you are less interesting you might get 1 follower instead of 100 from a server of 100,000, but 1 or 100 makes no difference WRT federating. So for large servers if we federate or not is going to be almost entierly determined by if we are blocked or not.
It would only play a role if a server is small enough that popularity has a significant effect on if a server has that one user.
So its going to play a role for sure, but I dont think its going to be the majority of the effect at play.
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.
@freemo Good point. I figured the primary motivation for following a QOTO user (thereby making your instance a peer of QOTO) is because you think the guy you’re following is interesting enough you want to see what he posts. But maybe the connection between the two is more tenuous than that, and my assumption was unjustified.