• @[email protected]
    link
    fedilink
    English
    04 months ago

    They didn’t make this too be easy to use. They don’t give a shit about that. That isn’t their job in the slightest.

    They reserved a TLD, that’s all.

    You can use any TLD you want on your internal network and DNS and you have always been able to do that. It would be stupid to use an already existing domain and TLD but you absolutely can. This just changes so that it’s not stupid to use .internal

    • @[email protected]
      link
      fedilink
      English
      14 months ago

      No one is saying it is their job.

      Merely that using a TLD like .internal requires some consideration regarding ssl certificates.

      • @[email protected]
        link
        fedilink
        English
        -14 months ago

        But why are people even discussing that?

        This is about an ICANN decision. TLS has nothing to do with that. Also you don’t really need TLS for self hosting. You can if you want though.

        • @[email protected]
          link
          fedilink
          English
          24 months ago

          Because people can discuss whatever they like?

          If you don’t like it just down vote it.

        • JackbyDev
          link
          fedilink
          English
          14 months ago

          People can talk about whatever they want whenever they want. The discussion naturally went to the challenges of getting non-self-signed certificates for this new TLD. That’s all.