For example, can I find ActivityPub instances that kbin.social is federating with? I know that kbin.social is federating with fedia.io, lemmy.world, and mastodon.social. Then I want to find other interesting instances. I am also interested in ActivityPub instances that a certain instance is blocking because they may be rather good for me.

There are web sites that are publishing ActivityPub instances, for example:
https://the-federation.info/platform/184

And maybe there are other sites that are publishing federation relationships of instances. However I want to know how to find federated/blocked instances from a certain instance instead of the sites if I can. Doesn’t ActivityPub have such a method itself?

Update: Lemmy instances have their linked/blocked instances list.
https://lemmy.world/instances
https://lemmy.ml/instances
https://feddit.cl/instances

I want /kbin to have the same list!

Update 2: Mastodon has instance API.
$ curl https://mastodon.social/api/v1/instance/peers

  • uhvaygaOP
    link
    fedilink
    1
    edit-2
    2 years ago

    It probably has a way, since kbin has a federation button at the top right in the sidebar. kbin.social’s bar has the “instances” list empty there.

    I didn’t notice it until seeing your post. Thanks!

    I have no kbin account so I cannot tell if it’s private and the list would be nonempty when someone logged in kbin.social views it.

    The list is also empty with my account logging in kbin.social.

    […] they are already in the magazines list of your instance.

    They are as you said. Now I’ve come to think that scraping the magazines list is the most realistic way to find federated instances from a certain instance except blocked ones.

    I want admins to publish their configs to federate/block other instances though they have no duty to do. :D

    • Brunacho
      link
      fedilink
      English
      12 years ago

      The list is also empty with my account logging in kbin.social.

      Makes perfect sense, tbh. The list of instances federating with yours will get too large pretty quickly to have it listed in the sidebar -see the one of my instance, literally hundreds-. A sidebar is a terrible place for that information.

      I want admins to publish their configs to federate/block other instances though they have no duty to do. :D

      Maybe you can ask for the feature in the project site and future versions of Kbin will have it and no need for admins to include it themselves. I believe the developers had the intention to show the instances connected -as seen by the sidebar thing-, so maybe it’s just asking for a page similar to Lemmy’s one. Though it is possible that kbin.social admins do not want to show it and are actually hiding it.