• RA2lover@burggit.moe
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    manually checking the list, there are some communities that defederated but remain in the list:

    as well as some communities with policies that would clearly defederate burggit:

    The list also includes plenty of single-user instances without any posts, as well as instances using whitelists not including burggit.moe and a few local-only instances, though i didn’t bother making lists for them.

    You should be able to fetch instance block lists from other instances (which on most lemmy web UIs is exposed in /instances) - but even that isn’t a requirement AFAIK :-/

    • Burger@burggit.moeOPM
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Thanks for that. I’ll put those in a secondary script which should automatically scrub them off the federated instance list when the compile script runs later. I had to manually remove sh.it.just.works too, but I guess there’s a lot more than I thought there would be.

  • Disa@burggit.moeM
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    Great that you got this working, happy I could help with the minimal frontend work involved. disa yay

    • Burger@burggit.moeOPM
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Yep, ty. The API is a pain in the ass. There’s no function to see who defederated us. So I had to crudely scrape fba.ryona.agency and do a little bash to compare the two files. One being the list of instances we are linked to and the other being who blocked us.

      Also, fuuuuuck typescript. It can go to hell.

    • Burger@burggit.moeOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      It’s not just you. I need to work on it again since I forgot to copy it over when we moved servers and lost all of my work for making the logic work since my /home partition got reformatted.