Hexbear’s domain has expired and the admins can’t get ahold of the original registar. Currently up for auction at 20 bids and $550.

https://www.sav.com/auctions/details/7073489/hexbear.net

Edit: Their new domain is chapo.chat. Probably should let admins know so they can defederate them again.

  • tal@lemmy.todayEnglish
    15·
    11 hours ago

    Hmm.

    I assume that they could refederate under a new domain name, but I have no idea how the Threadiverse deals with an instance changing its domain name. Probably not well.

    • Draconic NEO@sh.itjust.worksOPEnglish
      183·
      10 hours ago

      That’s going to be a nightmare honestly if they do. Since there are so many Servers now with a big stick in their ass about defederation and only Defederated Hexbear after a lot of persuasion. This will probably end up giving their instance a second chance on many instances which defederated them before.

      @imaqtpie@sh.itjust.works @kersploosh@sh.itjust.works @InEnduringGrowStrong@sh.itjust.works We may want to be on the lookout for their new domain whenever they migrate to it.

      Edit: Their new domain is chapo.chat, we should probably block them before they try to refederate with us and spam our users.

      • tal@lemmy.todayEnglish
        14·
        10 hours ago

        I was less thinking “they might become refederated and have content reach instances that wanted to defederate” and more “what happens at a protocol and database level if one just changes a domain name, updates the X.509 certificate, and then refederates?” I mean, I don’t know how other instances deal with that, whether it can create problems. IIRC from past discussion, there are user keys somewhere in the protocol, and I assume that those would now be identical and collide across old and new instances, for one…

      • imaqtpie@sh.itjust.worksEnglish
        163·
        8 hours ago

        Please stop @ing the admins. We know about this. We will defederate if necessary.

        Edit:

        It appears that sh.itjust.works is not on the allowlist for chapo.chat. Just in case, we have added them to our blocklist anyway.

    • Draconic NEO@sh.itjust.worksOPEnglish
      111·
      10 hours ago

      Aaand they’ve already moved to chapo.chat. Probably should let all the instance admins who defederated hexbear before know before they’re refederated unknowingly.

        • tal@lemmy.todayEnglish
          6·
          9 hours ago

          If I remember correctly from a prior discussion, as-implemented, the two do not work the same way. User blocking blocks communities on an instance, but not users with it as their home instance, whereas defederation blocks both.

          That being said, I haven’t blocked instances myself, so I can’t personally confirm.