@underlap
It is not fully connected. Nodes federate with eachother whenever a user from one node follows a user from another. Only federated servers that share atleast one pair of mutual followers sync up but in that case thry sync up all users and all users from one server will appear in the federated timeline of the other.
You also have servers that operate whitelists or blacklists that block other servers.
@underlap
There are relays to help with discovery.
@zpartacoos
@freemo I can't find a definition of an ActivityPub relay - just various lists of them and nothing in the spec. Do you have a good reference, please?
@zpartacoos
@underlap
relay is just instance without UI
@odesa Ok. So presumably any actors are predefined or similar?
Hi glyn, in case you hadn't found them, I co-maintain some #ActivityPub watchlists:
https://git.feneas.org/feneas/fediverse/-/wikis/Watchlist-for-ActivityPub-developer-resources
https://git.feneas.org/feneas/fediverse/-/wikis/Watchlist-for-ActivityPub-apps
And the central community hub of fedi devs is #SocialHub at:
https://socialhub.activitypub.rocks
There's a crowdsourced Guide for AP implementers here:
https://socialhub.activitypub.rocks/t/guide-for-new-activitypub-implementers/479
@freemo @zpartacoos Very interesting. So the graph of nodes is "induced" by the graph of user follows.
So a node with a larger number of users would probably need to connect to correspondingly more other nodes because of the disparate social networks of its users. On the other hand, small nodes with, say, a hundred users who each follow less than a hundred others would only need to connect to at most 10k other nodes, and probably a lot less. (If there were billions of users, I think discovery would become a problem unless there are some nodes with very many users.)